Do You Even Tech Anymore: Management & Leadership in Security?
summary
Riot built a self-service and feedback-driven security program across a hybrid infrastructure and deliberately delayed a POODLE TLS change because millions of players ran XP, showing security tradeoffs with product impact. Management mistakes called out: micromanaging, wearing too many hats, becoming a one-on-one machine, and letting Slack and open calendars destroy deep work. Prescriptions are concrete: delegate, own the calendar, block schedule deep work, use explicit accountability and feedback (target a 5:1 feedback ratio), and get mentors — these changes scale teams from a few to many successfully.
AI-written summary · about
chapters (5)
- 0:00Introduction and welcome
- 1:28From tech to management
- 9:11Story time and failures
- 17:26From what to how
- 26:50Key takeaways and Q&A
related talks
38mKeynote: Dumping Traditional Security Teams
50mYou’re Doing It Wrong! Common Security Anti Patterns
13mTen Ways to Doom Your DevSecOps
25mWhat Does it Mean to Build a Proactive Security...
43mTitans of Scale: Strategies to Scale Security in Expanding Organizations
27mSecurity: The Thing That Everyone...
46mFire, Brimstone, and Bad Security Decisions
33mDon't You Know That You're Toxic? Moving Towards Positive Security Practices w/in Your Organization