cm/controlmapping
Sources
CIS v8.1 · 17. Incident Response Management
CIS 17.2

Establish and Maintain Contact Information for Reporting Security Incidents

frameworkCIS Controls v8.1 section17. Incident Response Management csf 2.0RC.CO-04 RS.CO-02 RS.CO-03 topicsCommunication frameworks5 3 4 1
Official text · not licensableSafeguard title © CIS (CC BY-NC-ND 4.0). See CIS Controls v8.1 for details.

Wrong or missing mapping? Report it

Equivalents of CIS 17.2 in other frameworks
FrameworkRequirementTitleLinkSource / reason
NIST CSF 2.0RS.CO-03Information is shared with designated internal and external stakeholdersCrosswalkSame topic: Communication
2 loosely related (not mappings)
RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging Loosely related
Only shares CSF RC.CO-04: related, not a mapping
RS.CO-02 Internal and external stakeholders are notified of incidents Loosely related
Only shares CSF RS.CO-02: related, not a mapping
ISO 27001Clause 7.4A.5.6Communication; Contact with special interest groupsCrosswalkSame topic: Communication
1 loosely related (not mappings)
A.5.26 Response to information security incidents Loosely related
Only shares CSF RS.CO-02, RS.CO-03: related, not a mapping
SOC 2CC2.3Communication with external partiesEditorialSame topic: Communication (editorial pick)
1 loosely related (not mappings)
CC7.5 Recovering from identified security incidents Loosely related
Only shares CSF RC.CO-04: related, not a mapping
PCI DSS12.10.112.8.212.10.312.8.4Incident response plan ready to activate; Written agreements with service providers…Loosely relatedNo mapping. Only shares CSF RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping
+2 more loosely related (not mappings)
12.8.5 Responsibilities split with each provider documented Loosely related
Only shares CSF RS.CO-02: related, not a mapping
12.10.6 Plan updated from lessons learned and industry changes Loosely related
Only shares CSF RS.CO-03: related, not a mapping
CMMCIR.L2-3.6.2Incident ReportingCrosswalkSame topic: Communication
1 loosely related (not mappings)
IR.L2-3.6.1 Incident Handling Loosely related
Only shares CSF RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping
800-53IR-7Incident Response AssistanceCrosswalkSame topic: Communication
5 loosely related (not mappings)
IR-4 Incident Handling Loosely related
Only shares CSF RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping
IR-6 Incident Reporting Loosely related
Only shares CSF RS.CO-02, RS.CO-03: related, not a mapping
SR-3 Supply Chain Controls and Processes Loosely related
Only shares CSF RS.CO-02, RS.CO-03: related, not a mapping
SR-8 Notification Agreements Loosely related
Only shares CSF RS.CO-02, RS.CO-03: related, not a mapping
CP-2 Contingency Plan Loosely related
Only shares CSF RC.CO-04: related, not a mapping
HIPAA§164.308(a)(6)§164.308(a)(6)(ii)§164.308(a)(1)(ii)(D)§164.314(a)(2)(i)Security Incident Procedures; Response and Reporting…Loosely relatedNo mapping. Only shares CSF RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping
+9 more loosely related (not mappings)
§164.314(a)(2)(iii) Business associate contracts with subcontractors Loosely related
Only shares CSF RS.CO-02, RS.CO-03: related, not a mapping
§164.314(b)(2)(iv) Group Health Plan Implementation Specification Loosely related
Only shares CSF RS.CO-02, RS.CO-03: related, not a mapping
§164.308(a)(7) Contingency Plan Loosely related
Only shares CSF RC.CO-04: related, not a mapping
§164.308(a)(7)(ii)(B) Disaster Recovery Plan Loosely related
Only shares CSF RC.CO-04: related, not a mapping
…and 5 more in the downloads
GDPRArt.34(1)Art.33(1)Communication of a personal data breach to the data subject; Notification of a personal data breach to the supervisory authorityLoosely relatedNo mapping. Only shares CSF RC.CO-04, RS.CO-02: related, not a mapping
NIS24.3Crisis managementCrosswalkSame topic: Communication
2 loosely related (not mappings)
3.5 Incident response Loosely related
Only shares CSF RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping
3.3 Event reporting Loosely related
Only shares CSF RS.CO-02: related, not a mapping
Essential EightISM-0123ISM-0140Cyber 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…Loosely relatedNo mapping. Only shares CSF RS.CO-02: related, not a mapping
DORAArt.14(1)Art.14(2)Art.17(3)(d)Communication; Communication…EditorialSame topic: Communication (editorial pick)
6 loosely related (not mappings)
Art.11(2)(e) Response and recovery Loosely related
Only shares CSF RC.CO-04: related, not a mapping
Art.11(7) Response and recovery Loosely related
Only shares CSF RC.CO-04: related, not a mapping
Art.18(1) Classification of ICT-related incidents and cyber threats Loosely related
Only shares CSF RS.CO-02: related, not a mapping
Art.19(1) Reporting of major ICT-related incidents and voluntary notification of significant cyber threats Loosely related
Only shares CSF RS.CO-02: related, not a mapping
Art.19(3) Reporting of major ICT-related incidents and voluntary notification of significant cyber threats Loosely related
Only shares CSF RS.CO-02: related, not a mapping
Art.19(4) Reporting of major ICT-related incidents and voluntary notification of significant cyber threats Loosely related
Only shares CSF RS.CO-02: related, not a mapping
CPS 234Para 25Response plans cover all stages and escalationEditorialSame topic: Communication (editorial pick)
2 loosely related (not mappings)
Para 35 Notify APRA of material incidents within 72 hours Loosely related
Only shares CSF RS.CO-02: related, not a mapping
Para 36 Notify APRA of material control weaknesses within 10 business days Loosely related
Only shares CSF RS.CO-02: related, not a mapping
Cyber Essentials—No requirementNo mapping in our dataNo 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 · Loosely related 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.