# SOC 2 (2017 TSC) CC7.5 — Security Incident Recovery Activities - Source: https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc7-5-security-incident-recovery-activities - Section: [Compliance](https://support.icompaas.com/compliance) › [SOC 2 Trust Services Criteria (2017, with 2022 points of focus)](https://support.icompaas.com/compliance/soc-2-trust-services-criteria) › Common Criteria (Security) — CC7 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **SOC 2 (2017 TSC)**·Criterion `CC7.5`·high·Component: **Common Criteria (Security)** ## What this control requires > The entity identifies, develops, and implements activities to recover from identified security incidents. > > — SOC 2 (2017 TSC), Criterion CC7.5 ### In plain English The entity identifies, develops, and implements activities to recover from identified security incidents. In practice, this means you can prove you change response-level controls on a defined cadence. ## Why it matters Every SOC 2 audit opinion is built control-by-control from the Trust Services Criteria. A missing or failing criterion produces an exception in the report, which buyers, partners and procurement teams read line-by-line during vendor reviews. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A SOC 2 auditor (under AT-C §§ 105/205) tests both design and operating effectiveness over the audit window. For each criterion they expect a written control, a control owner, a population of events, and a sample tested against the population — including remediation tickets for exceptions. Within **Common Criteria (Security)**, the assessor will trace your implementation back to the catalogue reference (Criterion CC7.5) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Incident Response **Runbook.** Maintain a runbook keyed by incident type with named roles (IC, comms, scribe), an out-of-band comms channel, and a 72-hour timeline for external notification. **Tabletop.** Run a quarterly tabletop exercise (ransomware, insider, supply-chain) and feed gaps back into the runbook. ### Operational checklist - **Change.** Document the trigger, the owner and the cadence. - **Incident.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Management.** Document the trigger, the owner and the cadence. - **Scope:** response, management. ## Evidence to collect - **Ticketing Workflow.** `ticketing_workflow` evidence - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Workflow metrics (ServiceNow, Jira) show approvals and remediation. Focus: Security Incident Recovery Activities (Original component: System Operations). ## Common pitfalls - Runbooks that name a role but no person, or list a paging channel that no longer exists. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-53 Rev. 5 IR-3(2)** — Coordination With Related Plans](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ir-3-2-coordination-with-related-plans) - [**NIST SP 800-171 Rev. 3 3.6.2** — Incident Monitoring, Reporting, and Response Assistance](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-6-2-incident-monitoring-reporting-and-response-assistance) - [**CIS Controls v8 17.8** — Conduct Post-Incident Reviews](https://support.icompaas.com/compliance/cis-controls-v8/17-8-conduct-post-incident-reviews) - [**ISO/IEC 27001:2022 A.5.27** — Learning from information security incidents](https://support.icompaas.com/compliance/iso-27001-2022/a-5-27-learning-from-information-security-incidents) - [**BSI C5:2020 OPS-21** — Involvement of Cloud customers in the event of incidents](https://support.icompaas.com/compliance/bsi-c5-2020/ops-21-involvement-of-cloud-customers-in-the-event-of-incidents) ## Related controls in SOC 2 (2017 TSC) - [**Criterion CC7.4** — Incident Response](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc7-4-incident-response) - [**Criterion CC7.3** — Incident Detection](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc7-3-incident-detection) - [**Criterion P6.6** — Breach and Incident Notification to Stakeholders](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-6-breach-and-incident-notification-to-stakeholders) - [**Criterion P6.3** — Logging and Retention of Unauthorized Disclosure Incidents](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-3-logging-and-retention-of-unauthorized-disclosure-incidents) - [**Criterion CC3.4** — Change Identification](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc3-4-change-identification) - [**Criterion CC8.1** — Change Management](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc8-1-change-management) ## References - [AICPA / ASEC — SOC 2 (2017 TSC)](https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2) - Catalogue identifier: `Criterion CC7.5` Topics: incident responsechange managementbackup recovery ## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Start with the full SOC 2 implementation guide — scope, roadmap, evidence and how the assessment runs. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): The certificate most non-US customers ask for instead of SOC 2; the controls overlap enough to run one matrix for both. - [HIPAA compliance for SaaS: a practical implementation guide](https://support.icompaas.com/compliance/hipaa): If health-tech customers ask for SOC 2, they will also ask about the Security Rule; the two are usually evidenced from the same controls.