Screenata
All SOC 2 Policy Templates
AICPA CC7.3AICPA CC7.4AICPA CC7.5SOC 2ISO 27001HIPAAGDPR

SOC 2 Incident Response Policy Template (CC7.4)

Quick Summary

A SOC 2 Incident Response Policy defines how your team detects, triages, contains, communicates, and learns from security and availability incidents. Auditors test this under AICPA CC7.3, CC7.4, and CC7.5 by checking incident tickets, postmortems, and at least one annual tabletop exercise if no major incidents occurred.

Free Markdown Template

Copy or download the incident response policy

Replace bracketed [PLACEHOLDERS] with your actual stack

soc-2-incident-response-policy.mdMarkdown
# Security Incident Response Policy (SOC 2 CC7.3 – CC7.5)

**Document Owner:** [Security / Engineering Lead]  
**Approved By:** [CEO / CTO]  
**Effective Date:** [YYYY-MM-DD]  
**Review Cadence:** Annual (plus annual tabletop test)  
**Applies To:** All employees, contractors, production systems, and third-party subprocessors

---

## 1. Purpose
This policy establishes a structured process to detect, triage, contain, eradicate, recover from, and review security and availability incidents affecting [Company Name] or customer data.

## 2. Roles and Responsibilities
- **Incident Commander (IC):** [CTO / On-Call Lead]: owns triage, coordination, containment decisions, and status updates.
- **Technical Responders:** Engineering & Infrastructure team: executes investigation, log preservation, containment, and remediation.
- **Communications & Legal Lead:** [CEO / General Counsel]: manages customer notifications, regulatory filings, and external messaging.
- **All Personnel:** Report suspected security events immediately to [security@company.com / #security-incidents].

## 3. Severity Classification

| Severity | Definition | Target Initial Response | Update Cadence |
|---|---|---|---|
| **SEV-1 (Critical)** | Confirmed or suspected unauthorized access to customer data, active ransomware/compromise, or full production outage | Within [1] hour | Every [2] hours until contained |
| **SEV-2 (High)** | Degraded production security control, exposed non-customer secret/credential, or partial service outage | Within [4] hours | Daily until resolved |
| **SEV-3 (Medium)** | Isolated endpoint malware, phishing attempt clicked without confirmed data loss, or minor policy violation | Within [1] business day | Upon resolution |
| **SEV-4 (Low)** | False positive, blocked scan, or informational security alert | Logged and triaged in queue | As needed |

## 4. Incident Response Phases
1. **Detection & Reporting (CC7.3):** Alerts arrive from automated monitoring ([CloudTrail / GuardDuty / Datadog / Sentry]), customers, or employees. Every confirmed or suspected incident receives a tracked ticket in [Jira / Linear / Incident.io].
2. **Triage & Containment (CC7.4):** The Incident Commander assigns severity, isolates affected accounts/hosts/keys, revokes compromised sessions, and preserves logs and forensic evidence before destructive remediation.
3. **Eradication & Recovery:** Root cause is removed, systems are patched or rebuilt from clean images, credentials are rotated, and service integrity is verified before resuming normal traffic.
4. **Notification:**
   - **Customers:** For confirmed breaches affecting customer data, [Company Name] notifies impacted customers without undue delay and within contractual SLA (typically within [48 / 72] hours of confirmation).
   - **Regulators / Subprocessors:** Legal counsel coordinates any statutory notifications (e.g., GDPR 72-hour window, state breach laws, or HIPAA where applicable).
5. **Post-Incident Review (CC7.5):** Within [5 / 10] business days of closing any SEV-1 or SEV-2 incident, the team completes a blameless postmortem documenting timeline, root cause, customer impact, and tracked preventive action items.

## 5. Annual Testing (Tabletop Exercise)
At least once every 12 months, [Company Name] runs a documented incident response tabletop exercise (simulating a realistic scenario such as credential compromise or production breach), records participants and lessons learned, and updates this policy and runbooks accordingly.

## 6. Review
This policy is reviewed annually and after any SEV-1 security incident.

Evidence Mapping

What auditors test beyond this policy

A signed policy document only satisfies design intent. During SOC 2 fieldwork, your CPA auditor samples operating evidence against each clause below:

Policy RequirementControlEvidence Your Auditor Requests
Incident tracking & postmortem trailCC7.4 / CC7.5List of security incidents during the observation period with incident tickets, containment timestamps, customer notifications (if any), and completed postmortems.
Annual tabletop exercise (especially with zero incidents)CC7.4Dated tabletop exercise notes showing scenario, participants, walkthrough decisions, and follow-up action items.
Alerting & escalation channels operationalCC7.3Configuration of security alerting (GuardDuty/CloudTrail/Sentry/PagerDuty) routing to your on-call or #security-incidents channel.
Common Audit Exceptions to Avoid
  • Assuming that having zero security incidents during the year means no evidence is needed. Auditors still require an annual tabletop exercise to prove the plan works.
  • Promising '24-hour notification to every customer for any security event' instead of specifying confirmed unauthorized access to customer data within contractual/statutory timelines.
  • Writing postmortems in ephemeral Slack threads instead of archiving dated postmortem documents with tracked remediation tickets.

Related guide: The 7 documents your SOC 2 auditor actually needs

Frequently Asked Questions

Incident Response Policy FAQ

What if we had zero security incidents during our SOC 2 audit period?
Auditors still test CC7.4 by asking for a documented annual incident response tabletop exercise (a 45–60 minute walkthrough of a realistic scenario like a leaked AWS key or phishing compromise) plus written confirmation that no reportable security incidents occurred.
How long does a SOC 2 incident response tabletop exercise need to be?
A focused 45 to 60 minute session with your CTO, engineering lead, and CEO walking through one realistic scenario is plenty, as long as you document the date, attendees, scenario steps, gaps found, and follow-up tickets.
Should incident response include availability outages as well as security breaches?
Yes, especially if you include the Availability Trust Services Criteria in your SOC 2 scope. Covering both security compromises and production outages in one severity table keeps engineering runbooks unified.

Skip manual fill-in-the-blank edits

Draft this policy directly from your real infrastructure.

Screenata scans your AWS, GCP, GitHub, and identity provider read-only, writes auditor-ready policies tied to real controls, and collects signed evidence automatically.