Security Chaos Engineering
Sustaining Resilience in Software and Systems
Failed to add items
Add to basket failed.
Add to wishlist failed.
Remove from wishlist failed.
Adding to library failed
Follow podcast failed
Unfollow podcast failed
£0.00 for first 30 days
Buy Now for £17.99
No valid payment method on file.
We are sorry. We are not allowed to sell this product with the selected payment method
-
Narrated by:
-
April Doty
About this listen
Cybersecurity is broken. Year after year, attackers remain unchallenged and undeterred, while engineering teams feel pressure to design, build, and operate "secure" systems. Failure can't be prevented, mental models of systems are incomplete, and our digital world constantly evolves. How can we verify that our systems behave the way we expect? What can we do to improve our systems' resilience?
In this comprehensive guide, authors Kelly Shortridge and Aaron Rinehart help you navigate the challenges of sustaining resilience in complex software systems by using the principles and practices of security chaos engineering. By preparing for adverse events, you can ensure they don't disrupt your ability to innovate, move quickly, and achieve your engineering and business goals.
In this book, you'll learn how to design a modern security program; make informed decisions at each phase of software delivery to nurture resilience and adaptive capacity; understand the complex systems dynamics upon which resilience outcomes depend; navigate technical and organizational trade-offs that distort decision making in systems; explore chaos experimentation to verify critical assumptions about software quality and security; and learn how major enterprises leverage security chaos engineering.
PLEASE NOTE: When you purchase this title, the accompanying PDF will be available in your Audible Library along with the audio.
©2023 Aaron Rinehart and Kelly Shortridge (P)2023 Ascent AudioWhat listeners say about Security Chaos Engineering
Average customer ratingsReviews - Please select the tabs below to change the source of reviews.
-
Overall
-
Performance
-
Story
- Jason Marks
- 16-01-24
Older methodologies get a fresh coat of paint
I 'bought' this book using one of my Audible credits for the year as I found myself nodding in agreement with the synopsis and hungry to hear how this 'new' approach might enhance our lives in the cybersecurity space. I wasn't disappointed but neither was I enthralled by the content or pace of this, quite (virtually) hefty tome.
As an audiobook it may be that some of the volume's usefulness as a reference is lost, having said that, many books really don't make the transition to audio format nearly so well as this one, as there is a reasonable narrative and call to action which is consistent throughout the 18 hours plus of the presentation. In mentioning the length of the audiobook, it is fair to say that those familiar with the subject matter and comfortable with April Doty's clear American English narration will be able to happily run this at 1.5x speed without any loss of content or context,
The real-life reports of SCE in later chapters were useful, but could have been more substantial and used earlier in the 'text' to add flavour to the methods being described.
Personally, I found much of what is discussed and espoused as new 'chaos engineering' to be common sense, and have tried to practice over many years in the field, that said there is a lot to unpack. The foundations, as I understood the book to suggest, are to know what you are wanting to achieve with a system, understand the inputs, the upstream and downstream systems and ensure you have end-to-end visibility of transactions as they traverse these. Run use *and* misuse cases against the systems and check that you can see how these play out, make sure that the right way to use systems is clearly documented *and* referenced, so you can work both ways from any point in a complex system.
Even further distilled to it's essence, the book suggests:
Know what you are doing within a system, tell others what you are doing, show them the right way to use it (make it the easy way), test (and keep testing) the right AND wrong ways to use it, take all feedback with grace and try *really* hard not to break production - but if you do, be sure you can see why and how and use that learning to make it better.
A good book well worth consuming, thanks, Kelly, for putting together such a comprehensive guide.
Something went wrong. Please try again in a few minutes.
You voted on this review!
You reported this review!