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

IaC security best practices

Ensuring security within IaC is paramount as it directly affects the provisioning and configuration of resources. Here are some detailed IaC security best practices and examples:

  • Use secret management systems

    Do not hardcode secrets or sensitive information in your IaC scripts. Instead of embedding API keys or database passwords in your Terraform script, use tools such as AWS Secrets Manager, HashiCorp Vault, or Azure Key Vault to fetch them at runtime.

  • Keep IaC configurations in version control

    Use version control systems (such as Git) to track changes, audit modifications, and roll back if necessary. Use Git branches to represent different environments. A pull request can act as a gateway for changes, ensuring peer review before deployment.

  • Regularly audit and update dependencies

    Periodically review and update modules, plugins, or dependencies your IaC scripts rely on. If using Terraform, you can use terraform init to see if newer versions...