AI-Driven Security as Code in Jenkins
summary
Claims that Jenkins pipelines run SAST SCA DAST and container scans with policy as code and secret management, catching vulnerabilities 17× faster and surfacing ~26 findings per KLOC, enabling developers to fix 77% of security issues before escalation. Cites a 94% drop in misconfigurations, container scans preventing 60% of incidents, costs from ~$25 in design to ~$75,000 in production (a ~3,000× gap), and rollout metrics showing 57% fewer critical vulns after adoption.
AI-written summary · about
chapters (12)
- 0:00Introduction to Con 42 and Speaker Background
- 0:48The Importance of Security as Code
- 3:01Challenges in Balancing Speed and Security
- 4:07Impact and Benefits of Security as Code
- 5:25Foundations and Principles of Security as Code
- 7:12Economic Benefits of Early Security Integration
- 8:36Implementing Security in Jenkins Pipelines
- 12:01Organizational Transformation with Security as Code
- 13:44Challenges in Implementing Security as Code
- 15:43Adoption Journey of Security as Code
- 17:59Future of Security as Code
- 20:08Conclusion and Thank You
related talks
39mContinuous Security at the Next Level
14mHow Security as Code Transforms Platform Engineering at Scale
43mSecurity in DevOps Strategies
19mApplication Security at High Velocity
43mBuilding a Secure DevOps Pipeline
32mAutomating Security Compliance at Scale
25mPaC in Jenkins for DevOps Pipelines
40mDevSecOps Guide to Bulletproof Your Development Workflow