Compliance-Aware Platform Engineering
summary
Platform engineering embeds regulatory controls as executable gates: Terraform/Bicep requests hit an admission layer that rejects deployments with encryption disabled or public IPs in regulated subnets, policies live in Git with PRs and tests, and runtime scans run continuously. Golden images are hardened, signed and rebuilt on a fixed cadence (biweekly unless critical CVE), provisioning time drops from days to under an hour, and a single global baseline eliminates regional configuration drift.
AI-written summary · about
chapters (16)
- 0:00Introduction and Speaker Background
- 0:37Understanding Compliance in Platform Engineering
- 2:26Agenda Overview
- 2:56Regulatory Landscape and Design Implications
- 3:26Evolution of Delivery Model
- 3:45Building Blocks of Compliance by Design
- 4:44Compliance Challenges in Financial Services
- 6:52Platform Engineering Evolution
- 10:01Provisioning Frameworks and Policy Enforcement
- 13:27Golden Images and Compliance
- 15:33CICD and Continuous Compliance
- 17:21Policy as Code
- 19:56Enabling Self-Service with Compliance
- 22:37Case Study: Financial Organization
- 24:25Implementation Roadmap
- 25:23Key Takeaways and Conclusion
related talks
29mPlatform engineering maturity - Your key to competitive differentiation
26mPlatform Engineering Loves Security: Shift Down To Your Platform, Not Left To Your Developers! - Maxime Coquerel, Royal Bank of Canada
15mThe Art of Platform Engineering
45mPlatform Engineering vs DevOps
39mPlatform Engineering as a (Community) Service
38mPlatform Engineering in the Age of AI Teammates
32mHow to win at platform engineering
25mPlatform Engineering: Evolution or a Fancy Rename?