Building Resilient Security Log Pipelines with Chaos
summary
Applies Chaos Engineering to security log pipelines by injecting controlled failures into specific streams (for example Okta, Duo, AWS and syslog agents) and observing knock‑on effects so hidden single points of failure surface. Recommends monitoring for 10 minutes of silence during business hours (longer off hours), using tools like Chaos Monkey/Simian Army and running experiments in a lab before prod. Notes need for existing monitoring, higher risk appetite, and benefits for mature teams with alerting automation.
AI-written summary · about
chapters (5)
related talks
40mNavigating the Unknowable: Resilience through Security Chaos Engineering
28mBuilding Safety, Security and Resilience through Chaos
54mControlled Chaos: The Inevitable Marriage of DevOps & Security
43mCyber Chaos Engineering
31mNavigating the Unknowable: Resilience through Security Chaos Engineering
28mUnknown Unknowns + Chaos = Security Chaos Engineering
27mExecuting Chaos Engineering in Production at a Critical Financial Institution
37mUse Chaos Testing to Build Resilience in the Software