DORA
DORA Chapter III: ICT-Related Incident Management

DORA DORA-Art.18: Classification of ICT-related incidents and cyber threats

What does DORA-Art.18 require?

Financial entities classify ICT-related incidents and assess their impact using: how many clients or financial counterparts are affected or how relevant they are, transaction value or count where relevant, and any reputational impact; the length of the incident and of any service downtime; geographical spread, particularly where more than two Member States are affected; data losses affecting availability, authenticity, integrity or confidentiality; criticality of the services affected; and direct and indirect economic impact in absolute and relative terms. Significant cyber threats are classified by the criticality of services at risk, the clients or counterparts targeted and geographical spread. Thresholds are set by Commission Delegated Regulation (EU) 2024/1772: an incident is major when it has affected critical services and either involves a successful malicious intrusion into its network and information systems (Art. 9(5)(b)) or meets at least two other materiality thresholds (Art. 8(1)); the rule that aggregates recurring incidents into one major incident (Art. 8(2)) does not apply to microenterprises or to Article 16(1) entities.

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

What else in your programme already covers this

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

NIS2 Directive · 3 controls

  • Art.21.2.b Incident handling
  • Art.23.1 Notify significant incidents to the CSIRT or competent authority, and warn affected service recipients
  • Art.23.4.b Submit an incident notification within 72 hours, with an initial assessment and indicators of compromise

CIS Controls v8 · 2 controls

  • CIS-16.6 Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities
  • CIS-17.9 Establish and Maintain Security Incident Thresholds

FedRAMP High · 2 controls

  • IR-5 Incident Monitoring
  • RA-2 Security Categorization

FedRAMP Moderate · 2 controls

  • IR-5 Incident Monitoring
  • RA-2 Security Categorization

ISO 27001:2022 · 2 controls

  • 5.25 Assessment and decision on information security events
  • 5.7 Threat intelligence

ISO 27002:2022 · 2 controls

  • 5.25 Assessment and decision on information security events
  • 5.7 Threat intelligence

NIST SP 800-53 Rev 5 · 2 controls

  • NIST800-IR-5 IR-5 Incident Monitoring
  • NIST800-RA-2 RA-2 Security Categorization

SOC 2 · 2 controls

  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents

C5 (Germany) · 1 control

  • CFTC-SS-16 Security Incident Response Plan and Testing
  • PSD2-Art.96 Incident reporting to competent authority (PSD2 Article 96)

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.18 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 25 it maps to, and the evidence behind each claim, over MCP and REST.