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

Basic principles of chaos engineering

Ensuring the safety of systems during chaos engineering experiments is an essential aspect of the process. Here are a few ways that organizations can ensure the safety of their plans during chaos engineering experiments:

  • Establishing safety limits: Organizations should set safety limits for the tested systems before conducting any experiments. These limits should take into account the system’s expected behavior and should be used to stop an experiment if the system begins to suddenly behave unexpectedly.
  • Monitoring the system: Organizations should closely monitor the system during the experiment to detect unintended consequences and ensure that the system behaves as expected.
  • Rollback mechanisms: Organizations should have rollback mechanisms in place that can quickly restore the system to its previous state if an experiment begins to have unintended consequences.
  • Communication: Organizations should have clear communication...