Automating Enterprise/Industry Regulation Enforcements During Software Delivery
summary
Shows a working integration of OPA policies with Spinnaker that enforces real compliance checks: pipeline stages require two-person approvals for production, block deploys if image scans show critical or high vulnerabilities, and prevent pipeline edits unless changes come from an approved GitOps flow. Uses an OPA server plus a small provenance database for artifact origin checks and a Clouddriver plugin for admission control; demoed pipelines enforce and audit the policies though full provenance workflows run outside Spinnaker.
AI-written summary · about
chapters (9)
- 0:00Automating regulation enforcement
- 2:07Drivers for security compliance
- 5:15Challenges in automation
- 7:22Security in delivery pipelines
- 13:02Admission control for security
- 16:34Defining compliance policies
- 17:57Policy pipeline examples
- 21:22Summary and demo
- 22:04Q&A
related talks
33mAutomating Industry Regulation (SoX, SoC 2) Enforcement...
20mUsing OPA to Ensure Compliant Software Delivery in a Highly Regulated Finance Envi...
23mPolicy-driven Deployments in Spinnaker
29mHardening Spinnaker Pipelines
11mLightning Talk: Automating Industry Regulation (SoX, SoC...
18mDevOps All the Things: Creating a Pipeline to Validate Your OPA Policies
15mSecuring your Deployments using a Policy Driven Approach
40mOPA Introduction & Community Update
