Regulatory Compliance as a DevOps Enabler
summary
Argues that regulatory demand becomes a funding and design lever not a blocker and shows concrete steps: creates a DevOps tooling platform, automates CI/CD and regression tests, decouples portfolio, and proves compliance to ECB evidence standards in about 2–3 years; proposes compliance as code frameworks, event‑driven zero‑touch pipelines, and auto‑remediation (example target: 55% of fixes automated); demonstrates selective production data copy for testing (subset of 10,000 policies) and pragmatic pre‑prod “islands” that regulators accept.
AI-written summary · about
chapters (13)
- 0:00Regulatory compliance as DevOps enabler
- 1:05From compliance to DevOps journey
- 6:39Regulatory controls in SDLC
- 9:48Multi-speed compliance adoption
- 13:01Portfolio in regulatory prioritization
- 16:54Value stream for compliance
- 21:51Compliance as code example
- 27:09Dynamic evidence generation
- 31:00Regulator proximity vs progress
- 33:28Segregation of duties risks
- 36:40Database copies in deployments
- 41:19Production readiness review
- 42:47Q&A
related talks
48mWhen DevOps Meets Regulation: Integrating 'Continuous' with 'Government'
44mDevOps in Regulatory Spaces: It's Only 25% What You Thought It Was…
33mCompliance as Code - Lessons Learned From Regulated Organizations
37mDevOps - The Automation of Compliance
37mCompliance & Regulatory Standards Are NOT Incompatible with Modern Development..
43mBringing product thinking into DevOps
31mWrangling Compliance in the Wild West of Software Delivery
22mBridging Compliance and Innovation: A Guide for DevOps Leaders