Organizations struggle with obtaining buy-in and implementing DevOps methodologies because security, compliance, and audit stakeholders (both internal and external) believe that change control requirements cannot be met. These stakeholders often tend to disrupt adoption of DevOps before an organization can explore its potential for implementation. In this paper, we will provide some high-level guidance on three major concerns about DevOps Practices: DevOps and Change Control, DevOps and Security, DevOps and Separation of Duties.
CHAPTER 1: DevOps & Change Control
CHAPTER 2: DevOps with Security: Secured Delivery Pipeline
CHAPTER 3: DevOps and Separation of Duties
James DeLucia, Director and Leader for Certification Services, EY Certify-Point
Paul Duvall, Chairman and CTO at Stelligent, Author of Continuous Integration and DevOps in AWS
Mustafa Kapadia, DevOps Service Line Leader, IBM Gene Kim, Author and Researcher
Dave Mangot, Director of Operations, Librato, Inc.
Tapabrata “Topo” Pal, Director, Next Generation Infrastructure, CapitalOne
James Wickett, Sr. Engineer, Signal Sciences Corp
Julie Yoo, Vice President, Information Security Compliance at Live Nation
Publication: October 1, 2015