Baking a Security Community From Scratch
summary
OSTIF spends a year turning security audits into an active community by following repeatable steps: work backwards from a clear goal, find willing co-contributors, and centralize on useful, automated content (recordings, data feeds, repeatable reports) rather than socializing alone. Recruitment uses targeted outreach and email/social campaigns, roles are intentionally handed off to create redundancy, and failure is treated as feedback. Recommended resources: Smart Brevity and the University of Kansas Community Toolbox; results so far are positive.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:07Planning foundation
- 5:59Engaging members
- 7:45Empowering contributors
- 10:15Adapting strategies
- 12:23Additional resources
related talks
24mConcrete Steps to Create a Security Culture
30mSuccess Stories in Open Source: Security Audits with OSTIF
20mBuilding security culture on infrastructure teams
26mLooking at Open Source Security from the Community Angle
35mSecurity Culture: Why is it important?
17mA Sneak Peak Into Security Reviews with the Community
37mSecurity Culture Hacking: Disrupting the Security Status Quo
39mManaging Audits for Critical Open Source Projects
