DevOps in a Highly Regulated Financial Infrastructure Company
summary
SIX moves from siloed ops to cross-functional teams while keeping full regulatory compliance by involving security, compliance and auditors from day one and negotiating concrete acceptable controls. Segregation of duties is enforced with dissemination of roles, break-glass procedures and immutable servers, automation replaces manual handoffs to improve audit trails, and a critical booking system uses an opt-in change list so continuous deployment runs but every high-risk change has recorded, reviewer-verified evidence.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:17What is SIX
- 3:10Whats special about SIX
- 3:45Why DevOps
- 7:28DevOps and regulatory requirements
- 12:14segregation of duty
- 14:00auditability
- 14:53key mechanism
- 16:17PCI
- 17:26Continuous Deployment
- 18:40Conclusions
related talks
22mDevOps in Regulated Industries: What to do when Internal Audit says ‘No!’
44mDevOps in Regulatory Spaces: It's Only 25% What You Thought It Was…
46m360 ° DevSecOps Enterprise Adoption
21mSecure and Fast into Production — Modern Software Development in Regulated Environments
48mDesigning a Secure Software Development Lifecycle with DevOps
23mBackbone of the Swiss Financial Center Goes DevOps
37mDevOps - The Automation of Compliance
48mWhen DevOps Meets Regulation: Integrating 'Continuous' with 'Government'