Unknown Unknowns + Chaos = Security Chaos Engineering
summary
Claims that security chaos engineering uncovers “unknown unknowns” by running controlled experiments with community tools like Litmus Chaos, Chaos Mesh and Chaos Monkey, starting in non‑prod and iterating toward production. Cites IBM 2020: 48% of breaches link to human error or misconfiguration. Concrete experiments include making an S3 public bucket readable, enabling anonymous orchestrator access, testing sudo in container execution and delete bash history to see whether detection and alerting catch them, then analyze results and harden controls.
AI-written summary · about
chapters (13)
- 0:00Security Chaos Engineering intro
- 2:10Complex systems resilience
- 4:59Failure and resilience factors
- 7:46Unknown unknowns defined
- 10:14Unknown unknowns and security
- 12:21What is Chaos Engineering
- 14:09Security Chaos explained
- 16:39Mind map for Security Chaos
- 19:31Applying Security Chaos
- 22:01Performing experiments
- 23:27Creating hypotheses
- 25:56Experiment examples
- 27:42Closing and Key Takeaways
related talks
40mNavigating the Unknowable: Resilience through Security Chaos Engineering
31mNavigating the Unknowable: Resilience through Security Chaos Engineering
43mCyber Chaos Engineering
23mStandard Classification: Security Chaos Engineering - Turning the Tide in ...
40mSecurity & Chaos Engineering: Resilient Distributed Systems
23mMaking Chaos Engineering Boring: Debunking Myths Hampering Adoption
21mThe Psychology of Chaos Engineering
24mSecurity Chaos Engineering for Fun and Profit