Enhancing cloud security with continuous compliance
summary
Claims that encoding CIS and DISA checks as executable profiles lets teams detect and remediate compliance failures in minutes, not months; shows Chef’s inspect language running in pipelines with Test Kitchen to reproduce a prod failure, fix code, and verify before deploy. Gives concrete wins: Scholastic remediates a Shellshock fix and ships to production within an hour, a bank cuts $2M in tooling and slashes remediation time. Also shows exceptions encoded in code for auditable approval.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:30Continuous compliance: What we're talking about
- 3:30Importance of Continuous Compliance
- 4:28Continuous compliance: The baseline
- 5:33Continuous compliance: As Code
- 6:49What about exceptions?
- 7:48Continuous compliance: Managing exceptions
- 8:41Exceptions as code
- 9:07Today's audits
- 11:42Customer evidence Compliance automation
related talks
38mKick Starting our DevOps Transition with Chef Compliance
24mSecurity as Code A SecDevOps Use Case
36mImproving Security while Reducing Toil with DevSecOps
31mShifting Left Securely
05mHow To Automate Compliance If You Aren't Chuck Norris
43mPolicy-as-code for Any Cloud to Any Edge Automation
15mDevopsec: Rapid Security in the Cloud with AWS and CIS
36mImproving Security while Reducing Toil with DevSecOps