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 key functions of observability

Observability has three main pillars of success when it comes to finding and gaining measurements: logs, metrics, and tracing. Raw telemetry data from backend applications can be observed, however, it might not give us the complete picture of the systems that are operating in the backend. We need to understand the frontend application data as well as the backend application data to get a complete view of application performance. These three pillars can be extended. Let’s take a look:

  • Logs: Logs are generated from any activity that occurs in systems and applications (when configured properly). Logs can be in plain text or structured or unstructured form. Logs contain the minutest details about event activities, including timestamps and the context behind them.
  • Metrics: Metrics define the statistics and criteria to measure the aspects of an application. These could be based on the network, hardware, or infrastructure. They can also...