Integrating security into DevOps to deliver "DevSecOps" requires changing mindsets, processes and technology. Security and risk management leaders must adhere to the collaborative, agile nature of DevOps to be seamless and transparent in the development process, making the Sec in DevSecOps silent.
- Adapt Your Security Testing Tools and Processes to the Developers, Not the Other Way Around
- Quit Trying to Eliminate All Vulnerabilities During Development
- Focus First on Identifying and Removing the Known Critical Vulnerabilities
- Don't Expect to Use Traditional DAST/SAST Without Changes
- Train All Developers on the Basics of Secure Coding, but Don't Expect Them to Become Security Experts
- Adopt a Security Champion Model and Implement a Simple Security Requirements Gathering Tool
- Eliminate the Use of Known Vulnerable Components at the Source
- Secure and Apply Operational Discipline to Automation Scripts
- Implement Strong Version Control on All Code and Components
- Adopt an Immutable Infrastructure Mindset
Gartner Recommended Reading
©2020 Gartner, Inc. and/or its affiliates.
All rights reserved.
Gartner is a registered trademark of Gartner, Inc. and its affiliates.
This publication may not be reproduced or distributed in any form without Gartner’s prior written permission.
It consists of the opinions of Gartner’s research organization, which should not be construed as statements of fact.
While the information contained in this publication has been obtained from sources believed to be reliable, Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information.
Although Gartner research may address legal and financial issues, Gartner does not provide legal or investment advice and its research should not be construed or used as such.
Your access and use of this publication are governed by Gartner’s Usage Policy.
Gartner prides itself on its reputation for independence and objectivity.
Its research is produced independently by its research organization without input or influence from any third party.
For further information, see
Guiding Principles on Independence and Objectivity.