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

Introducing chaos engineering

Chaos engineering has its roots in things such as safety engineering in contexts such as aerospace engineering, where structures and components are tested to just before the point of failure.

Chaos engineering can be applied to various systems, including IT infrastructure, software systems, and business processes. It is typically performed by injecting simulated failures or “chaos” into the system and observing how it responds.

This allows engineers to identify and fix problems before they cause a real-world loss or outage.

Several different techniques can be used to perform chaos engineering, including the following:

  • Randomly killing or failing processes or services
  • Introducing network delays or packet loss
  • Increasing or decreasing the system load
  • Removing or adding resources
  • Changing system configurations

A team of engineers usually conducts the process of chaos engineering, and it is often automated...