Path To Production: Sustainable Compliance In Strict Environments
summary
A concrete path to continuous compliance using policy and machine-readable controls: OSCAL documents map tool capabilities (Big Bang, Iron Bank, Kyverno) to NIST controls, Cerna (policy engine) and the Lula CLI validate manifests, and a zarf package demo shows AC‑4 enforced by mTLS sidecar injection — the check passes, then fails when injection is removed. The system emits OSCAL compliance reports ingestible by GRC tooling, supports versioned policy-as-code and audit-signable policies, and works live against Kubernetes.
AI-written summary · about
chapters (10)
- 0:00Sustainable compliance intro
- 1:09Regulated environments challenges
- 3:40Avoiding NIH in compliance
- 6:07Reciprocity for DevSecOps
- 8:13Compliance as code vs docs
- 12:14Policy as code controls
- 17:40Automating compliance OSCAL
- 20:11Kubernetes compliance demo
- 29:10Future of compliance automation
- 36:39Q&A auditor trust
related talks
22mOSCAL in Action: Real World Examples of Automating Policy & Comp...
40mAutomating Security and Compliance via a new standard-of-standards
43m12 Essential Requirements for Policy Enforcement and Governance with OSCAL
41mAvoiding IAC Potholes with Policy + Cloud Controllers
40mCloud Native GRC
33mAutomating Industry Regulation (SoX, SoC 2) Enforcement...
08mTrestle Compliance Collab Platform OS Project + NIST Compliance as Code OSCAL Standard
29mZero Trust Maturity Assessment With OSCAL