Prove it! The Last Mile for DevOps in Regulated Organizations
summary
Shows how regulated teams turn requirements into runnable proof: capture every API call with CloudTrail JSON → CloudWatch → Kinesis → ELK, index and keep census instead of screenshots, and link dashboards to specific regs like map 45 CFR 164.312 audit control to log searches. Describes cataloging config in GitHub, enforcing separation via Jenkins pipelines, and a workflow to treat each artifact as a sprint so auditors get reproducible, automated evidence.
AI-written summary · about
chapters (9)
- 0:00The DevOps and audit gap
- 2:52Lessons from mathematical proofs
- 5:05Isolation vs. transparency
- 9:34The human side of compliance
- 12:11Adapting to modern infrastructure
- 17:15The importance of iteration
- 20:06Trusting makers over authorities
- 22:19Engineering for compliance
- 29:04Resources and concluding remarks
related talks
33mCompliance as Code - Lessons Learned From Regulated Organizations
44mDevOps in Regulatory Spaces: It's Only 25% What You Thought It Was…
33mCompliance Without the Chaos: Building It Right Into Your DevOps...
29mAn Unlikely Happy Couple - DevOps and IT Audit?
43mRegulatory Compliance as a DevOps Enabler
29mPanel Discussion: Ask an Auditor Anything: DevOps Compliance
48mWhen DevOps Meets Regulation: Integrating 'Continuous' with 'Government'
37mDevOps - The Automation of Compliance