Policy-as-code for Any Cloud to Any Edge Automation
summary
Claims that packaging every policy as code makes multi‑cloud and edge configs provable and automatable using Chef plus a compliance/test layer, pushing the same git + pipeline + Jenkins workflows to infrastructure. Backed by a cited 50% information loss per handover and under 10% survival to production, and real deployments across millions of objects (retail, restaurants, remote sites) that run with intermittent connectivity. Uses CIS profiles for checks and produces auditable proof that the approach scales and catches simple misconfigurations.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 1:29Speaker background
- 3:14Computing and data evolution
- 7:56Manual config to IaC
- 10:46Infrastructure as code principles and benefits
- 13:15Shift left and DevSecOps
- 18:58Public cloud and multicloud
- 23:33Security in distributed cloud
- 26:03Data generation trends
- 30:00Policy as code for automation
- 31:47Benefits of policy as code
- 33:55Recommendations
related talks
17mEnhancing cloud security with continuous compliance
14mRisk Management in a Coded Enterprise
12mEnd-to-end policy-as-code from IaC to Running Workloads
33mCompliance as Code - Lessons Learned From Regulated Organizations
38mKick Starting our DevOps Transition with Chef Compliance
23mSecure Your Systems the Better Way Using Policy-as-Code
24mGeneralizing Policy-as-Code for Compliance Posture Management on Multi-Cloud Infrastructure
25mPaC in Jenkins for DevOps Pipelines