DevOps: The Return of Security
summary
Claims that adding security into DevOps boosts outcomes (up to ~20% faster time to market) and that one security person for 100 developers plus 10 ops is a bottleneck. Shows concrete controls: pipelines with static and dynamic analysis, secret rotation via Azure Key Vault, infrastructure and configuration as code using ARM templates. Recommends CI checks, dependency scans, fuzzing, periodic pen tests, role‑based just‑in‑time access and automated runbooks for blocking attacks; examples of failures and fixes on staging vs production.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 3:57DevOps process overview
- 8:38Security bottlenecks in DevOps
- 12:30Security as code and configuration
- 19:16Integrating security in DevOps workflow
- 23:07Security testing in CI/CD
- 29:30Post-deployment security monitoring
- 35:11Access management and data security
- 38:05Closing remarks and thanks
related talks
25mKeynote: DevOps - The Return of Security
31mDevOps: You Build It, You Secure It
01h 02mDevSecOps for Developers: How To Start
06mDevSecOps – Security Throughout the DevOps Pipeline
34mDevOps and Security: The Facts, The Myths, The Legend
27mDevSecOps: How to Use DevOps to Make You More Secure
34mDevSecOps: How to Use DevOps to Make You More Secure
30mHandling Security Objections to DevOps