How To Automate Compliance If You Aren't Chuck Norris
summary
Claims that compliance moves from paper to code by putting documentation and tests into the delivery flow and that an automated system security plan can be assembled from repository fragments. Practical recipe: add CI pipeline scans (InSpec, OpenSCAP, SecureCI) and pen‑test tooling, fold OpenControl manifests into source control, and feed results into a generated SSP. Community adoption examples include 18F, Pivotal, Docker, Red Hat and a referenced Fredonia compliance tutorial that demonstrates the pipeline end‑to‑end.
AI-written summary · about
related talks
30mBuilding a Cloud-Native Compliance Culture - CeeCee O'Connor (Boston Scientific), Chuck D'Antonio
26mOperational Compliance: From Requirements to Reality
33mCompliance Without the Chaos: Building It Right Into Your DevOps...
32mAutomating Security Compliance at Scale
31mShifting Left Securely
10mTest Driven Compliance
03mCompliance-As-Code For API Security - session preview
37mDevOps - The Automation of Compliance