What makes a DORA ICT-related incident major?
The first gate is critical-service impact. Delegated Regulation (EU) 2024/1772 treats an incident as major only where it affects critical services and either a successful malicious unauthorised access threshold linked to possible data loss is met, or at least two other materiality thresholds are met.
Critical-service impact is not limited to total outages. It includes ICT services or systems supporting critical or important functions, authorised or supervised financial services, and successful malicious unauthorised access to the financial entity's network and information systems.
- Start with the DORA Article 18 criteria: clients, financial counterparts and transactions; reputational impact; duration and downtime; geographical spread; data losses; criticality of services; and economic impact.
- Confirm whether the affected ICT service, system, or financial service supports a critical or important function before applying the major-incident gate.
- Do not invent lower internal numeric triggers and present them as DORA thresholds. Internal severity triggers can escalate review, but the DORA major classification should map back to the regulatory criteria.
- If actual client, counterparty, transaction, duration, downtime, or loss data is unavailable at classification time, use estimates based on available data and update the report when better figures are available.
Article 18 sets the incident classification criteria and Article 19 establishes reporting of major ICT-related incidents.
Specifies the major-incident classification rule, critical-service criterion, recurring incidents, and materiality thresholds.