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

The importance of SCA

In the intricate and interwoven world of software development, SCA tools act as vigilant guardians and advisors. They ensure that the components you’re weaving into your masterpiece are sound, safe, and compliant, helping to craft a final product that’s not only functional but also secure and legally unassailable.

Imagine you’re putting together a massive jigsaw puzzle. Each piece you add is a piece of code or a component you’re using in your software project. Some of these puzzle pieces you craft yourself (your custom code), but many you get from various sets (open source libraries or third-party components) because why reinvent the wheel, right?

Now, while using these pre-made pieces speeds things up and can bring in some fantastic artwork, there’s a risk: what if some of these pieces have defects, are outdated, or come with conditions on their usage? This is where SCA tools come into play. Let’s look at why they...