cm/controlmapping
Sources
Essential Eight · Logging and incident response (all strategies)
ISM-0140

Cyber security incidents are reported to ASD as soon as possible after they occur or…

frameworkASD Essential Eight sectionLogging and incident response (all strategies) levelsML2, ML3 csf 2.0RS.CO-02 topicsReporting frameworks0 12 0 1
Official textCyber security incidents are reported to ASD as soon as possible after they occur or are discovered.Australian Signals Directorate, Information Security Manual (September 2026). © Commonwealth of Australia, CC BY 4.0

Wrong or missing mapping? Report it

Equivalents of ISM-0140 in other frameworks
FrameworkRequirementTitleLinkSource / reason
NIST CSF 2.0RS.CO-02Internal and external stakeholders are notified of incidentsEditorialSame topic: Reporting (editorial pick)
ISO 27001A.5.5A.6.8Contact with authorities; Information security event reportingEditorialSame topic: Reporting (editorial pick)
2 loosely related (not mappings)
A.5.26 Response to information security incidents Loosely related
Only shares CSF RS.CO-02: related, not a mapping
Clause 7.4 Communication Loosely related
Only shares CSF RS.CO-02: related, not a mapping
CIS v8.1CIS 17.3Establish and Maintain an Enterprise Process for Reporting IncidentsEditorialSame topic: Reporting (editorial pick)
1 loosely related (not mappings)
CIS 17.2 Establish and Maintain Contact Information for Reporting Security Incidents Loosely related
Only shares CSF RS.CO-02: related, not a mapping
SOC 2CC2.3Communication with external partiesEditorialSame topic: Reporting (editorial pick)
PCI DSS12.10.1Incident response plan ready to activateEditorialSame topic: Reporting (editorial pick)
3 loosely related (not mappings)
12.8.2 Written agreements with service providers Loosely related
Only shares CSF RS.CO-02: related, not a mapping
12.8.5 Responsibilities split with each provider documented Loosely related
Only shares CSF RS.CO-02: related, not a mapping
12.10.3 Incident response staff available around the clock Loosely related
Only shares CSF RS.CO-02: related, not a mapping
CMMCIR.L2-3.6.2Incident ReportingEditorialSame topic: Reporting (editorial pick)
1 loosely related (not mappings)
IR.L2-3.6.1 Incident Handling Loosely related
Only shares CSF RS.CO-02: related, not a mapping
800-53IR-6Incident ReportingEditorialSame topic: Reporting (editorial pick)
4 loosely related (not mappings)
IR-4 Incident Handling Loosely related
Only shares CSF RS.CO-02: related, not a mapping
IR-7 Incident Response Assistance Loosely related
Only shares CSF RS.CO-02: related, not a mapping
SR-3 Supply Chain Controls and Processes Loosely related
Only shares CSF RS.CO-02: related, not a mapping
SR-8 Notification Agreements Loosely related
Only shares CSF RS.CO-02: related, not a mapping
HIPAA§164.308(a)(6)(ii)Response and ReportingEditorialSame topic: Reporting (editorial pick)
5 loosely related (not mappings)
§164.308(a)(1)(ii)(D) Information System Activity Review Loosely related
Only shares CSF RS.CO-02: related, not a mapping
§164.308(a)(6) Security Incident Procedures Loosely related
Only shares CSF RS.CO-02: related, not a mapping
§164.314(a)(2)(i) Business Associate Contracts Loosely related
Only shares CSF RS.CO-02: related, not a mapping
§164.314(a)(2)(iii) Business associate contracts with subcontractors Loosely related
Only shares CSF RS.CO-02: related, not a mapping
§164.314(b)(2)(iv) Group Health Plan Implementation Specification Loosely related
Only shares CSF RS.CO-02: related, not a mapping
GDPRArt.33(1)Art.34(1)Notification of a personal data breach to the supervisory authority; Communication of a personal data breach to the data subjectEditorialSame topic: Reporting (editorial pick)
NIS23.3Event reportingEditorialSame topic: Reporting (editorial pick)
2 loosely related (not mappings)
3.5 Incident response Loosely related
Only shares CSF RS.CO-02: related, not a mapping
4.3 Crisis management Loosely related
Only shares CSF RS.CO-02: related, not a mapping
DORAArt.18(1)Art.19(1)Art.19(3)Art.19(4)Classification of ICT-related incidents and cyber threats; Reporting of major ICT-related incidents and voluntary notification of significant cyber threats…EditorialSame topic: Reporting (editorial pick)
CPS 234Para 35Para 36Notify APRA of material incidents within 72 hours; Notify APRA of material control weaknesses within 10 business daysEditorialSame topic: Reporting (editorial pick)
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.