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

Continuous Integration and Continuous Deployment

CI/CD stands for continuous integration/continuous deployment/delivery. While CI automatically releases every change to production, CD ensures changes are production-ready but may require a manual step for deployment. It is a software development practice that involves frequently integrating code changes into a central repository and then automatically building and deploying those changes to a test or production environment.

CI is the practice of regularly merging code changes into a shared repository, where automated tests are run to catch any issues that may have been introduced.

CD is the practice of automatically deploying code changes that pass all tests to a production environment. A CI/CD pipeline automates the process of testing, building, and deploying software changes; it helps catch and fix errors early, reduces the risk of introducing bugs, and improves the overall software quality.

We will cover the following topics...