Putting Governance Into your DevOps Processes
summary
Argues that governance must be built into DevOps pipelines with continuous compliance not periodic audits, shows a live pattern for achieving 100% PCI DSS compliant workloads in containers by combining policy-as-code, role-based access controls, separation-of-duties checks and automated alerts. Demonstrates using Elasticsearch and Apache Spark for real-time visibility and anomaly detection, advocates just-in-time admin and reduced privileged lifetimes, warns automation helps but does not replace governance, and recommends third-party controls and encrypted telemetry for auditability.
AI-written summary · about
chapters (7)
- 0:00Introduction governance DevOps
- 1:49Compliance challenges in DevOps
- 5:51Visibility and security in cloud
- 10:11Risk management strategies
- 16:38Certification and lifecycle
- 20:17Monitoring and automation
- 22:00Q&A and conclusion
related talks
30mAutomating Governance - Dear Security, Compliance, & Auditors We’re Sorry. Love DevOps
31mWrangling Compliance in the Wild West of Software Delivery
01mWhat is DevGovOps?
33mCompliance Without the Chaos: Building It Right Into Your DevOps...
30mHandling Security Objections to DevOps
29mAn Unlikely Happy Couple - DevOps and IT Audit?
22mBridging Compliance and Innovation: A Guide for DevOps Leaders
28mImplementing Critical Cybersecurity Controls in a DevOps Environment
