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

What is DAST?

DAST is a security testing process that evaluates a running application, typically a web application, in real time to detect vulnerabilities that could be exploited during its operation. Unlike static analysis, which examines application code without executing it, DAST focuses on the application’s behavior and data flow during its operation, often from an outsider’s perspective without visibility into the underlying code.

A DAST tool could be used to do the following:

  • Test for SQL injection vulnerabilities by sending specially crafted input to application forms or URL parameters to see if the app inadvertently executes those inputs as part of a SQL query. If it does, an attacker could potentially access, modify, or delete data from the database.
  • Check for cross-site scripting (XSS) by attempting to insert malicious scripts into inputs. If successful, when this input is reflected to a user without being properly sanitized, the script can run...