ISO 27001:2022 6.8: Information security event reporting

What else in your programme already covers this

This control maps to 56 controls across 36 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CIS Controls v8 · 4 controls

CIS-14.6 Train Workforce Members on Recognizing and Reporting Security Incidents
CIS-14.7 Train Workforce on How to Identify and Report if Their Enterprise Assets are Missing Security Updates
CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents
CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 4 controls

CCM-HRS-11 Security Awareness Training
CCM-LOG-13 Failures and Anomalies Reporting
CCM-SEF-01 Security Incident Management Policy and Procedures
CCM-SEF-08 Points of Contact Maintenance

ISO 27701:2019 · 3 controls

6.13.1 Management of information security incidents and improvements
6.6.3 User responsibilities
6.8 Physical and environmental security

NIST Cybersecurity Framework 2.0 · 3 controls

NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
NIST-CSF-RS.CO-03 Information is shared with designated internal and external stakeholders
NIST-CSF-RS.MA-02 Incident reports are triaged and validated

APRA CPS 234 · 2 controls

CPS234-30 Detection and Response Mechanisms
CPS234-P25 Response Plan Content and Escalation Mechanisms

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

CFTC-SS-16 Security Incident Response Plan and Testing
CFTC-SS-3 Information Security Category

CMMC 2.0 · 2 controls

AT.L2-3.2.3 Insider Threat Awareness
IR.L2-3.6.2 Incident Reporting

FedRAMP High · 2 controls

AT-2(2) Insider Threat
IR-6 Incident Reporting

FedRAMP Moderate · 2 controls

AT-2(2) Insider Threat
IR-6 Incident Reporting

ISO 27001:2013 · 2 controls

A.16.1.2 Reporting information security events
A.16.1.3 Reporting information security weaknesses

ISO 27002:2022 · 2 controls

5.24 Information security incident management planning and preparation
6.8 Information security event reporting

ISO/IEC 29100:2024 · 2 controls

29100-6.10 Information security
ISO29100-5.10.10 Information Security

NIST SP 800-171 Rev 3 · 2 controls

03.02.01 Literacy Training and Awareness
03.06.02 Incident Monitoring, Reporting, and Response Assistance

SOC 2 · 2 controls

SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents

ACSC Essential Eight · 1 control

E8-APP-ML2 Application Control (ML2)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-40 Define a Security Incident Management Procedure

APRA CPS 230 Operational Risk Management · 1 control

CPS230-27 Identification and Escalation of Incidents and Near Misses

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-15 User education (Limited)

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-STEP5 Step 5 - Manage and report security incidents

Australia My Health Records Act 2012 · 1 control

MYHR-ENF-1 Mandatory data breach notification

Authorised Economic Operator (AEO) Programmes - Global Standards · 1 control

AEO-10 Education, Training and Awareness

Azure Security Benchmark · 1 control

ASBv3-IR-2 Preparation - setup incident notification

C5 (Germany) · 1 control

C5-SIM-04 Duty of the users to report security incidents to a central body

COBIT 2019 · 1 control

DSS02.02 DSS02.02 Record, classify and prioritize requests and incidents

DORA · 1 control

DORA-Art.17 ICT-related incident management process

EU AI Act · 1 control

EUAI-Art.87 Reporting of infringements and protection of reporting persons

HIPAA Security Rule · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

ISO/IEC 42001:2023 · 1 control

A.3.3 Reporting of concerns

NIST SP 800-161 Rev 1 · 1 control

161R1-IR-6 Incident Reporting

NIST SP 800-172 · 1 control

3.2.1e Provide Awareness Training on Advanced Persistent Threat

NIST SP 800-218 · 1 control

SP800-218-RV.1.3 Vulnerability Disclosure Policy

NIST SP 800-53 Rev 5 · 1 control

NIST800-IR-6 IR-6 Incident Reporting

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

PCI DSS 4.0 · 1 control

12.10.1 12.10.1 Incident response plan ready for activation

Turkey Cybersecurity Law (Law No. 7545) · 1 control

7.1.b-report Article 7(1)(b): report vulnerabilities and cyber incidents to the Presidency without delay

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of ISO 27001:2022 have you already done?

ISO 27001:2022 6.8 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.

If you hold NIST SP 800-53 Rev 584.9% covered · 14 gaps If you hold ISO 27001:201383.9% covered · 15 gaps If you hold FedRAMP Moderate80.6% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.2% covered · 24 gaps If you hold C5 (Germany)69.9% covered · 28 gaps If you hold NIST Cybersecurity Framework 2.063.4% covered · 34 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free