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

What is SCA?

SCA is like a dedicated quality assurance team that covers security and compliance for your software’s ingredients. It ensures you’re building your software with the most up-to-date, safest, and compliant components available. This not only ensures a better end product but also saves you from potential headaches, be they security breaches or legal battles, down the road.

Unlike in cooking, in software, using outdated or vulnerable components can have severe outcomes. Imagine you’re a chef preparing a large banquet. While you may grow some of your ingredients in your backyard garden (equivalent to the custom code you write), you’re also sourcing many ingredients from various markets and suppliers (akin to third-party or open source components). Now, just as you’d want to ensure that every ingredient is fresh, free from contamination, and ethically sourced, in software, you want to ensure every component is secure, updated, and compliant...