Test Driven Compliance
summary
Claims that compliance controls become executable tests and run in CI to yield continuous, auditable compliance. Shows concrete examples such as when a pull request has no review then the merge build fails, maps controls to BDD-style examples and implements them as a unit testing framework that checks static analysis, test coverage and vulnerability scans in the pipeline. Describes integration with DevOps pipelines, independence of failing controls for clear diagnostics, and cites industry implementations that successfully prevent unsafe deployments while speeding delivery.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:05Not just regulated industries
- 1:20Improve quality
- 1:30In the middle
- 2:13Proof paper
- 2:39Slow process
- 3:03Prevent code delivery
- 3:32DevOps
- 5:04Compliance is a sociotechnical system
- 6:26BehaviorDriven Development
- 6:57Compliance
- 8:28Unit Testing Framework
- 9:01Automated Compliance
related talks
05mHow To Automate Compliance If You Aren't Chuck Norris
37mDevOps - The Automation of Compliance
32mBuilding Confidence Together: Continuous Integration & Testing
44mCompliance by Design | Continuous Compliance
34mUsing Test Automation for Continuous Integration, Delivery and Quality
29mAutomating Continuous Compliance for Scalable SaaS Delivery
33mCompliance as Code - Lessons Learned From Regulated Organizations
34mWhy continuous testing is essential