Regulatory Technical Standard
DORA Incident Classification RTS
This regulatory technical standard sets the criteria and materiality thresholds that decide whether an ICT-related incidentA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident. is major and must be reported under DORADigital Operational Resilience Act, and when a cyber threatAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. is significant.
- 7 classification criteria
- EUR 100,000 economic impact threshold
- 2 hours downtime threshold for critical services
What Is DORA Incident Classification RTS?
It makes incident classification consistent across the financial sector, so that competent authorities receive reports on the same kind of incidents from all financial entities.
Articles 1 to 7 specify the classification criteria of Article 18 of DORADigital Operational Resilience Act: clients, financial counterparts and transactions affected; reputational impact; duration and service downtime; geographical spread; data losses; criticality of the services affected; and economic impact.
Article 9 sets the materiality thresholds. Clients: more than 10% of the clients using the affected service, more than 100,000 clients, more than 30% of financial counterparts, more than 10% of the daily average number or value of transactions, or relevant clients or counterparts affected. Duration and downtime: longer than 24 hours, or downtime longer than 2 hours for ICTInformation and Communication Technology services supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions.. Geographical spread: impact in two or more Member States. Economic impact: costs and losses that exceed or are likely to exceed EUR 100,000. Reputational impact and data losses have qualitative thresholds.
Under Article 8 an incident is major if it affects critical services and either the threshold for malicious unauthorised access to network and information systems (Article 9(5)(b)) is met, or two or more other thresholds are met. Recurring incidents with the same apparent root cause that occur at least twice in 6 months and together meet the criteria count as one major incident; entities assess them monthly. Article 10 defines significant cyber threatsA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident.: high probability of materialisation, possible impact on critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions. and at least one relevant threshold.
- Full title
- Commission Delegated Regulation (EU) 2024/1772 on the Criteria for the Classification of ICT-Related Incidents and Cyber Threats (DORA Incident Classification RTS)
- Official reference
- Commission Delegated Regulation (EU) 2024/1772
- Type
- Regulatory technical standard
- Issued by
- European Commission
- Adopted
- 13 March 2024
- In force
- 15 July 2024
- Applies from
- 17 January 2025
- Status
- In force and applicable
- Applies to
- Financial entities
- Supplements
- Digital Operational Resilience Act (DORA)
Official text
Verified by
Ahmet Ucar
Principal Consultant (CISSPCertified Information Systems Security Professional, CISMCertified Information Security Manager, CISACertified Information Systems Auditor, CIPP/ECertified Information Privacy Professional/Europe)
Last updated 4 November 2026
Does It Apply to You?
Tools that work with this act, free and without signing up.
What DORA Incident Classification RTS Requires
Articles 1 to 7
Classification criteria
Incidents are assessed on the clients, financial counterparts and transactions affected, reputational impact, duration and service downtime, geographical spread, data losses, the critical services affected and the economic impact.
Articles 8(1) and 9
Major incidents
An incident is major when it has affected critical services and either meets the threshold for malicious unauthorised access in Article 9(5)(b) or meets two or more of the other materiality thresholds.
Article 8(2)
Recurring incidents
Non-major incidents count as one major incident when they occur at least twice within 6 months, share an apparent root cause and together meet the major criteria. Assessed monthly; not for microenterprisesMicroenterprise Under DORA or DORADigital Operational Resilience Act Article 16(1) entities.
Article 10
Significant cyber threats
When a cyber threatAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. counts as significant, so that the entity may notify it voluntarily.
Show All 5 Requirements
Articles 11 and 12
Major incidents relevant in other Member States
When a major incident matters to the competent authorities of other Member States, and what is shared with them.
More Requirements in Related Documents
- DORAthe act it supplements · 7 requirements
| Covered entities | Kind | Article | Where defined |
|---|---|---|---|
| Financial entities | Legal status | Classify ICT-related incidentsA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident. and cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. and report major incidents. | |
| MicroenterprisesMicroenterprise Under DORA and Article 16 entities | Legal status | Classify incidents, but are not required to aggregate recurring incidents. | |
| Credit InstitutionsCredit institutions | Legal status | ||
| Crypto-Asset Service ProvidersCrypto-asset service providers | Legal status | ||
| Electronic Money InstitutionsElectronic money institutions | Legal status | ||
| Insurance and Reinsurance UndertakingsInsurance and reinsurance undertakings | Legal status | ||
| Investment FirmsInvestment firms | Legal status | ||
| Payment InstitutionsPayment institutions | Legal status |
Where it applies: Financial entities authorised or registered in the EU.
Local representative: Not required.
All financial entities within DORADigital Operational Resilience Act, which must classify every ICT-related incidentA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident. and assess cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. with these criteria. The aggregation of recurring incidents does not apply to microenterprisesMicroenterprise Under DORA or to the entities of Article 16(1) of DORADigital Operational Resilience Act.
Major ICT-related incident reports Article 19 DORA; Articles 8-9
When: Initial notification within 4 hours of classification as major and no later than 24 hours after becoming aware; intermediate report within 72 hours; final report within one month (Delegated Regulation (EU) 2025/301).
Initial, intermediate and final reports on incidents classified as major under this regulation.
There are no penalties in this regulation itself. It supplements DORADigital Operational Resilience Act, under which Member States lay down administrative penalties and remedial measures for breaches (Article 50) and may lay down criminal penalties (Article 52); competent authorities apply them.
-
DORA
-
DORA ICT Risk Management RTS: Regulatory Technical Standards on ICT Risk Management
- JC 2024 34: Major ICT Incident Costs and Losses Guidelines
-
DORA Third-Party Policy RTS: Regulatory Technical Standards on the ICT Third-Party Policy
-
DORA Subcontracting RTS: RTS on Subcontracting of ICT Services
-
DORA Register of Information ITS: Implementing Technical Standards on the Register of Information
-
DORA Incident Reporting RTS: Regulatory Technical Standards on Major Incident Reports
- DORA Incident Reporting ITS: Implementing Technical Standards on Incident Reporting Forms and Templates
-
DORA TLPT RTS: Regulatory Technical Standards on Threat-Led Penetration Testing
-
DORA Critical Provider Criteria: Criteria for Designating Critical ICT Third-Party Service Providers
-
DORA Oversight Conditions RTS: Regulatory Technical Standards on the Conduct of Oversight Activities
Each mapping links requirements one by one, with how closely they match and what the other one adds. The full tables are available as spreadsheets.
Latest DORA Incident Classification RTS Updates
DORA Incident Classification RTS Milestones Since 2024
- Applies with DORA
- In force
- Published in the Official Journal
- Adopted by the Commission
How We Help With DORA Incident Classification RTS
Start with an assessment, or have us run the work.
Questions
DORA Incident Classification RTS FAQ: Common Questions Answered
When is an ICT-related incident major under DORA?
When it affects critical services and either involves successful, malicious and unauthorised access to network and information systems that can lead to data losses, or meets two or more of the other materiality thresholds in Article 9 of Delegated Regulation (EU) 2024/1772.
Do recurring minor incidents have to be reported?
Yes, if they are not major on their own but have occurred at least twice within 6 months, have the same apparent root cause and together meet the criteria for a major incident. MicroenterprisesMicroenterprise Under DORA and Article 16 entities are exempt from this aggregation.
Preparing for DORA RTS on incident classification?
Thirty minutes with a GRC+ consultant: we look at your scope, the requirements that apply and where to start.