Art.18 Classification of ICT-related incidents and cyber threats
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.
Source: DORA (Regulation (EU) 2022/2554), Art.18. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open DORA (Regulation (EU) 2022/2554) in the compliance library.
Applies to the financial entities listed in Article 2. Many duties are lighter or absent for microenterprises and for the entities in Article 16(1); each statement says where. Article 19 carries the reporting clocks of Delegated Regulation (EU) 2025/301, Article 5.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Monthly recurring-incident assessment records (not required of microenterprises or Article 16(1) entities) · Document repository
- Significant cyber threat classification records · Data governance / DLP tooling
governing documentDocuments that govern the control
- Incident classification procedure mapping each DORA Article 18(1) criterion to the Delegated Regulation (EU)/1772 thresholds · Policy repository / GRC workspace
- Classification worksheet per incident recording clients, counterparts, transactions, duration, spread, data loss, critical services and costs · Policy repository / GRC workspace
First move
Common gaps auditors find
- Classification ignores reputational impact or geographical spread
- No monthly check for recurring incidents with the same apparent root cause
- Thresholds taken from internal severity scales instead of Delegated Regulation (EU) 2024/1772
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetArt.17 ICT-related incident management process · Art.19 Reporting of major ICT-related incidents