Rise of Risk Ops teams - A solution for reducing cognitive load on DevOps teams.
summary
At ING a dedicated RiskOps enabling team takes ownership of monitoring, evidencing and tooling so DevOps stops juggling audits and fixes. Implementation follows Team Topologies practices, introduces automation and policy as code / compliance as code, and delivers measurable wins: 70% reduction in evidence load, 30% faster vulnerability remediation and 100% internal/external audit satisfaction. The team runs for 18 months, nudges automation into SDLC and shifts risk management from reactive to proactive.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:48Agenda
- 2:32RiskOps health checks
- 5:03What is RiskOps
- 7:10RiskOps in team structures
- 7:51Cognitive load in DevOps
- 10:17Team topologies
- 11:18Enabling teams in RiskOps
- 12:44Pain points before RiskOps
- 16:57Results after RiskOps
- 19:26Key achievements
- 21:34Implementing RiskOps
- 24:44Future of RiskOps
- 26:30Q&A
related talks
49mAt What Point Does DevSecOps Become Too Risky for the Business?
29mAn Unlikely Happy Couple - DevOps and IT Audit?
45m200 Teams, 1 Goal: DevOps Maturity at Scale
47mWhere the Security Rubber Meets the DevOps Road
43mBringing product thinking into DevOps
21mDevOps in a Highly Regulated Financial Infrastructure Company
39mDevOps: The Return of Security
22mDevOps in Regulated Industries: What to do when Internal Audit says ‘No!’