Article 19Reporting of major ICT-related incidents and voluntary notification of significant cyber threats
What it says
1. Financial entities shall report major ICT-related incidents to the relevant competent authority as referred to in Article 46 in accordance with paragraph 4 of this Article.
Where a financial entity is subject to supervision by more than one national competent authority referred to in Article 46, Member States shall designate a single competent authority as the relevant competent authority responsible for carrying out the functions and duties provided for in this Article.
Credit institutions classified as significant, in accordance with Article 6(4) of Regulation (EU) No 1024/2013, shall report major ICT-related incidents to the relevant national competent authority designated in accordance with Article 4 of Directive 2013/36/EU, which shall immediately transmit that report to the ECB.
For the purpose of the first subparagraph, financial entities shall produce, after collecting and analysing all relevant information, the initial notification and reports referred to in paragraph 4 of this Article using the templates referred to in Article 20 and submit them to the competent authority. In the event that a technical impossibility prevents the submission of the initial notification using the template, financial entities shall notify the competent authority about it via alternative means.
DORA, the European Union regulation on digital operational resilience, Article 19Show the rest of the text(20 more paragraphs, about 890 words)
The initial notification and reports referred to in paragraph 4 shall include all information necessary for the competent authority to determine the significance of the major ICT-related incident and assess possible cross-border impacts.
Without prejudice to the reporting pursuant to the first subparagraph by the financial entity to the relevant competent authority, Member States may additionally determine that some or all financial entities shall also provide the initial notification and each report referred to in paragraph 4 of this Article using the templates referred to in Article 20 to the competent authorities or the computer security incident response teams (CSIRTs) designated or established in accordance with Directive (EU) 2022/2555.
2. Financial entities may, on a voluntary basis, notify significant cyber threats to the relevant competent authority when they deem the threat to be of relevance to the financial system, service users or clients. The relevant competent authority may provide such information to other relevant authorities referred to in paragraph 6.
Credit institutions classified as significant, in accordance with Article 6(4) of Regulation (EU) No 1024/2013, may, on a voluntary basis, notify significant cyber threats to relevant national competent authority, designated in accordance with Article 4 of Directive 2013/36/EU, which shall immediately transmit the notification to the ECB.
Member States may determine that those financial entities that on a voluntary basis notify in accordance with the first subparagraph may also transmit that notification to the CSIRTs designated or established in accordance with Directive (EU) 2022/2555.
3. Where a major ICT-related incident occurs and has an impact on the financial interests of clients, financial entities shall, without undue delay as soon as they become aware of it, inform their clients about the major ICT-related incident and about the measures that have been taken to mitigate the adverse effects of such incident.
In the case of a significant cyber threat, financial entities shall, where applicable, inform their clients that are potentially affected of any appropriate protection measures which the latter may consider taking.
4. Financial entities shall, within the time limits to be laid down in accordance with Article 20, first paragraph, point (a), point (ii), submit the following to the relevant competent authority:
(a) an initial notification;
(b) an intermediate report after the initial notification referred to in point (a), as soon as the status of the original incident has changed significantly or the handling of the major ICT-related incident has changed based on new information available, followed, as appropriate, by updated notifications every time a relevant status update is available, as well as upon a specific request of the competent authority;
(c) a final report, when the root cause analysis has been completed, regardless of whether mitigation measures have already been implemented, and when the actual impact figures are available to replace estimates.
5. Financial entities may outsource, in accordance with Union and national sectoral law, the reporting obligations under this Article to a third-party service provider. In case of such outsourcing, the financial entity remains fully responsible for the fulfilment of the incident reporting requirements.
6. Upon receipt of the initial notification and of each report referred to in paragraph 4, the competent authority shall, in a timely manner, provide details of the major ICT-related incident to the following recipients based, as applicable, on their respective competences:
(a) EBA, ESMA or EIOPA;
(b) the ECB, in the case of financial entities referred to in Article 2(1), points (a), (b) and (d);
(c) the competent authorities, single points of contact or CSIRTs designated or established in accordance with Directive (EU) 2022/2555;
(d) the resolution authorities, as referred to in Article 3 of Directive 2014/59/EU, and the Single Resolution Board (SRB) with respect to entities referred to in Article 7(2) of Regulation (EU) No 806/2014 of the European Parliament and of the Council, and with respect to entities and groups referred to in Article 7(4)(b) and (5) of Regulation (EU) No 806/2014 if such details concern incidents that pose a risk to ensuring critical functions within the meaning of Article 2(1), point (35), of Directive 2014/59/EU; and
(e) other relevant public authorities under national law.
7. Following receipt of information in accordance with paragraph 6, EBA, ESMA or EIOPA and the ECB, in consultation with ENISA and in cooperation with the relevant competent authority, shall assess whether the major ICT-related incident is relevant for competent authorities in other Member States. Following that assessment, EBA, ESMA or EIOPA shall, as soon as possible, notify relevant competent authorities in other Member States accordingly. The ECB shall notify the members of the European System of Central Banks on issues relevant to the payment system. Based on that notification, the competent authorities shall, where appropriate, take all of the necessary measures to protect the immediate stability of the financial system.
8. The notification to be done by ESMA pursuant to paragraph 7 of this Article shall be without prejudice to the responsibility of the competent authority to urgently transmit the details of the major ICT-related incident to the relevant authority in the host Member State, where a central securities depository has significant cross-border activity in the host Member State, the major ICT-related incident is likely to have severe consequences for the financial markets of the host Member State and where there are cooperation arrangements among competent authorities related to the supervision of financial entities.
What it means in practice
Major ICT-related incidents must be reported to the relevant competent authority under Article 46, using the Article 20 templates.
Three submissions are required: an initial notification; an intermediate report once the incident or its handling has changed significantly, with updates on each relevant change and on request; and a final report once root cause analysis is complete, with actual impact figures replacing estimates. The time limits are not in the Regulation. They sit in Commission Delegated Regulation (EU) 2025/301, made under Article 20.
Reporting may be outsourced, but the entity stays fully responsible.
Under Article 5(1) of that act, the initial notification is due as early as possible and in any case within four hours from classifying the incident as major and no later than 24 hours from awareness. The intermediate report is due within 72 hours of the initial notification, with an updated report without undue delay and in any case when regular activities have recovered. The final report is due no later than one month after the intermediate report or the latest updated one. If the entity classifies the incident as major only after 24 hours, Article 5(2) still gives four hours from classification. Article 5 also has a weekend and bank-holiday rule, so read it before relying on these limits.
What a supervisor would ask to see: the reporting log, with a copy of every report and the time it was sent (P21-A08, EV-20).
What is in the packs for this
Each one helps with this requirement.
- Excel
DORA Article-to-Control Mapping Library
in DORA ICT Risk & Resilience ReadinessRequirement Library rows RQ-29, RQ-30: Report major incidents on time; Significant cyber threats (optional). Each gives the provision in plain words, what to show and the documents that help. - Excel
DORA Readiness Self-Assessment
in DORA ICT Risk & Resilience ReadinessReadiness items IM-02, IS-01: Major incidents can be reported on time; Information sharing and threat notification: a decision. Each rates how ready the entity is, with the evidence and the gap. - Word
Incident Response Plan
in Security Incident ManagementLists the reporting duties RD-10 to RD-12 that a financial entity follows for a major ICT-related incident. - Excel
Incident Classification, Severity & Escalation Matrix
in Security Incident ManagementThe Reporting Clocks sheet sets the clocks for a major ICT-related incident: RD-10 to RD-12 for the initial notification, intermediate report and final report, and RD-13 for the notice to clients. - Word
Incident Communications Template Set
in Security Incident ManagementMessage CT-04 is the notice to clients whose financial interests are affected. - Excel
EU Incident Notification Timeline Matrix (NIS2, DORA, GDPR)
in Regulatory Incident Notification & ReportingRows RD-10 to RD-12 give the timeline of the initial notification, intermediate report and final report; RD-13 the notice to clients; one row the voluntary notification of a significant cyber threat. - Word
Reportability Decision Model
in Regulatory Incident Notification & ReportingCovers the voluntary notification of significant cyber threats. - Word
Regulatory Notification Operating Procedure
in Regulatory Incident Notification & ReportingThe DORA rows set the reports and their clocks, the follow-up reports, and outsourced reporting (RN-16). - Excel
Regulatory Notification Log
in Regulatory Incident Notification & ReportingThe Submissions and Follow-ups sheets record the initial notification and the intermediate and final reports, each due from the earlier report.
Text: Regulation (EU) 2022/2554, as published in the Official Journal of the European Union, from EUR-Lex. Only the Official Journal text is authentic.