Skip to content
SOC 2 Compliance Software

Home / Glossary / Incident response plan

Glossary, read 12 Nov 2026

Incident response plan in a SOC 2 examination, defined with a sourced example

All termsRead the guides

The definition of Incident response plan

A SOC 2 reviewer reads the plan and then asks for proof it works: the incident log for the window, tickets for real events, and records of a test or tabletop exercise. If there were no incidents, auditors will still ask to see how you decide something is an incident and who is called.

IR-8 also asks that the plan define metrics, address sharing of incident information, be reviewed and approved by named parties, and be updated after problems found during execution or testing. Teams usually write the first half, a call tree and severity levels, and skip the update step. A plan last edited the day it was written looks unused.

The common error is treating every security alert as an incident, or none of them. Define the threshold in writing. Then each alert is either closed with a note under the threshold or opened as an incident with a timeline, a root cause and a customer notice decision. Keep the incident register even for false alarms, since the auditor samples from it.

A sourced example

NIST SP 800-53 IR-8 says the plan should provide "a roadmap for implementing its incident response capability", define "reportable incidents", provide "metrics for measuring the incident response capability" and "Explicitly designate responsibility for incident response". Four phrases give a company a checklist to test its own plan against before the auditor does. NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026.

Sources

  1. NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026
  2. NIST CSRC glossary, incident response plan, read 12 Nov 2026

Last reviewed 12 Nov 2026.