DORA
DORA Chapter III: ICT-Related Incident Management

DORA DORA-Art.17: ICT-related incident management process

Financial entities shall define, establish and implement an ICT-related incident management process to detect, manage and notify ICT-related incidents, including early warning indicators, procedures to identify/track/log/categorise incidents by priority and severity, roles and responsibilities, and communication plans.

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

What else in your programme already covers this

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

FedRAMP High · 6 controls

  • IR-1 Policy and Procedures
  • IR-4 Incident Handling
  • IR-5 Incident Monitoring
  • IR-6 Incident Reporting
  • IR-7 Incident Response Assistance
  • IR-8 Incident Response Plan

FedRAMP Moderate · 6 controls

  • IR-1 Policy and Procedures
  • IR-4 Incident Handling
  • IR-5 Incident Monitoring
  • IR-6 Incident Reporting
  • IR-7 Incident Response Assistance
  • IR-8 Incident Response Plan

ISO 27001:2022 · 6 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.28 Collection of evidence
  • 6.8 Information security event reporting
  • 8.15 Logging

ISO 27002:2022 · 6 controls

  • 5.24 Information security incident management planning and preparation
  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.28 Collection of evidence
  • 6.8 Information security event reporting
  • 8.15 Logging
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-RS.AN-06 Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved
  • NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared
  • NIST-CSF-RS.MA-02 Incident reports are triaged and validated
  • NIST-CSF-RS.MA-03 Incidents are categorized and prioritized

CIS Controls v8 · 4 controls

  • CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-17.5 Assign Key Roles and Responsibilities
  • CIS-17.9 Establish and Maintain Security Incident Thresholds

NIST SP 800-161 Rev 1 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

  • 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
  • SOC2-CC7.5 CC7.5 Recovering from security incidents

C5 (Germany) · 3 controls

  • C5-SIM-01 Policy for security incident management
  • C5-SIM-02 Processing of security incidents
  • C5-SIM-04 Duty of the users to report security incidents to a central body

NIS2 Directive · 3 controls

  • Art.21.2.b Incident handling
  • Art.23.4.b Submit an incident notification within 72 hours, with an initial assessment and indicators of compromise
  • Art.23.4.c Provide an intermediate report on status when the CSIRT or competent authority requests one
  • CPS230-27 Identification and Escalation of Incidents and Near Misses
  • CFTC-SS-16 Security Incident Response Plan and Testing
  • EBA-GL-3.5.1 ICT incident and problem management

EU AI Act · 1 control

  • PSD2-Art.96 Incident reporting to competent authority (PSD2 Article 96)

GDPR · 1 control

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

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 DORA Chapter III: ICT-Related Incident Management

You are reading one control. How much of DORA have you already done?

DORA DORA-Art.17 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of DORA your existing evidence covers. Hold NIS2 Directive and 17 of 26 DORA 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. 0 were rejected on the NIS2 Directive pair alone.

Query this from an agent

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