In this episode, we brought in two exceptional guests that are no stranger to chaos. In fact, they've identified ways to engineer for chaos. In the studio, we have Aaron Rinehart, CTO, and founder at Verica. We also have Jamie Dicken, former manager of applied security at Cardinal Health and current director at Resilience. These two are also authors of Security Chaos Engineering. If you haven't read that book it's already out, you should check it out. 
Chaos engineering is the technique of introducing turbulent conditions into a distributed system to try to determine the conditions that cause it to fail before it actually fails. So they simplify it. What we do with chaos engineering is learn about the system without experiencing the pain of an outage or an incident. You learn to trust your gear by testing.
The biggest impact really came once we understood how security chaos engineering fits into the bigger security picture. It's not about just being a part of the latest and greatest techniques and having the excitement of doing something that's cutting edge, but security chaos engineering at the end of the day. It's useless unless what you've learned drives change. 
 
Key Takeaways:
0:00 Previously on the show
1:40 Aaron Rinehart and Jamie Dixon introduction 
2:08 Episode begins
2:59 What Jamie and Aaron are doing today
3:13 What Jamie is doing
4:13 What Aaron is doing
5:00 Discuss chaos engineering
9:26 Importance of chaos engineering
10:16 Myths of chaos engineering
12:55 Chaos engineering customer impacts
17:34 Learning to trust the test and end result
19:03 Reader and customer feedback
22:21 Chaos engineering gone wrong
27:39 Implementing change in cybersecurity
28:11 Building a team of experts
39:08 Getting involved in chaos engineering 
41:09 Tools for listeners
43:25 Keeping up with Aaron and Jamie
 
 
<a href='https://twitter.com/aaronrinehart'>Aaron Rinehart on Twitter</a>
<a href='mailto:aaron@verica.io'>aaron@verica.io</a>
<a href='https://twitter.com/jamie_dicken'>Jamie Dicken on Twitter</a>
<a href='https://www.linkedin.com/company/vericaio/'>Verica on LinkedIn</a>
<a href='https://www.verica.io/sce-book/'>Verica Free Book </a>
<a href='https://hackervalley.com/'>Learn more about Hacker Valley Studio</a>
<a href='https://www.patreon.com/hackervalleystudio'>Support Hacker Valley Studio on Patreon</a>
<a href='https://twitter.com/TheHackerValley'>Follow Hacker Valley Studio on Twitter</a>
<a href='https://twitter.com/ronaldeddings'>Follow Ron Eddings on Twitter</a>
<a href='https://twitter.com/chriscochrcyber'>Follow Chris Cochran on Twitter</a>
<a href='https://www.axonius.com/'>Sponsored by Axonius</a>

In this episode, we brought in two exceptional guests that are no stranger to chaos. In fact, they've identified ways to engineer for chaos. In the studio, we have Aaron Rinehart, CTO, and founder at Verica. We also have Jamie Dicken, former manager of applied security at Cardinal Health and current director at Resilience. These two are also authors of Security Chaos Engineering. If you haven't read that book it's already out, you should check it out. 
Chaos engineering is the technique of introducing turbulent conditions into a distributed system to try to determine the conditions that cause it to fail before it actually fails. So they simplify it. What we do with chaos engineering is learn about the system without experiencing the pain of an outage or an incident. You learn to trust your gear by testing.
The biggest impact really came once we understood how security chaos engineering fits into the bigger security picture. It's not about just being a part of the latest and greatest techniques and having the excitement of doing something that's cutting edge, but security chaos engineering at the end of the day. It's useless unless what you've learned drives change. 
 
Key Takeaways:
0:00 Previously on the show
1:40 Aaron Rinehart and Jamie Dixon introduction 
2:08 Episode begins
2:59 What Jamie and Aaron are doing today
3:13 What Jamie is doing
4:13 What Aaron is doing
5:00 Discuss chaos engineering
9:26 Importance of chaos engineering
10:16 Myths of chaos engineering
12:55 Chaos engineering customer impacts
17:34 Learning to trust the test and end result
19:03 Reader and customer feedback
22:21 Chaos engineering gone wrong
27:39 Implementing change in cybersecurity
28:11 Building a team of experts
39:08 Getting involved in chaos engineering 
41:09 Tools for listeners
43:25 Keeping up with Aaron and Jamie
 
 
<a href='https://twitter.com/aaronrinehart'>Aaron Rinehart on Twitter</a>
<a href='mailto:aaron@verica.io'>aaron@verica.io</a>
<a href='https://twitter.com/jamie_dicken'>Jamie Dicken on Twitter</a>
<a href='https://www.linkedin.com/company/vericaio/'>Verica on LinkedIn</a>
<a href='https://www.verica.io/sce-book/'>Verica Free Book </a>
<a href='https://hackervalley.com/'>Learn more about Hacker Valley Studio</a>
<a href='https://www.patreon.com/hackervalleystudio'>Support Hacker Valley Studio on Patreon</a>
<a href='https://twitter.com/TheHackerValley'>Follow Hacker Valley Studio on Twitter</a>
<a href='https://twitter.com/ronaldeddings'>Follow Ron Eddings on Twitter</a>
<a href='https://twitter.com/chriscochrcyber'>Follow Chris Cochran on Twitter</a>
<a href='https://www.axonius.com/'>Sponsored by Axonius</a>

hacker-valley-blue.podbean.com/efde3daf-184d-33a2-a9ea-8dcebd6775d4

In this episode, we brought in two exceptional guests that are no stranger to chaos. In fact, they've identified ways to engineer for chaos. In the studio, we have Aaron Rinehart, CTO, and founder at Verica. We also have Jamie Dicken, former manager ...

In this episode, we brought in two exceptional guests that are no stranger to chaos. In fact, they've identified ways to engineer for chaos. In the studio, we have Aaron Rinehart, CTO, and founder at Verica. We also have Jamie Dicken, former manager of applied security at Cardinal Health and current director at Resilience. These two are also authors of Security Chaos Engineering. If you haven't read that book it's already out, you should check it out. 
Chaos engineering is the technique of introducing turbulent conditions into a distributed system to try to determine the conditions that cause it to fail before it actually fails. So they simplify it. What we do with chaos engineering is learn about the system without experiencing the pain of an outage or an incident. You learn to trust your gear by testing.
The biggest impact really came once we understood how security chaos engineering fits into the bigger security picture. It's not about just being a part of the latest and greatest techniques and having the excitement of doing something that's cutting edge, but security chaos engineering at the end of the day. It's useless unless what you've learned drives change. 
 
Key Takeaways:
0:00 Previously on the show
1:40 Aaron Rinehart and Jamie Dixon introduction 
2:08 Episode begins
2:59 What Jamie and Aaron are doing today
3:13 What Jamie is doing
4:13 What Aaron is doing
5:00 Discuss chaos engineering
9:26 Importance of chaos engineering
10:16 Myths of chaos engineering
12:55 Chaos engineering customer impacts
17:34 Learning to trust the test and end result
19:03 Reader and customer feedback
22:21 Chaos engineering gone wrong
27:39 Implementing change in cybersecurity
28:11 Building a team of experts
39:08 Getting involved in chaos engineering 
41:09 Tools for listeners
43:25 Keeping up with Aaron and Jamie
 
 
Aaron Rinehart on Twitter
aaron@verica.io
Jamie Dicken on Twitter
Verica on LinkedIn
Verica Free Book 
Learn more about Hacker Valley Studio
Support Hacker Valley Studio on Patreon
Follow Hacker Valley Studio on Twitter
Follow Ron Eddings on Twitter
Follow Chris Cochran on Twitter
Sponsored by Axonius

Learning Through Chaos Engineering with Aaron and Jamie

Apple

Google

Spotify

Amazon

Exploring the defensive side of cybersecurity through the eyes of the experts and innovators.