SOC 2 · CC2 Communication and information
CC2.3
Communication with external parties
frameworkSOC 2 (Trust Services Criteria)
sectionCC2 Communication and information
csf 2.0RC.CO-03 RC.CO-04 RC.RP-05 RS.CO-02 RS.CO-03
topicsCommunication, Reporting, Comms & Restore
frameworks0 12 1
Official text · not licensableSummary (ControlMapping's wording): Communication with external parties. The criterion text is AICPA's copyright.
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | RC.CO-03RC.CO-04RC.RP-05RS.CO-02RS.CO-03 | Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders; Public updates on incident recovery are shared using approved methods and messaging… | Editorial | Same topic: Comms & Restore, Reporting, Communication (editorial pick) |
| ISO 27001 | A.5.5A.5.6A.5.26A.6.8Clause 7.4 | Contact with authorities; Contact with special interest groups… | Editorial | Same topic: Reporting, Communication, Comms & Restore (editorial pick)1 loosely related (not mappings) |
| CIS v8.1 | CIS 17.2CIS 17.3CIS 17.6 | Establish and Maintain Contact Information for Reporting Security Incidents; Establish and Maintain an Enterprise Process for Reporting Incidents… | Editorial | Same topic: Communication, Reporting, Comms & Restore (editorial pick)1 loosely related (not mappings)CIS 11.1 Establish and Maintain a Data Recovery Process Only shares CSF RC.RP-05: related, not a mapping |
| PCI DSS | 12.10.1 | Incident response plan ready to activate | Editorial | Same topic: Reporting (editorial pick)8 loosely related (not mappings)12.8.2 Written agreements with service providers Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03: related, not a mapping 12.10.3 Incident response staff available around the clock Only shares CSF RC.CO-03, RC.CO-04, RS.CO-02: related, not a mapping 12.8.4 Service provider compliance monitored annually Only shares CSF RC.CO-03, RS.CO-03: related, not a mapping 10.4.1 Security event and critical logs reviewed daily Only shares CSF RC.RP-05: related, not a mapping 11.4.4 Penetration test findings corrected and retested Only shares CSF RC.RP-05: related, not a mapping 12.8.5 Responsibilities split with each provider documented Only shares CSF RS.CO-02: related, not a mapping 12.10.6 Plan updated from lessons learned and industry changes Only shares CSF RS.CO-03: related, not a mapping |
| CMMC | IR.L2-3.6.2 | Incident Reporting | Editorial | Same topic: Communication, Reporting, Comms & Restore (editorial pick)1 loosely related (not mappings)IR.L2-3.6.1 Incident Handling Only shares CSF RC.CO-03, RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping |
| 800-53 | CP-10IR-6IR-7 | System Recovery and Reconstitution; Incident Reporting… | Editorial | Same topic: Comms & Restore, Reporting, Communication (editorial pick)5 loosely related (not mappings)IR-4 Incident Handling Only shares CSF RC.CO-03, RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping |
| HIPAA | §164.308(a)(6)(ii) | Response and Reporting | Editorial | Same topic: Reporting (editorial pick)12 loosely related (not mappings)§164.308(a)(6) Security Incident Procedures Only shares CSF RC.CO-03, RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping §164.308(a)(1)(ii)(D) Information System Activity Review Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03: related, not a mapping §164.314(a)(2)(i) Business Associate Contracts Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03: related, not a mapping §164.314(a)(2)(iii) Business associate contracts with subcontractors Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03: related, not a mapping §164.314(b)(2)(iv) Group Health Plan Implementation Specification Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03: related, not a mapping §164.308(a)(7)(ii)(B) Disaster Recovery Plan Only shares CSF RC.CO-04, RC.RP-05: related, not a mapping §164.308(a)(7)(ii)(C) Emergency Mode Operation Plan Only shares CSF RC.CO-04, RC.RP-05: related, not a mapping §164.308(a)(7)(ii)(D) Testing and Revision Procedure Only shares CSF RC.CO-04, RC.RP-05: related, not a mapping …and 4 more in the downloads |
| GDPR | Art.33(1)Art.34(1) | Notification of a personal data breach to the supervisory authority; Communication of a personal data breach to the data subject | Editorial | Same topic: Reporting, Comms & Restore (editorial pick)1 loosely related (not mappings) |
| NIS2 | 3.34.3 | Event reporting; Crisis management | Editorial | Same topic: Reporting, Communication, Comms & Restore (editorial pick)1 loosely related (not mappings)3.5 Incident response Only shares CSF RC.CO-03, RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping |
| Essential Eight | ISM-0123ISM-0140 | Cyber security incidents are reported to the chief information security officer, or one…; Cyber security incidents are reported to ASD as soon as possible after they occur or… | Editorial | Same topic: Reporting (editorial pick)1 loosely related (not mappings)ISM-1515 Restoration of data, applications and settings from backups to a common point in time… Only shares CSF RC.RP-05: related, not a mapping |
| DORA | Art.11(2)(e)Art.11(7)Art.14(1)Art.14(2)Art.17(3)(d)Art.18(1)Art.19(1)Art.19(3)Art.19(4) | Response and recovery; Response and recovery… | Editorial | Same topic: Comms & Restore, Communication, Reporting (editorial pick) |
| CPS 234 | Para 25Para 35Para 36 | Response plans cover all stages and escalation; Notify APRA of material incidents within 72 hours… | Editorial | Same topic: Communication, Reporting (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.