Building a Product Security Incident Response Team: Learnings From the Hivemind
summary
Provides concrete playbook pieces: a web-based vulnerability disclosure policy and boilerplate, a checklist of investigation fields and an advisory checklist to publish, plus templates for SLAs and escalation criteria. Recommends roles (application security engineer, technical program manager, optional comms), tooling (Jira fields, source‑code scanner + vulnerability‑intel feed), yearly emergency drills, and decision rules for triage (example: what to do when 150 CVSS ≥7.5 items appear).
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:52AGENDA
- 4:43BUT WHAT ABOUT ISO STANDARDS!?
- 6:07COMMON SIRT STRUCTURES
- 8:26TYPICAL ROLE RESPONSIBILITIES
- 12:48SDL OVERVIEW
- 13:43INCIDENT RESPONSE PROCESS
- 14:53INTERNAL POLICY
- 18:35PUBLIC DOCUMENTATION
- 21:10TOOLKIT
- 23:43DATA MANAGEMENT FOR SIRTS
- 24:47PITFALLS
- 27:20FREE RESOURCES
- 28:11QUESTIONS
related talks
12mAll Hands on Deck – Handling Security Issues
10mHandling Security Issues
49mTraining for Incident Response: The Red, the Blue, and the Ugly
33mRapid-Fire Stories of Creative Solutions to InfoSec Problems
21mApplication Security Response: When Hackers Come A-Knockin
18mWhat You Need to Know and Do about Vulnerability Disclosure
33mLearning from Past Security Breaches: Strengthening AppSec Efforts and Focus
41mHow to Keep Your Cool and Write Powerful Incident Response Reports