Vol. III
Cloud-Native Security for DevSecOps
Zero trust, Kubernetes hardening, IaC security and compliance automation
§ 01, What it's about
Zero-trust architecture, Kubernetes hardening, infrastructure-as-code security and compliance automation, with evidence mapped to ISO 27001, SOC 2, PCI DSS and DORA. The compliance part is the Compliance Automation Framework explained at length.
§ 02, What I want the reader to be able to do
- 01
Harden a Kubernetes cluster and show which control covers which risk.
- 02
Keep infrastructure code scanned, policy-checked and free of secrets.
- 03
Map a control to ISO 27001, SOC 2, PCI DSS or DORA and collect its evidence from the pipeline.
§ 03, The diagram I keep coming back to
Scrolls sideways →
§ 04, Planned structure
- Part I
Zero trust architecture
Workload identity, mutual TLS and just-in-time access, applied to cloud-native systems.
- Part II
Kubernetes security engineering
Hardened images, pod security standards, admission policy, runtime detection and network policy.
- Part III
Infrastructure as code security
Scanning and policy for infrastructure code, secrets kept out of it, and drift caught before it matters.
- Part IV
Compliance automation
A continuous compliance pipeline, with controls mapped to ISO 27001, SOC 2, PCI DSS and DORA and evidence collected as a side effect.
§ 05, When it's readable