Cyber Chaos Engineering
summary
Security chaos engineering executes controlled experiments against live systems to reveal real failures not assumptions: an open source tool Chaos Slinger injects misconfigured ports via an AWS EC2 security group routine called PortSlinger and finds firewall detection only ~60% of the time, cloud-native config management blocks most changes, and alerts lack metadata so the SOC cannot trace incidents quickly. The team adds pointer metadata, automates daily non‑destructive endpoint tests, and converts surprises into baselines and measurable compliance.
AI-written summary · about
chapters (15)
- 0:00Cyber Chaos Engineering intro
- 2:00Why security systems fail
- 8:00Human factors in incidents
- 11:11What is chaos engineering
- 13:16Netflix Chaos Monkey story
- 16:43Security chaos basics
- 21:56Chaos Slanger demo
- 25:48Why security chaos matters
- 27:54Baselining and metrics
- 31:03Getting started with security chaos
- 34:30Critical alerts and false positives
- 37:42Gap hunting in controls
- 39:28Measuring security success
- 41:57Overcoming resistance
- 43:04Conclusion and resources
related talks
40mSecurity & Chaos Engineering: Resilient Distributed Systems
28mBuilding Safety, Security and Resilience through Chaos
31mNavigating the Unknowable: Resilience through Security Chaos Engineering
40mNavigating the Unknowable: Resilience through Security Chaos Engineering
23mStandard Classification: Security Chaos Engineering - Turning the Tide in ...
24mSecurity Chaos Engineering for Fun and Profit
28mUnknown Unknowns + Chaos = Security Chaos Engineering
47mSecurity Pre-Cognition