Legal sources with official primary sources

Printed ·

Skip to main content
Skip to the answer

Back to the act

EU regulatory register · DORA

Article 17ICT-related incident management process

CELEX 32022R2554 · Read on 2026-08-18

Share this page

Short answer

1. Financial entities shall define, establish and implement an ICT-related incident management process to detect, manage and notify ICT-related incidents.

Verbatim from the article. Source: NovaCopilot · https://legal.exploreworldai.com/eu/rattsakter/dora-2022-2554/artikel-17 · Short answer as data · Official text

DORA, digital operational resilience in short

Financial entities must manage ICT risk, report major ICT incidents, test resilience and govern ICT providers by contract.

Source: NovaCopilot

Official text

Read from the EU Publications Office for this CELEX number. The wording stands as published; nothing here is rewritten or summarised.

1. Financial entities shall define, establish and implement an ICT-related incident management process to detect, manage and notify ICT-related incidents.

2. Financial entities shall record all ICT-related incidents and significant cyber threats. Financial entities shall establish appropriate procedures and processes to ensure a consistent and integrated monitoring, handling and follow-up of ICT-related incidents, to ensure that root causes are identified, documented and addressed in order to prevent the occurrence of such incidents.

3. The ICT-related incident management process referred to in paragraph 1 shall:

(a)

put in place early warning indicators;

(b)

establish procedures to identify, track, log, categorise and classify ICT-related incidents according to their priority and severity and according to the criticality of the services impacted, in accordance with the criteria set out in Article 18(1);

(c)

assign roles and responsibilities that need to be activated for different ICT-related incident types and scenarios;

(d)

set out plans for communication to staff, external stakeholders and media in accordance with Article 14 and for notification to clients, for internal escalation procedures, including ICT-related customer complaints, as well as for the provision of information to financial entities that act as counterparts, as appropriate;

(e)

ensure that at least major ICT-related incidents are reported to relevant senior management and inform the management body of at least major ICT-related incidents, explaining the impact, response and additional controls to be established as a result of such ICT-related incidents;

(f)

The article continues in the official text.

Open the article on EUR-Lex

Follow-up questions

Knowledge card

Applies
financial-entity: Define and implement an ICT-related incident management process.
Risk if ignored
high
What to do
Define and implement an ICT-related incident management process.
Deadline
No fixed deadline in the register

card:eu:article:dora--art-17 · sha256 4d56a1a4a56e · Source: NovaCopilot

Risk, sanction and outcome

  • Art. 17 · financial-entity

    Risk: high · Sanction: administrative_fine · Authority: Competent authority (Article 46)

    Decisions applying the provision: none in the register

    Full chain (JSON)

Outcomes are counted from stored judgments that cite the provision verbatim. Source: NovaCopilot

Recitals that carry the interpretation

The recitals in the preamble have no legal force of their own but often decide how the article is read. The links are curated against the official text. Read 2026-08-31.

  • Skäl 41 · Article 17

    Incident reporting: harmonised formats and short deadlines for major ICT incidents.

Guidance and secondary law

Authority guidance and the delegated or implementing acts that fill the article, with the primary source at the issuing body. Read 2026-08-31.

The text is quoted from the official source and is not legal advice. A national court reads the language version that binds in its jurisdiction.

Verifiable trust signals

  • Source-linked answers and explicit evidence gaps
  • Obligations, controls, risks and consequences
  • Stable objects and verifiable checksums
  • Rule-based objects, optional source-linked reasoning
  • Model card, source status and audit

Model cardAudit