Handling Security Issues
summary
The talk explains a coordinated, cross‑functional process for handling software vulnerabilities, naming roles (developers, security, support, legal & communications) and concrete workflows: triage, patch, automated tests, hotfix branches, rollback, customer notification and partner coordination. It recommends documenting fixes and playbooks, tracking a single prioritized mitigation until verified, and using measured processes instead of ad‑hoc emails to shorten exposure and reduce customer impact.
AI-written summary · about
chapters (7)
- 0:00Security handling intro
- 3:27Security team roles
- 5:14Security fixes and testing
- 6:32Project coordination
- 8:13Incident response strategies
- 9:20Lessons from incidents
- 10:04Q&A
related talks
12mAll Hands on Deck – Handling Security Issues
29mMake It Fixable: Preparing for Security Vulnerability Reports
27mSecurity: The Thing That Everyone...
09mInterview
18mWhat You Need to Know and Do about Vulnerability Disclosure
22mThe Hip Approach to Safeguarding your Users
21mApplication Security Response: When Hackers Come A-Knockin
29mBuilding a Product Security Incident Response Team: Learnings From the Hivemind