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

Case study 2

A large financial institution was in the process of building a new online banking application. The application was designed to give customers a convenient and secure way to manage their accounts and conduct online transactions. As part of their development process, they integrated SAST into their development pipeline to identify any potential security vulnerabilities in their code.

During one of their SAST scans, they discovered a critical vulnerability in their application code. The vulnerability was a remote code execution flaw that could allow an attacker to execute arbitrary code on the server hosting the application. If left unaddressed, this vulnerability potentially exposed sensitive customer data and allowed attackers to take control of the application and the underlying infrastructure.

Thanks to the early detection provided by SAST, the development team was able to quickly remediate the issue before deploying the application to production. They fixed the...