Erich Blume
fe201a495c
Clone repo in init container, scan Dockerfiles and K8s manifests with Prowler's IaC provider (Trivy). Reports written to sifaka:/volume1/reports/prowler-iac/. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.9 KiB
1.9 KiB
| title | modified | last-reviewed | tags | ||
|---|---|---|---|---|---|
| Security & Compliance | 2026-03-24 | 2026-03-24 |
|
Security & Compliance
Security posture and compliance scanning for BlumeOps infrastructure.
Compliance frameworks
| Framework | Tool | Cluster | Notes |
|---|---|---|---|
| CIS Kubernetes Benchmark v1.11 | prowler | minikube-indri | Weekly CronJob, ~82 checks |
| PCI DSS v4.0 (K8s mapping) | prowler | minikube-indri | Reuses CIS checks mapped to PCI requirements |
| ISO 27001:2022 (K8s mapping) | prowler | minikube-indri | Partial — 22 of 92 controls mapped |
Scanning tools
- prowler — CIS Kubernetes Benchmark scanner (weekly CronJob)
- deploy-prowler — deployment and ad-hoc scan how-to
- read-compliance-reports — accessing and interpreting reports
Identity & access
- authentik — SSO/OIDC provider for all web services
- RBAC — Kubernetes role-based access control (audited by Prowler RBAC checks)
Network & TLS
- caddy — TLS termination for
*.ops.eblu.meservices - flyio-proxy — public ingress via Fly.io tunnel
- Tailscale — zero-trust mesh networking across all nodes
Secrets management
- 1password — root credential store
- external-secrets — Kubernetes secrets synced from 1Password
Reports
All compliance scan reports are stored on sifaka:/volume1/reports/. See read-compliance-reports for access and interpretation.
Known gaps
- No SOC 2 compliance mapping for Kubernetes (Prowler only maps SOC 2 for AWS/Azure/GCP)
- k3s control plane checks produce no results (embedded binary, no static pods) — consider kube-bench
- Container image scanning covers
blumeops/*images only — upstream images (ollama, immich, etc.) are not scanned - IaC scanning covers the blumeops repo only — no scanning of third-party Helm charts or vendored manifests