Robert Ross CEO @ Firehydrant.com LinkedIn: https://www.linkedin.com/in/bobby-tables/ Imagine pulling the fire alarm on your team and throwing them into an incident response process they haven't prepared for. That's probably not too hard to imagine because it happens all too often. This talk dives into practical ways to use chaos engineering to stress test your incident response. ​ We’re pretty sure using a real incident to test a new response process is not the best idea. So, how do you test your process ahead of time? — 0:00 Intro 0:26 Who am I? 1:06 What are we talking about? 1:28 Quick overview of chaos engineering 2:14 Examples of chaos experiments 2:50 Process Experiments 3:39 So how do you run an experiment on process? 3:49 Surprise Meeting + What we learned 4:53 Do this for any common operation you do during an incident 5:32 People mitigate incidents, not processes 5:59 Guide, don't prescribe 6:50 Why this matters 7:24 Rearrange blocks for different scenarios 8:09 The bricks are boring 8:45 Example: marching band technique 9:32 Identify which techniques lack undestanding 13:15 Then practice them 14:15 What did we cover? 14:47 Thank you! — 🥇 Gold Sponsor: StackPulse 🥈 Silver Sponsors: Aval Digital Labs BoomerTechnologyGroup bxblue Certus Cybersecurity Chaos Native CrowdSec bol.com effx FireHydrant GoCardless Gremlin Locelle Nuaware PagerDuty Zühlke Group 7bulls.com 🤝 Media Partners: The New Stack Manning AWS Inside Dev — Website 🚀🪐 https://www.conf42.com Reach out 📧📭 mark@conf42.com Conf42 Discord 🧑‍🤝‍🧑💬 https://discord.com/invite/dT6ZsFJ5ZM LinkedIn 👨‍💼💼 https://www.linkedin.com/company/49110720/ Twitter 🎵🐦https://twitter.com/conf42com Conf42Cast @ Spotify 🎧 https://tinyurl.com/bnyj6a8y