Panel: Peak Performance Under Pressure: Building Cross-Functional Resilience in Incident Response
summary
Panel argues incident response works when day‑to‑day ops mirror incident workflows, so teams run weekly Slack drills, use dedicated incident command separate from detection engineers, and keep a logging standard and ready templates so reports go out within days. They inject chaos into tabletop exercises (calls at 2 a.m., sudden role swaps) to build muscle memory, use AI for note‑taking but not decisioning, and tie remediation tickets and stakeholder relationship matrices to performance reviews.
AI-written summary · about
chapters (10)
- 0:00Cross-functional incident response
- 1:05Daily ops vs incident response
- 4:37Avoiding panic in comms
- 9:35Workflow changes for incidents
- 12:26AI in incident response
- 16:35Graduated response coordination
- 23:13Building trust with partners
- 28:05Risk tolerance across teams
- 31:33Uber principles elsewhere
- 35:23Q&A on tools & post-mortems
related talks
15mIncident Ready: Chaos Engineer Your Incident Response
29mComposing the Response: Building an Incident Pipeline from Scratch
36mSo You Want a New Incident Commander—Lessons from Building Incident Response...
51mUnder Pressure: What Cyber Can Learn from First Responders
49mTraining for Incident Response: The Red, the Blue, and the Ugly
51mReal World Stories of Incident Response and Threat Intelligence
17mIncident Response @ Scale-Building a Next Generation SOC
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams