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

Topics covered in this book

The following topics were covered in detail:

  • Threat modeling: Threat modeling is a proactive approach to identifying, understanding, and mitigating potential security threats. In the case of the government agency (GovAgency), threat modeling was used to determine the most likely and dangerous threats to their infrastructure. This helped them prioritize their security efforts and invest in the most effective countermeasures.
  • Software composition analysis (SCA): SCA is used to identify potential vulnerabilities in open source components of software. The IT company (TechSoft) heavily relied on SCA to ensure the open source components they used did not compromise their software’s security. It helped them keep track of all third-party components, their associated licenses, and known vulnerabilities.
  • SAST and DAST: SAST involves examining the source code for potential vulnerabilities, while DAST involves testing a running application for...