PaC in Jenkins for DevOps Pipelines
summary
Claims that embedding Policy as Code into Jenkins pipelines catches misconfigurations early and prevents breaches, supported by concrete metrics: 60% of breaches stem from misconfigurations, 87% linked to human error, and an average recovery cost of $3.92M per breach. Implementation uses Open Policy Agent, Conftest, Sentinel, Terraform and Jenkins with pipeline gates that fail builds on critical violations, IDE and pull‑request checks for realtime feedback, and versioned policies in git so enforcement is auditable and rollbackable.
AI-written summary · about
chapters (16)
- 0:00Introduction to DevOps and Speaker Background
- 0:30The Importance of Security in DevOps
- 0:51Policy as Code: An Overview
- 1:16Challenges in DevOps Security
- 2:01Integrating Security in DevOps Pipelines
- 3:14Financial Impact of Security Incidents
- 4:03Understanding Policy as Code
- 5:30Policy as Code in the DevOps Lifecycle
- 9:33Why Jenkins for Policy as Code?
- 10:30Implementing Policy as Code
- 14:30Popular Policy Enforcement Tools
- 17:12Real-World Policy Examples
- 18:43Integrating Policy as Code in Development Workflows
- 21:35Pipeline Gates and Compliance Reporting
- 24:07Getting Started with Policy as Code
- 24:55Conclusion and Contact Information
related talks
20mAI-Driven Security as Code in Jenkins
27mCatch Me If You Can: Hunting Misconfigurations Before They...
29mAbusing CI/CD - Top Ways to Reach Production
48mInfrastructure-Agnostic Continuous Delivery
32mAutomating Security Compliance at Scale
39mContinuous Security at the Next Level
30mIntelligent Pipelines: Bringing AI/ML into DevSecOps Automation
26mProtect the Pipe! A Policy-based Approach for Securing CI/CD Pipe...