Book Image

Implementing DevSecOps Practices

By : Vandana Verma Sehgal
Book Image

Implementing DevSecOps Practices

By: Vandana Verma Sehgal

Overview of this book

DevSecOps is built on the idea that everyone is responsible for security, with the goal of safely distributing security decisions at speed and scale to those who hold the highest level of context. This practice of integrating security into every stage of the development process helps improve both the security and overall quality of the software. This book will help you get to grips with DevSecOps and show you how to implement it, starting with a brief introduction to DevOps, DevSecOps, and their underlying principles. After understanding the principles, you'll dig deeper into different topics concerning application security and secure coding before learning about the secure development lifecycle and how to perform threat modeling properly. You’ll also explore a range of tools available for these tasks, as well as best practices for developing secure code and embedding security and policy into your application. Finally, you'll look at automation and infrastructure security with a focus on continuous security testing, infrastructure as code (IaC), protecting DevOps tools, and learning about the software supply chain. By the end of this book, you’ll know how to apply application security, safe coding, and DevSecOps practices in your development pipeline to create robust security protocols.
Table of Contents (25 chapters)
1
Part 1:DevSecOps – What and How?
3
Part 2: DevSecOps Principles and Processes
8
Part 3:Technology
15
Part 4: Tools
17
Part 5: Governance and an Effective Security Champions Program
20
Part 6: Case Studies and Conclusion

How chaos engineering is different from other testing measures

Chaos engineering is like a stunt double for our systems. It takes on the tough, unexpected scenarios to see how our systems would react, so that when the real thing comes along, they’re ready to perform.

Here’s how it’s different from other testing measures:

  • Real-world conditions: Traditional testing often takes place in controlled, predictable environments. Think of it like practicing a dance routine in a spacious, mirrored dance studio. On the other hand, chaos engineering is like practicing that same routine on a crowded dance floor with spilled drinks and unpredictable dancers. It mimics the unpredictable, chaotic conditions of the real world to see how systems perform under stress.
  • Proactive, not reactive: Most testing methods are reactive – they identify bugs or problems after they’ve occurred, or they validate that a certain feature is working as expected. Chaos...