Security Advocacy Shouldn't Be for Security Professionals: How the Industry Misses the Mark...
summary
Analysis of 200 pieces of content scores vendor, nonprofit and indie materials on a score out of six that checks plain language, no assumed knowledge, clear go‑dos, single‑person actions and under‑one‑hour consumability; results show not‑for‑profits top vendors bottom, many vendor docs are long and link outward (example: AWS PDF 125 pages, Microsoft benchmark links 60+ pages), one intro course runs 18+2 hours, most content is not paywalled. Recommendation: provide a TL;DR, explicit what/why/how, concise baselines and decision trees.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 2:29Current content state
- 7:43Psychological barriers
- 10:45Research findings
- 20:21Comparative document audit
- 25:51Strategies for improvement
- 30:21Conclusion and takeaways
- 36:24Q&A session
related talks
44mA Matter Of Trust: When Security Is Not Enough
46mIn Search of Security Shangri-la
39mProactive Security, less buzzword, more action
41mAim-Ready-Fire
10mSecurity Starts With Plain Language
27mSecurity Does Not Need to Be Fun: Ignoring OWASP to Have a Terrible Time
44mNavigating Open Source and Open Standards for Better Cybersecurity
51mThinking Differently About Security