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

Challenges within the DevSecOps pipeline that principles can resolve

With Dev, Ops, and Sec, we’ve got a lot of hands touching the code. This could create chaos, but DevSecOps makes sure everyone’s working from the same recipe. Shared responsibility means less finger-pointing and more high-fiving. Traditional models often slap on security measures at the end, making it a frantic game of catch-up. DevSecOps principles such as shift left say, “Why wait?” By baking security in from the get-go, you’re not just avoiding a disaster – you’re planning for success.

No one likes to be bogged down by bureaucratic procedures when you’re trying to move fast. DevSecOps helps by automating security protocols. This means you can sprint without tripping over paperwork. Also, the Dev team and the Sec team sometimes seem like they’re speaking different languages. DevSecOps bridges this gap, turning that miscommunication into a harmonious...