SOC 2 · CC7 System operations
CC7.5
Recovering from identified security incidents
frameworkSOC 2 (Trust Services Criteria)
sectionCC7 System operations
csf 2.0ID.IM-03 ID.IM-04 RC.CO-03 RC.CO-04 RC.RP-01 RC.RP-02 RC.RP-05 RC.RP-06
topicsRecovery Planning, Lessons Learned, Comms & Restore
frameworks0 11 1
Official text · not licensableSummary (ControlMapping's wording): Recovering from identified security incidents. The criterion text is AICPA's copyright.
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | ID.IM-03ID.IM-04RC.CO-03RC.CO-04RC.RP-01RC.RP-02RC.RP-05RC.RP-06 | Improvements are identified from execution of operational processes, procedures, and activities; Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved… | Editorial | Same topic: Lessons Learned, Recovery Planning, Comms & Restore (editorial pick) |
| ISO 27001 | A.5.26A.5.27A.5.29A.5.30Clause 7.4Clause 10.1 | Response to information security incidents; Learning from information security incidents… | Editorial | Same topic: Comms & Restore, Lessons Learned, Recovery Planning (editorial pick) |
| CIS v8.1 | CIS 11.1CIS 17.6CIS 17.8 | Establish and Maintain a Data Recovery Process; Define Mechanisms for Communicating During Incident Response… | Editorial | Same topic: Recovery Planning, Comms & Restore, Lessons Learned (editorial pick)1 loosely related (not mappings)CIS 17.2 Establish and Maintain Contact Information for Reporting Security Incidents Only shares CSF RC.CO-04: related, not a mapping |
| PCI DSS | 12.10.112.10.6 | Incident response plan ready to activate; Plan updated from lessons learned and industry changes | Editorial | Same topic: Recovery Planning, Lessons Learned (editorial pick)10 loosely related (not mappings)12.10.2 Incident response plan reviewed and tested annually Only shares CSF ID.IM-04, RC.RP-01, RC.RP-02, RC.RP-06: related, not a mapping 12.10.3 Incident response staff available around the clock Only shares CSF ID.IM-04, RC.CO-03, RC.CO-04, RC.RP-01: related, not a mapping 1.2.4 Accurate account-data flow diagram maintained Only shares CSF RC.RP-02: related, not a mapping 10.4.1 Security event and critical logs reviewed daily Only shares CSF RC.RP-05: related, not a mapping 10.5.1 Audit logs retained 12 months, three immediately available Only shares CSF RC.RP-06: related, not a mapping 11.4.4 Penetration test findings corrected and retested Only shares CSF RC.RP-05: related, not a mapping …and 2 more in the downloads |
| CMMC | IR.L2-3.6.1IR.L2-3.6.2 | Incident Handling; Incident Reporting | Editorial | Same topic: Lessons Learned, Comms & Restore (editorial pick) |
| 800-53 | CP-2CP-10IR-4IR-6 | Contingency Plan; System Recovery and Reconstitution… | Editorial | Same topic: Recovery Planning, Comms & Restore, Lessons Learned (editorial pick)3 loosely related (not mappings)IR-8 Incident Response Plan Only shares CSF ID.IM-03, ID.IM-04, RC.RP-01, RC.RP-02…: related, not a mapping |
| HIPAA | §164.308(a)(7)§164.308(a)(7)(ii)(B) | Contingency Plan; Disaster Recovery Plan | Editorial | Same topic: Recovery Planning (editorial pick)11 loosely related (not mappings)§164.308(a)(6)(ii) Response and Reporting Only shares CSF ID.IM-03, ID.IM-04, RC.CO-03, RC.CO-04…: related, not a mapping §164.308(a)(6) Security Incident Procedures Only shares CSF ID.IM-03, RC.CO-03, RC.CO-04, RC.RP-01…: related, not a mapping §164.308(a)(7)(ii)(C) Emergency Mode Operation Plan Only shares CSF ID.IM-03, ID.IM-04, RC.CO-04, RC.RP-01…: related, not a mapping §164.308(a)(7)(ii)(D) Testing and Revision Procedure Only shares CSF ID.IM-03, ID.IM-04, RC.CO-04, RC.RP-02…: related, not a mapping §164.308(a)(7)(ii)(E) Applications and Data Criticality Analysis Only shares CSF ID.IM-03, ID.IM-04, RC.CO-04: related, not a mapping §164.310(a)(2)(i) Contingency Operations Only shares CSF ID.IM-03, ID.IM-04, RC.CO-04: related, not a mapping §164.312(a)(2)(ii) Emergency Access Procedure Only shares CSF ID.IM-03, ID.IM-04, RC.CO-04: related, not a mapping §164.308(a)(1)(ii)(D) Information System Activity Review Only shares CSF ID.IM-03, RC.CO-03: related, not a mapping …and 3 more in the downloads |
| GDPR | Art.32(1)(c)Art.34(1) | Security of processing; Communication of a personal data breach to the data subject | Editorial | Same topic: Recovery Planning, Comms & Restore (editorial pick) |
| NIS2 | 3.64.14.3 | Post-incident reviews; Business continuity and disaster recovery plan… | Editorial | Same topic: Lessons Learned, Recovery Planning, Comms & Restore (editorial pick) |
| Essential Eight | ISM-1515 | Restoration of data, applications and settings from backups to a common point in time… | No mapping. Only shares CSF RC.RP-02, RC.RP-05: related, not a mapping | |
| DORA | Art.11(2)(e)Art.11(3)Art.11(7)Art.12(6)Art.13(2)Art.13(3) | Response and recovery; Response and recovery… | Editorial | Same topic: Comms & Restore, Recovery Planning, Lessons Learned (editorial pick) |
| CPS 234 | Para 25 | Response plans cover all stages and escalation | Editorial | Same topic: Lessons Learned (editorial pick) |
| Cyber Essentials | — | No requirement | No mapping in our data | No mapping in our data (Cyber Essentials covers five technical controls only). |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.