CC7.4: Responding to incidents

The company has a defined incident response process with roles, containment steps, communication and evidence handling, and follows it when an incident occurs.

Category: Security (common criteria, required in every SOC 2 report) · Series: CC7 (System operations) · TSC 2017 (2022 points of focus)

That summary is Policyseed’s own paraphrase, written to be read next to the policy sections below. The authoritative wording is the AICPA’s Trust Services Criteria, which the CPA firm tests your controls against during the examination.

How auditors usually test CC7.4

For response the auditor reads the incident procedure and then tests it against real records: an incident from the period, or the tabletop exercise if nothing happened. Roles, containment, communication and evidence handling are checked against what the plan says should occur. Typical exceptions are a tabletop that was planned but not held within the year, or an incident ticket missing the decision on notifying customers.

Example control for CC7.4

  • Incidents follow a written procedure with a named contact and a post-incident review. Documented in P13 Incident Response. Evidence: Incident tickets with timeline and review notes, or a tabletop exercise record if there were none.

One way to meet the criterion, not the only one. The SOC 2 controls list has the other examples side by side.

Policies that address CC7.4

The Policyseed crosswalk points CC7.4 at one policy. Each link opens the full sample text at the section an auditor would read. Section 4 holds the statements management commits to; section 5 holds the procedures that produce evidence.

Preparing for ISO 27001 as well? The same policies are mapped to Annex A controls on the ISO 27001 policy templates page, so one document set can serve both. The Annex A controls that share a policy with CC7.4 are listed in the SOC 2 to ISO 27001 mapping.

Evidence examples for CC7.4

Artifacts a company of 5 to 200 people can realistically produce. The Audit Kit’s evidence checklist lists them per policy with an owner column so each one has a name against it before the examination.

  • Approved Incident Response Policy with contact details and severity levels
  • Incident record for at least one real or tabletop incident showing detection, containment, communication and closure
  • Annual tabletop exercise notes with attendees, scenario and lessons learned
  • Customer notification template and record of any notifications sent

Readiness check question for CC7.4

  • Do you have a written incident response plan that you tested (for example a tabletop) in the last 12 months?

It is one of the 20 questions in the free SOC 2 readiness check, which scores your answers in the browser and lists what to fix first.

Related criteria in CC7 (System operations)

Previous: CC7.3 Evaluating security events. Next: CC7.5 Recovering from incidents. All 38 criteria are listed on the template index.

Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.