Security & Chaos Engineering: Resilient Distributed Systems
summary
Security Chaos Engineering applies failure injection to validate real controls rather than hope. It shows a Lambda-based, opt-in framework (Chaoslinger / portslinger) with three functions — generator, slinger, tracker — that inject misconfigured ports and trace detection. A real run finds firewall detection succeeds only about 60% while a cloud config tool catches it 100%; logging and SIM context gaps stop analysts from acting. Use cases: continuous control validation, measured incident response drills, and discovering missing observability before adversaries exploit it.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:31Agenda
- 1:21About Aaron
- 2:40The Problem
- 3:16Complexity
- 5:06Visceral
- 10:06Systems Engineering
- 13:59How do we discover when our security measures fail
- 16:35Chaos Engineering
- 20:20Security Chaos Engineer
- 22:59Use Cases
- 25:16Instant Response
- 26:55ChaosSlinger
- 27:54Example Portslinger
- 28:45Chaoslinger
- 31:27Ask better questions
- 31:58Chaos vs penetration testing
- 36:22AI tools
related talks
43mCyber Chaos Engineering
40mNavigating the Unknowable: Resilience through Security Chaos Engineering
28mBuilding Safety, Security and Resilience through Chaos
31mNavigating 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
29mSecurity-Focused Chaos Engineering - the Lasso for AI Security T...