Who Hurt You? Earning the trust of developers
summary
Argues that developer buy‑in is the linchpin: trust shortage creates attrition, slows innovation, and blocks fixes; specific fixes include secret scanning and rotate secrets as quick wins, buying a stack analysis tool with developers, running security champions and hands‑on training via Sura Academy, doing security architectural reviews and shifting left, measuring progress with data plus stories, and closing the feedback loop; reports a real outcome of faster remediation and higher engagement and even 5,000 YouTube subscribers for ongoing outreach.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:35Buy-in for security
- 7:36Cost of broken trust
- 15:46Building trust with devs
- 26:57Earning developer buy-in
- 36:27Conclusion
- 39:16Q&A
related talks
27mDevelopers Struggle with Application Security (and How to Make ...)
52mLeveraging Psychological Needs For Building A Security Culture Amongst Developers
20mHow to Use Your Vulnerabilities to Train Your Developers on Security
40mDevelopers Dislike Security: Ten Frustrations and Resolutions
31mPrioritizing Trust while Creating Applications
01h 04mShifting Security Everywhere
38mPrioritizing Trust While Creating Applications
20mThe road to developers' hearts