Standard Classification: Security Chaos Engineering - Turning the Tide in ...
summary
Claims that Security Chaos Engineering moves security from hope to measurable practice and demonstrates it with a working toolkit and experiments. Uses an open source framework chaoslinger (Python lambdas) against AWS by opening unauthorized ports, finds perimeter controls fail about 60% of the time, shows a cognitive configuration management tool reliably catches the change, and exposes a logging/siem gap where alerts lack environment metadata so fixes require added metadata to alerts to make detection operational.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:52Outline
- 1:22Background
- 2:03The Issue
- 2:36Complexity
- 5:51Software
- 6:41Chaos Engineering
- 7:01Legacy Systems
- 9:49System Engineering is Messy
- 11:14Security is a Context Dependent Discipline
- 12:38Testing and Experimentation
- 13:22Detecting Security Measures Fail
- 13:50What Happens During a Security Incident
- 14:27Chaos Engineering Definition
- 15:20Chaos Engineering Books
- 15:42Newsflash
- 16:12Security Kiosk Engineer
- 16:40Use Cases
- 18:26Response
- 19:43Chaosing
- 20:06Chaoslinger
related talks
43mCyber Chaos Engineering
40mNavigating the Unknowable: Resilience through Security Chaos Engineering
40mSecurity & Chaos Engineering: Resilient Distributed Systems
31mNavigating the Unknowable: Resilience through Security Chaos Engineering
28mBuilding Safety, Security and Resilience through Chaos
28mUnknown Unknowns + Chaos = Security Chaos Engineering
24mSecurity Chaos Engineering for Fun and Profit
29mSecurity-Focused Chaos Engineering - the Lasso for AI Security T...