The Six Developers You'll Meet in Security: Why Secure by...
summary
Central claim: the "average developer" is fictional and security fails unless interventions target real behavioral barriers. Presents a six‑persona framework SECUR-E (Skeptic, Enthusiast, Compliant, Unaware, Resistant, Embedded) derived from a 28‑person study and mapped to the behavioral model COM‑B (Capability, Opportunity, Motivation). Recommends specific fixes: reduce scanner noise, pair an embedded engineer with the unaware, create champion roles for enthusiasts, and map the top three controls to persona barriers, then measure persona shifts over 3–18 months.
AI-written summary · about
chapters (8)
- 0:00Security program challenges
- 3:52Average developer problem
- 7:47Secure E framework
- 10:19Six developer personas
- 16:29Resistant and embedded personas
- 20:25Tailored security interventions
- 24:03Sustainable security culture
- 25:52Key takeaways
related talks
52mHow to Transform Developers into Security People
52mLeveraging Psychological Needs For Building A Security Culture Amongst Developers
51mThinking Differently About Security
40mDevelopers Dislike Security: Ten Frustrations and Resolutions
46mAre Developers the New Front Line of Security?
48mLevel Up Your Security Mindset
57mThe Developer's Field Guide to Software Security
27mDevelopers Struggle with Application Security (and How to Make ...)