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

Detection of security flaws

SCA tools are primarily focused on detecting vulnerabilities in open source and third-party components. However, it’s important to understand that while SCA tools are a crucial part of the software security landscape, they specifically cater to the threats posed by the reuse of external components. Here’s a deeper dive into how SCA tools detect security flaws:

  • Open source databases and repositories: SCA tools continuously monitor and pull data from popular vulnerability databases such as the NVD, as well as other sources such as security advisories, mailing lists, or even GitHub repositories.
  • Dependency analysis: SCA tools analyze the list of dependencies used in an application. This includes both direct dependencies (the ones you include explicitly) and transitive dependencies (dependencies of your dependencies).
  • Version checking: Once the tool knows which components and versions are being used, it checks them against its database...