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

Why should we perform threat modeling?

Threat modeling is an essential step in the software development and system design process, focusing on foreseeing and addressing potential vulnerabilities. Performing threat modeling has a myriad of advantages, and here’s why it should be integrated into the development life cycle:

  • Proactive approach to security: Rather than taking a reactive stance and waiting for vulnerabilities to be discovered or exploited, threat modeling allows you to anticipate potential threats and address them in advance.

    Example: Before deploying a web application, a threat model might identify that the application is susceptible to SQL injection. By catching this in the design phase, developers can write more secure code to prevent this well-known attack vector.

  • Cost-efficient: Addressing security issues early in the design or development phase is significantly cheaper than dealing with breaches or vulnerabilities after deployment.

    Example: If a major...