blumeops/docs/reference/operations/security.md
Erich Blume 69737dc915 C1: docs-first removal of compensating-controls framework
Deletes the CC how-to and explanation docs, and the orphan changelog
fragments describing CC reviews. Updates security.md and
read-compliance-reports.md to describe muting in terms of the mutelist
files only. Adds the branch changelog fragment.

Mutelist YAML files, the Prowler CronJobs, and the
review-compliance-reports task all stay — they're updated in the next
commit.
2026-05-22 20:09:28 -07:00

2.2 KiB

title modified last-reviewed tags
Security & Compliance 2026-03-24 2026-03-24
operations
security

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)
  • kingfisher — Secret detection and live validation for Forgejo repos (weekly CronJob + prek hook)

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.me services
  • flyio-proxy — public ingress via Fly.io tunnel
  • Tailscale — zero-trust mesh networking across all nodes

Secrets management

Reports

All compliance scan reports are stored on sifaka:/volume1/reports/. See read-compliance-reports for access and interpretation.

Suppressed findings are kept in Prowler mutelist YAML under argocd/manifests/prowler/mutelist/. Each entry's Description field explains why the finding is muted; entries are reviewed ad-hoc rather than on a scheduled cadence.

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