When SRE and Security Teams Meet to Face a Crisis
summary
SRE and security teams trade hard specifics: an IDS update that redirects alerts to root floods an ISP with Port 25 SMTP traffic and causes self‑DOS, Juniper firewalls flap and trigger an OSPF LSA storm that multiplies outages when playbooks auto‑failover, Lapsus hands‑on deletions deallocate fleets of VMs identified by IOC IPs, teams build bespoke telemetry to prove SSRF‑style calls and spin up a cloned database for GDPR mapping under duress — rearchitect replacements for EOL firewalls and weeks of emergency dev work follow.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 7:23Security and SRE collaboration
- 18:44Conflicting priorities
- 26:18Incident coordination
- 33:55Incentivizing cooperation
- 38:14Building under duress
related talks
35mSRE for [cyber]security
33mSecurity and SRE: Natural Force Multipliers
28mDefending against SRE with SRE
20mImplementing SRE in a Regulated Environment
35mRole of SRE in DevSecOps
32mIs the S in SRE for “Security”?
30mIntegrating cloud native security into the SRE culture
25mHow do we help enterprise to adopt SRE and DevSecOps practices?