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 limitations of SAST

While SAST can identify vulnerabilities early in the software development process, it can produce false positives and false negatives, has a limited scope, and is less effective against certain types of vulnerabilities. SAST should be used in combination with other security testing techniques to ensure that software applications are secure and resilient against security risks.

Here are some of the key limitations of SAST:

  • False positives: SAST tools can produce false positives, which are security vulnerabilities that are reported by the tool but do not exist in the code. False positives can be time-consuming to remediate as they require additional analysis and can take resources away from more critical vulnerabilities.
  • False negatives: SAST tools may miss actual vulnerabilities, leading to a false sense of security.
  • Limited context: SAST tools analyze application source code in isolation, without considering how the code interacts with other...