Dear Security, Compliance, and Auditors, We’re Sorry. Love, DevOps.
summary
Argument: governance is the current delivery bottleneck and must be turned into autonomous governance where machines execute policy while humans codify it. Demo uses Maven test outputs, SonarQube-style scans, Nexus storage and sigstore signatures, with an upstream called plygos (step-runner) to serialize evidence, attest it and evaluate policies (OPA-style). He shows math: 0.98^5 ≈ 0.90 and batching 25 items drops success to ~60%, builds runnable pipelines that store signed governance contracts in Nexus and proves the approach works.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:35Modernizing Governance Capabilities
- 7:04Chapter Seven the Auto Evolution of Automation at Google
- 12:28Agenda Today
- 18:31Enabling Constraints
- 22:36Achieve Continuous Verification
- 24:55Governance Concept of a Governance Contract
- 28:16How Was this Governance Contract Created
- 38:06What if Your Change Approval Board Became a Modern Governance Platform Team
related talks
30mAutomating Governance - Dear Security, Compliance, & Auditors We’re Sorry. Love DevOps
36mKeynote - Automated Governance
33mAutomating Industry Regulation (SoX, SoC 2) Enforcement...
07mWe're Sorry, Love DevOps
33mGoverning the Ungovernable: Security and Compliance for AI Agents in Open Source Projec...
32mReimagining Trust in Software Releases: A New Approach to Supply Chain Integrity (Part 2)
01mWhat is DevGovOps?
42mThe Data Behind DevSecOps: The Power of Hindsight to Protect your Supply Chain