Decrease Your Stress and Increase Your Reach with Appsec Champions
summary
Argues for an appsec champions program with concrete prerequisites (a budgeted roadmap, a written role description, a secret list) and a workflow: biweekly meetings, Slack/wiki training, JIRA ticket ownership and video calls for remote rapport. Claims each appsec engineer can manage about six champions per appsec engineer, shows rewards that work (conference passes, quarterly lunches, stickers, even a $75 annual shield award), and reports measurable results: faster fixes within SLA, fewer 2am incidents, and sustained roadmap progress when security staff are absent.
AI-written summary · about
chapters (6)
- 0:00Introduction and overview
- 2:18The case for security champions
- 7:31Key program elements
- 14:36Managing developer engagement
- 17:48Incentives and rewards
- 27:03Conclusion and wrap-up
related talks
28mData-Driven AppSec Champions Programs – Benchmarking Your Program with Numbers
01h 01mSecurity Champion Worst Practices
32mSecurity Champions? Introduce them in your Organisation
27mSecurity Champions: The What, Why, and How
48mGrowing A Security Champion Program Into A Security Powerhouse
51mBuilding Security Champions
38mChampioning Security for your Agile Development
44mFrom Rogue One to Rebel Alliance: Building Developers into Security Champions