The Six Pillars of DevSecOps - Pragmatic Implementation
Released: 12/14/2022
Organizations have a wide array of tools and solutions to choose from when implementing security into the software development process. They often end up procuring solutions that are hard to deploy or challenging to operationalize and observe. Instead, using a framework-agnostic DevSecOps model that focuses on application development and platform security allows organizations to approach security in DevOps pragmatically.
This publication outlines the practices, processes, and technologies that organizations should consider when building out any DevSecOps program. Readers will learn how to implement DevSecOps pragmatically, focusing on security covering all software, regardless of where it runs.
Key Takeaways:
- The different role profiles to consider during DevSecOps adoption
- Some of the common mistakes made when designing a DevSecOps team structure
- How culture impacts velocity and performance
- The characteristics of an optimized and productive culture
- Which technologies and processes underpin the pragmatic implementation of DevSecOps
- Considerations for various activities across all stages of the DevSecOps process, including threat modeling, developer training, security unit testing, penetration testing, GitOps, secrets and key management, chaos engineering, and much more
This publication is part of an entire series on the Six Pillars of DevSecOps. You can find all the papers in the series that have been released so far here.
Best For:
- CISOs
- Application, platform, and security engineers/architects
