CompOps (Compliance Operations): Regulatory Cultural Change
summary
Argues that compliance must be engineered like software: apply CI/CD, automated testing, infrastructure as code and compliance as code so audits become repeatable attestations rather than ad hoc reports. Claims this cut audit response time and administrative cost, improves evidence delivery and reduces open findings; notes fintech teams often juggle a dozen federal regulators plus states. Recommends tools and practices such as policy as code (mentions Open Policy Agent), a maturity model, and continuous monitoring and verification.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:34Overview
- 1:20Compliance vs Operations
- 3:15Take aways
- 3:57GRC triad
- 5:23People processes technologies
- 6:23Modern compliance
- 7:53The GRC Triad
- 9:06The Good News
- 10:45Operational Excellence
- 12:22Review
- 13:05Maturity Model
- 14:29Security
- 16:07Velocity
- 20:45Compliance as a Service
- 24:23Questions
related talks
33mCompliance as Code - Lessons Learned From Regulated Organizations
05mHow To Automate Compliance If You Aren't Chuck Norris
37mDevOps - The Automation of Compliance
44mCompliance by Design | Continuous Compliance
54mCompliance-As-Code For API Security
33mCompliance Without the Chaos: Building It Right Into Your DevOps...
22mBridging Compliance and Innovation: A Guide for DevOps Leaders
21mDevOps in a Highly Regulated Financial Infrastructure Company