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 benefits of SCA

SCA tools offer multiple advantages, including bolstering the security of third-party code, ensuring legal compliance with licensing, providing timely updates for vulnerabilities, and streamlining the process of identifying potential threats, all of which grant developers peace of mind. However, they’re not without drawbacks. These tools can sometimes raise unnecessary alerts and may be complex and intimidating for new users. It’s not that SCA tools “don’t always” cover custom-written code; they primarily focus on third-party components. For custom-written code, other tools such as static application security testing (SAST) are more appropriate. It can be a financial strain for some and might face compatibility issues with certain development processes or tools.

Advantages:

  • Safety first: Imagine that your software is a house. SCA tools are like security checks that make sure you’re not unknowingly using bricks...