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

DevSecOps principles

DevSecOps practices concentrate on splitting down silos, enhancing collaboration, and, last but not least, changing security to integrate it early in the development process before moving on to production. Let’s deep dive into some key principles of DevSecOps:

  • Unifying the CI/CD pipeline
  • Fail fast automation
  • Empowering teams to make decisions
  • Cross-skilling and educating teams
  • Proper documentation
  • Relevant checkpoints
  • Building and managing secure dev environments and toolchains

Let’s look at them in detail.

Unifying the CI/CD pipeline

The sooner we can unify the CI/CD pipeline’s needs, the earlier we can enforce security controls. At the same time, we should ensure we understand what is needed in the whole pipeline – that is, tools, technology, and processes. We need to have appropriate controls in place for the pipeline and make sure everyone is aligned with them.

Teams should not bring...