Controlled Chaos: The Inevitable Marriage of DevOps & Security
summary
Large-scale survey data shows elite teams optimize four metrics—lead time for changes, release frequency, change fail rate and time to restore (MTTR)—and are 23× likelier if they meet NIST cloud characteristics and 1.5× likelier on PaaS. Chaos engineering (Netflix Chaos Monkey, kube-monkey, Pumba, Chaos Lambda) plus game days shift security left, exercise resilience, and favor the DIE triad (distributed, immutable, ephemeral). A practical shift measures MTTR over MTBF, automates toil, bakes immutability/ephemerality into pipelines, and scales one-to-ten-to-one-hundred security input.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:39DevOps fundamentals
- 5:31Bridging DevOps and security
- 10:53Cross-functional roles
- 15:03Applying chaos engineering
- 23:08InfoSec metamorphosis
- 26:30Resilient security strategies
- 30:27The DIE model
- 35:05Metrics for success
- 40:23Testing and tooling
- 49:30Conclusion
related talks
26mBreaking Systems for Resilience
27mExecuting Chaos Engineering in Production at a Critical Financial Institution
23mHow to tame chaos effectively?
27mChaos Engineering: The Path to Reliability
21mThe Psychology of Chaos Engineering
29mThe Psychology of Chaos Engineering
40mNavigating the Unknowable: Resilience through Security Chaos Engineering
37mUse Chaos Testing to Build Resilience in the Software