Improving Security while Reducing Toil with DevSecOps
summary
Automating compliance turns a months-long spreadsheet grind into CI checks and alerts: Ansible plus the Rackspace-derived CIS hardening playbooks enforce hundreds of settings, InSpec validates them, and monitoring surfaces exact remediation steps. The platform-level repave rotate repair cycle (BOSH or similar) limits dwell time for malware, and the automation frees about 3–4 FTEs across thousands of servers, saves “tens of thousands” in labor, and ships as part of the CI pipeline with canary updates.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:22Agenda
- 1:53What is Compliance?
- 5:02Example of Compliance Specifications
- 23:26Organizational culture eats strategy for breakfast, lunch and dinner
- 24:48Adopting a DevOps culture
- 26:38Value Stream Mapping Process
- 27:46Mappable Processes that include Security/Compliance
- 28:43Value Stream map for Provisioning a New Server
related talks
36mImproving Security while Reducing Toil with DevSecOps
25mTransform Your Security Practices With DevOps
53mGround Truths of a Rugged DevOps Practitioner
43mBuilding a Secure DevOps Pipeline
42mContinuous Security: Integrate security tools into your DevOps Pipeline
15mDevopsec: Rapid Security in the Cloud with AWS and CIS
31mDevSecOps, or How to Integrate Security into DevOps Practices
32mAutomating Security Compliance at Scale