DevOps: You Build It, You Secure It
summary
Argues that DevOps must add security across the pipeline with concrete practices: threat modeling, static analysis in CI, dynamic pen testing, IDE vulnerability plugins, image and secret scanning, and policy-based container images (example: Twistlock). Cites surprising metrics: 30x cheaper in dev to fix a vuln, $5M average breach cost, and test scale rising from 75M to 150M automated tests/day; gives real kill‑chain examples (Struts → default Jenkins → exposed S3) and a loan site that shut down to patch.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 1:51The origins of DevOps
- 3:50Defining DevOps culture
- 5:45Culture, speed, and resilience
- 9:06Lessons from Toyota
- 12:05Integrating security
- 15:35A holistic approach
- 20:06DevSecOps implementation
- 28:02The human element
related talks
39mDevOps: The Return of Security
34mDevSecOps: How to Use DevOps to Make You More Secure
27mDevSecOps: How to Use DevOps to Make You More Secure
30mHandling Security Objections to DevOps
27mMulti Security Checkpoints on DevOps Platform
38mDevOps Meet Sec: Your Journey To Delivering Secure Code Fast
01h 02mDevSecOps for Developers: How To Start
45mDevSecOps : add Security to your DevOps!