GitOps and CDevents that helps me get compliant? Really??
summary
Claims that GitOps plus CD Events enforce automated compliance across releases and proves it with an audit trail; the prototype wires Git commits to generic pipelines, a broker syncs results, and pipelines record policy outcomes and an SBOM before production. Examples use SonarQube, IQ Server and common scanners, validate 17 control chapters, and produce a notarized SBOM and report. The build returns investment in about five months and operators use parameter templates to decide which checks run per deploy. CD Events + GitOps synchronization 17 control chapters notarized SBOM ≈5 months ROI
AI-written summary · about
chapters (19)
- 0:00GitOps and CD Events for compliance
- 1:28Why GitOps and CD Events matter
- 3:21Evolution of software delivery
- 10:13From prescriptive to configurable
- 12:25Security and compliance challenges
- 17:10ROI for compliance automation
- 18:11CD Events and compliance role
- 21:07GitOps principles for infra
- 23:35Three stages in delivery chain
- 24:37Execution and validation phases
- 26:21Compliance templates and files
- 27:22Single source of truth for audit
- 29:54Security pipeline demo
- 33:09Building the software bill of materials for compliance
- 36:05Sync pipelines with CD Events
- 36:52Understanding SBOM
- 39:47Lessons from compliance automation
- 43:25First steps to compliance
- 46:00Q&A
related talks
47mGitOps - Using Git as your source of truth for build, deploy and observability
10mGitOps and the CD Pipeline - Friend or Foe?
30mThe Intersection of CD Gates and GitOps: A Match Made in Deployment Heaven
23mUsing CD Events to Capture End to End Application Security Posture
21mContinuous Delivery: The Missing Piece in the GitOps-OCI Security Puzzle
39mKeynote: Bridging The Gap: CDF & GitOps Communities In Collaboration
33mCompliance Without the Chaos: Building It Right Into Your DevOps...
37mDevOps - The Automation of Compliance