ISO 27001:2022
Organizational controls – ISO 27001:2022

ISO 27001:2022 5.25: Assessment and decision on information security events

Each information security event is to be assessed and a decision made on whether it counts as an information security incident. Purpose (stated in ISO/IEC 27002:2022): ensures information security events are categorized and prioritized effectively. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 5.25.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 10 controls

FedRAMP High · 9 controls

  • AC-2(12) Account Monitoring for Atypical Usage
  • AU-6 Audit Record Review, Analysis, and Reporting
  • IR-1 Policy and Procedures
  • IR-4 Incident Handling
  • IR-5 Incident Monitoring
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))
  • SA-1 Policy and Procedures
  • SI-4(5) System-Generated Alerts
  • SR-10 Inspection of Systems or Components (SR-10)

FedRAMP Moderate · 9 controls

  • AC-2(12) Account Monitoring for Atypical Usage
  • AU-6 Audit Record Review, Analysis, and Reporting
  • IR-1 Policy and Procedures
  • IR-4 Incident Handling
  • IR-5 Incident Monitoring
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))
  • SA-1 Policy and Procedures
  • SI-4(5) System-Generated Alerts
  • SR-10 Inspection of Systems or Components (SR-10)

CIS Controls v8 · 5 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-13.11 Tune Security Event Alerting Thresholds
  • CIS-17.9 Establish and Maintain Security Incident Thresholds
  • CIS-18.4 Validate Security Measures
  • CIS-8.11 Conduct Audit Log Reviews

PCI DSS 4.0 · 5 controls

  • 10.4.3 10.4.3 Exceptions and anomalies from log review addressed
  • 10.7.1 10.7.1 Service providers detect critical control failures (superseded)
  • 10.7.3 10.7.3 Respond promptly to critical security control failures
  • 12.10.5 12.10.5 Plan covers alerts from security monitoring systems
  • 12.3.2 12.3.2 Targeted risk analysis for each customized-approach requirement

CMMC 2.0 · 4 controls

ISO 27701:2019 · 4 controls

  • 5.6.2 Information security risk assessment
  • 5.8.1 Nonconformity and corrective action
  • 6.13 Information security incident management
  • 6.13.1 Management of information security incidents and improvements

SOC 2 · 4 controls

  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents

COBIT 2019 · 3 controls

  • DSS02.01 DSS02.01 Define classification schemes for incidents and service requests
  • DSS02.02 DSS02.02 Record, classify and prioritize requests and incidents
  • DSS02.04 DSS02.04 Investigate, diagnose and allocate incidents

DORA · 3 controls

HIPAA Security Rule · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

  • ASD37-28 Continuous incident detection and response (Excellent)
  • ASD37-31 Hunt to discover incidents (Very Good)
  • ASBv3-IR-3 Detection and analysis - create incidents based on high-quality alerts
  • ASBv3-IR-5 Detection and analysis - prioritize incidents

C5 (Germany) · 2 controls

  • C5-OPS-13 Logging and Monitoring - Identification of Events
  • C5-SIM-02 Processing of security incidents

ISO 27002:2022 · 2 controls

  • 5.25 Assessment and decision on information security events
  • 6.8 Information security event reporting

NIS2 Directive · 2 controls

  • Art.21.2.b Incident handling
  • Art.23.1 Notify significant incidents to the CSIRT or competent authority, and warn affected service recipients

NIST SP 800-171 Rev 3 · 2 controls

  • 03.06.01 Incident Handling
  • 03.06.02 Incident Monitoring, Reporting, and Response Assistance
  • E8-APP-ML2 Application Control (ML2)
  • ANSSI-HYG-40 Define a Security Incident Management Procedure
  • CPS230-27 Identification and Escalation of Incidents and Near Misses

APRA CPS 234 · 1 control

  • CFTC-SS-16 Security Incident Response Plan and Testing

EU AI Act · 1 control

GDPR · 1 control

  • GDPR-Art.33 Notification of a personal data breach to the supervisory authority

ISO 22301:2019 · 1 control

  • 10.2 Continual improvement

ISO 27001:2013 · 1 control

  • A.16.1.4 Assessment of and decision on information security events

ISO/IEC 42001:2023 · 1 control

  • 10.2 Nonconformity and corrective action

NIST SP 800-172 · 1 control

  • 3.6.1e Establish Security Operations Center (SOC)

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.

Other controls in Organizational controls – ISO 27001:2022

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

ISO 27001:2022 5.25 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.

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.

Query this from an agent

The graph holds this control, the 102 it maps to, and the evidence behind each claim, over MCP and REST.