Product Security Incident Response at a Fortune 500 SaaS
summary
ServiceNow PSIRT runs a 12‑person team that grows from a 2.5‑year build into 12 engineers on three continents, and operates as a CNA/member of FIRST.org. The talk claims SaaS incidents demand faster, risk‑based choices because of internet‑discoverable attack surface and near‑instant researcher access; it gives concrete practices: measure version adoption (eg. 0.1% bleeding‑edge), use telemetry to prioritize fixes, consider forcing updates onto customer instances and the tradeoffs of disclosures versus customer action.
AI-written summary · about
chapters (7)
- 0:00Product security response intro
- 3:57SaaS risk factors
- 7:06Shared cloud responsibility
- 13:50Customer intent challenges
- 19:45Resource abuse in SaaS
- 24:17SaaS security opportunities
- 32:50Q&A
related talks
17mIncident Response @ Scale-Building a Next Generation SOC
36mUsing data-driven metrics to anticipate and prevent security incidents
49mStories from the SOC Front Lines
45mRunning an efficient bug bounty program and PSIRT... (Garrett McNamara, Jeff Guerra)
40mAppSec’s Future and the Rise of the Chief Product Security Officer
30mWhen Application Security “The Wrong Way” Is the Right Thing for Your Organization
46mHow to Adapt to Security Changes in Cloud SaaS Transformation
41mDesigning Product Security for a Brighter Smile and a Healthier Tomorrow