Titans of Scale: Strategies to Scale Security in Expanding Organizations
summary
Panelists describe concrete wins and failures: a democratized vulnerability management flow that routes SLA extension approvals to directors/VPs and cuts P1 remediation from six weeks to 1.5, a failed attempt to scale self-service threat modeling beyond ~200 engineers (training works at 150–200 but not for thousands), a built service-to-service OAuth and high‑performance vault replacement for secrets that finally deliver secure defaults, and internal tools that aggregate app facts to avoid 14,000 noisy tickets and surface fixes in GitHub where developers actually act.
AI-written summary · about
chapters (9)
- 0:00Introductions and welcome
- 1:30Panelist introductions
- 3:11Challenges in scaling security
- 6:58Lessons from program failures
- 13:26Centralized vs decentralized
- 20:04Hiring and team structure
- 24:14Managing toxicity at scale
- 31:22Security as a bottleneck
- 35:52Tools for success
related talks
41mPanel Discussion: Foundations of Security and Leadership at Scale
38mKeynote: Dumping Traditional Security Teams
23mScalable security: how to win friends and not burn...
58mBalancing Security and Agility While Scaling Your Company
54mSDL at Scale: Growing Security Champions
57mBuilding a Modern Security Engineering Organization
24mBeing secure by design: Engineer-led security
51mBuilding Security Champions