A Year with Chef and InSpec: A Retrospective with Optum
summary
Optum spends a year replacing manual, PDF-driven compliance with Chef and InSpec, proving continuous compliance by running InSpec profiles locally, via scanned via SSH/WinRM, and against running containers with docker container scans (no agent). The team builds Test Kitchen proofs, an audit cookbook that runs during chef-client, and chef recipes that auto-remediate failures; results are measurable: faster visibility pre/post delivery, fewer outages for controls, culture shifts from sysadmin to code-first workflows, with patch automation and auditor evidence next.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:58Foundation Engineer
- 3:58Continuous Compliance
- 12:04Compliance as a Continuously Improving Journey
- 12:59Site Visibility
- 23:31Technical Challenges
- 26:44Non Technical Challenges
related talks
36mIntroduction to Test-kitchen and InSpec
33mTest Driven DevOps
49mBaking Safety into Infrastructure Testing
25mTransform Your Security Practices With DevOps
41mManaging the Unmanageable
22mMoving Fast Together: Test-Driven Infrastructure
15mMulti-Cloud Compliance As Code with InSpec
31mShifting Left Securely