Security Chaos Engineering for Fun and Profit
summary
Security Chaos Engineering (SCE) applies chaos experiments to verify preventive, detective and corrective controls across cloud layers, claiming layer‑agnostic visibility and empirical feedback. Examples include a public S3 bucket takeover test, a follow‑on bucket ransomware + backup recovery scenario, and an EKS pod to S3 lateral move that exposes gaps when CWPP and CSPM tools don’t correlate signals. Framework uses five pillars — execute, monitor, analyze, plan, knowledge — to turn failures into prioritized risk fixes.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:31Security Chaos Engineering
- 5:55Cloud Native Infrastructure is Complex
- 7:40Increasing Cloud Attacks
- 9:01Cloud Native Security Platforms
- 10:55Cloud Native Attack Surface
- 13:13Public Bucket Experiment
- 14:41Bucket Ransomware Experimente
- 16:18Advanced Ransome Experiment
- 18:31Risk Driven Fault Injection - Execute
- 19:56Risk Driven Fault Injection - Monitor
- 20:32Risk Driven Fault Injection - Analyze
related talks
43mCyber Chaos Engineering
40mSecurity & Chaos Engineering: Resilient Distributed Systems
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 ...
28mUnknown Unknowns + Chaos = Security Chaos Engineering
18mChaos Engineering: Break It On Purpose