Standardization & Security - A Perfect Match
summary
Northwestern Mutual standardizes a single SCM (migrating from GitHub Enterprise to GitLab) and narrows tool choices to a vetted set, then enforces a centralized pipeline that runs systic container scans, SBOM/bill-of-material checks and xray open-source vulnerability scans. The claim: consolidation cuts maintenance cost, reduces attack surface (supply-chain attacks rose 430%), improves developer fungibility and speeds delivery measurable by DORA metrics, with incentives and an exception process to allow safe innovation.
AI-written summary · about
chapters (15)
- 0:00Standardization & security journey
- 2:25Paradox of choice
- 7:22Tool proliferation causes
- 9:50From buffet to set menu
- 11:13Golden path for developers
- 13:19Enforcement carrots and sticks
- 14:25Choice vs developer productivity
- 16:09Tool selection criteria
- 18:16Case for boring tech
- 20:00Tools consolidation strategies
- 22:04Standardization vs innovation
- 24:31Incentives for innovation
- 25:37Centralized governance outcomes
- 28:02Lessons learned
- 31:30Q&A
related talks
11mKyle Persohn & Sean Corkum, Northwestern Mutual | GitLab Commit 2020
49mHow Lockheed Martin builds software faster, powered by DevSecOps
43mNorthwestern Mutual shifts left & shields right to stay secure on AWS
44mProtecting Customers Through Smarter OSS Management
19mApplication Security at High Velocity
52mManaging security with a unified strategy, featuring Nubank
38mDevOps Meet Sec: Your Journey To Delivering Secure Code Fast
33mOpen-Source Maturity in a 160-year-old organization: Technical and Legal hurdles
