Kick Starting our DevOps Transition with Chef Compliance
summary
Chooses a compliance-first route using Chef Compliance and InSpec, builds a multi-tenant Compliance-as-a-Service with a web front end and automated 24‑hour scans, and bakes checks into Packer-built gold images and Test Kitchen. Reporting is handled via Power BI after extracting JSON from scans. Practical metrics: a manual 15‑minute configuration review becomes reduced review time from 15 minutes to 1, and a modeled critical failure = 8 hours of unplanned work, driving measurable reductions in rework and outages.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:25Community Summit 2015
- 2:30Scanner
- 3:04CIS
- 3:50Compliance
- 5:25Deploy Compliance First
- 7:20Lay Down Mantra
- 8:02Targets and Compliance
- 12:28Time Savings
- 13:40Reducing Unplanned Work
- 14:57Example
- 15:39Youre a crossroads
- 16:05Have you sold this
- 16:31Adoption is key
- 17:19What one thing would help you
- 20:53Metadata
- 25:24PowerShell
- 26:55PowerBI
- 28:47Compliance as a Service
- 29:06Gold Templates
- 35:36Conclusion
- 36:27Closing
related talks
17mEnhancing cloud security with continuous compliance
15mMulti-Cloud Compliance As Code with InSpec
36mImproving Security while Reducing Toil with DevSecOps
49mBaking Safety into Infrastructure Testing
31mShifting Left Securely
33mCompliance Without the Chaos: Building It Right Into Your DevOps...
25mTransform Your Security Practices With DevOps
20mUsing Compliance to Quarantine: Remove The Risk and Rebuild Clean