SOC 2 ControlsIncident ResponseCC7NISTPlaybookSOC 2

Incident Response Planning for SOC 2: CC7.3 and CC7.4

Build an incident response capability that satisfies SOC 2 CC7.3 and CC7.4 — from detection to post-mortem, with templates and checklists.

SecureSpect Team··9 min read

What SOC 2 Requires for Incident Response

SOC 2 Common Criteria CC7.3 requires that you evaluate security events to determine if they constitute incidents. CC7.4 requires that you respond to security incidents through a defined, documented process. Together, these criteria mandate:

  • A mechanism to detect and log security events
  • Criteria for classifying events as incidents
  • Defined response procedures for different incident types
  • Communication obligations (internal and customer-facing)
  • Post-incident review to prevent recurrence
  • Incident Severity Classification

    Define severity levels before you need them:

    P1 — Critical Active breach, data exfiltration in progress, full service unavailability affecting multiple customers. Response SLA: 15-minute acknowledgement, 4-hour resolution target.

    P2 — High Suspected unauthorized access, partial service degradation, credential compromise. Response SLA: 1-hour acknowledgement, 24-hour resolution target.

    P3 — Medium Anomalous activity under investigation, isolated component degradation, policy violation detected. Response SLA: 4-hour acknowledgement, 72-hour resolution.

    P4 — Low Informational alerts, policy questions, minor configuration drift. Response SLA: Next business day.

    The Incident Response Lifecycle

    1. Detection and Logging

    Every security event must be logged. Connect your monitoring tools (Datadog, PagerDuty, CloudTrail) to SecureSpect so alerts flow into the incident log automatically.

    2. Triage and Classification

    Assign a severity level within the SLA window. A triage template should answer:

    • What happened?
    • What systems are affected?
    • Is there evidence of unauthorized access or data exposure?
    • Is the event ongoing?

    3. Containment

    P1/P2 containment actions (take immediate action without waiting for full analysis):

    • Revoke compromised credentials
    • Block suspect IP addresses / close network paths
    • Isolate affected infrastructure

    4. Eradication and Recovery

    Remove the threat and restore normal operations. Document every action taken with timestamps.

    5. Notification

    SOC 2 doesn't specify customer notification timelines, but most SLAs and privacy regulations do:

    • GDPR — 72 hours for data breaches involving EU residents
    • HIPAA — 60 days for breaches of PHI
    • Customer contracts — Typically 72 hours for any security incident affecting customer data

    6. Post-Mortem

    For P1 and P2 incidents, conduct a structured post-mortem within 5 business days. Document:

    • Timeline of events
    • Root cause
    • Contributing factors
    • Action items with owners and due dates

    Evidence for Auditors

    Your auditor will ask for:

    • The incident log for the observation period (including periods with zero incidents)
    • The incident response policy document
    • Evidence of at least one post-mortem (even for low-severity incidents)
    • Evidence that notification procedures were followed for any customer-impacting event

    SecureSpect's incident module captures all of this automatically. Each incident entry includes the timeline, severity, affected controls, resolution status, and linked post-mortem.

    Automate your SOC 2 evidence collection

    Connect your AWS and GitHub environments and start collecting audit-ready evidence today. Free to start.

    Start Free →More Articles