Growing A Security Champion Program Into A Security Powerhouse
summary
A security champions program grows from hobby to measurable engine by the specifics: a dashboard for one‑per‑10 engineers, automated onboarding and quarterly JIRA tickets, and behavioral nudges and boosts to drive tool use. Open‑source scanning with Checkov shows champions reach 34% adoption while only onboarding 18% of repos, scaling from 51 to 116 deputies in three months. Time to patch drops from two weeks to 48 hours on a critical misconfiguration, producing $15,000 saved and proving value for deputy paranoids.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:00How many companies have a security Champions program
- 2:30What are security Champions
- 6:04Our love for security
- 6:45Our security champions program
- 8:33The evolution of a program
- 10:05Building a Powerhouse
- 12:44How We Acted
- 18:03Executive Sponsorship
- 21:29Optimization In Maturity
- 23:25Value Case Studies
- 25:31Proof of Concept
- 27:38Baseline Scanning
- 33:18Conclusions
- 35:19Summary
- 36:48Questions
- 38:06Research Approach
- 40:38Leadership Buyin
- 43:53Financial Rewards
- 45:46BiWeekly Meetings
related talks
51mBuilding Security Champions
32mBeyond training: Building a high-impact security champions program
27mSecurity Champions: The What, Why, and How
36mChampioning Security: Scaling Security at Every Level
35mSDL at Scale: Growing Security Champions
37mBuilding Security Champions
38mChampioning Security for your Agile Development
49mTransforming Security Champions