Every one of the 64 articles with its official heading, a direct link into the EUR-Lex text, the delegated or implementing act it empowers, and where this site explains it. The regulation itself is on EUR-Lex, in 24 languages: this page is the way in.
Signed 14 December 2022, StrasbourgOJ L 333, 27.12.2022, p. 1Applies since 17 January 202564 articles, 9 chapters, 106 recitals24 official languagesUpdated October 2026
DORA is Regulation (EU) 2022/2554. It was signed on 14 December 2022, published in the Official Journal on 27 December 2022, and has applied since 17 January 2025. It runs to 64 articles across nine chapters, preceded by 106 recitals, and exists in the 24 official languages of the European Union. Only the EUR-Lex version is authoritative, so this page does not reproduce it: it indexes it, article by article, and shows which technical standard sits behind each mandate.
The act, formally
If you need to cite DORA in a policy, a board paper or a contract, these are the references that matter. The ELI link is the stable one: it does not break when EUR-Lex changes its interface.
Short name
DORADigital Operational Resilience Act
Formal citation
Regulation (EU) 2022/2554of the European Parliament and of the Council of 14 December 2022
Official Journal
OJ L 333, 27.12.2022, p. 1Published 27 December 2022
CELEX number
32022R2554The identifier to use in EUR-Lex searches
Entry into force
16 January 2023Article 64: the twentieth day after publication
Date of application
17 January 2025Article 64, second paragraph
Structure
9 chapters, 64 articles106 recitals, no annex
Legal form
RegulationDirectly applicable, no national transposition
A regulation, not a directive. Search queries often say "DORA directive". It is a regulation: it binds in its entirety and applies directly in all Member States, with no transposing national law in between. Article 64 says so in one sentence: "This Regulation shall be binding in its entirety and directly applicable in all Member States." The practical consequence is that there is no national version to look for, with one exception: the administrative penalty regime, which Article 50 leaves to Member State law.
Get the official text
Both links below go to EUR-Lex, the Official Journal's own publication service. The HTML version carries stable anchors, so #art_30 opens the contractual clauses directly instead of the top of the document. Every article number in the index further down uses those anchors. The PDF is the Official Journal typesetting, which is the version to attach to a board pack or an audit file.
Why this page does not host a copy. A regulation is amended, corrected and consolidated. A PDF sitting on a third-party site is a snapshot that silently goes stale, and anyone citing it in a supervisory file inherits that risk. EUR-Lex publishes the authentic text and its consolidated versions, so that is where the links point. What this site adds is the index, the mapping to the technical standards, and the practitioner reading.
All 24 language versions
Every language version is equally authentic. This matters more than it sounds: if your compliance documentation, your contracts or your board minutes are not in English, use the official terminology of your own language version rather than translating the English back. The vocabulary is fixed, and competent authorities use it.
Headings are the official ones. Each number links into the EUR-Lex text at that article. A purple tag means the article carries a mandate that the Commission has since filled with a delegated or implementing act; a blue tag points to where this site explains what the article asks for in practice.
DORA itself sets the obligations; the detail lives in the level-2 acts the Commission adopts on the mandates written into the articles. All of them are now adopted. The column that matters operationally is the middle one: it tells you which article you are actually complying with when you implement a technical standard. The same table, with the practitioner reading of each act, is on the RTS and ITS page.
What it covers
DORA mandate
Legal act
Status
RTS on the ICT risk management framework and the simplified framework
ESA guidelines, comply or explain at national level
A detail worth holding on to: the last row is not a technical standard. Joint Guidelines are an ESA instrument that competent authorities apply on a comply-or-explain basis, which is a different legal weight from a Commission Delegated Regulation. Treating the two as interchangeable in a gap analysis is a common and avoidable error.
The dates that are actually in the text
Three dates come from the regulation itself. Everything else circulating as a "DORA deadline" comes from a level-2 act, from a competent authority's own calendar, or from nowhere at all.
Date
What the text says
Where
16 January 2023
Entry into force, the twentieth day after publication in the Official Journal
By this date the Commission must carry out a review and report to the Parliament and the Council, covering among other things the CTPP designation criteria and the voluntary nature of cyber threat notification
17 January 2028 is a review clause, not a compliance deadline. It is read online as a second DORA deadline, often attached to threat-led penetration testing. Article 58 says what it says: the Commission reviews and reports. Nothing in it moves an obligation for a financial entity. If a project plan carries a 2028 milestone, it should trace back to something other than this article.
Reading it without reading all 64 articles
Not every article creates work for a financial entity. Roughly half of the text is supervisory machinery: how the European Supervisory Authorities organise oversight of designated providers, how authorities cooperate, how fees are charged. Useful to know it exists, not something to implement. The reading below is ours, not the regulation's, and it is meant as a route through the text rather than a substitute for it.
Article 3: the definitions, and in particular point (22), the critical or important function. Almost every obligation downstream is scoped by that definition, which is why it has a page of its own.
Articles 5 and 6: board accountability and the ICT risk management framework. This is the document a competent authority asks for first.
You appear in Article 2(1), at point (u), but you are not a financial entity: Article 2(2) reserves that term for points (a) to (t). The obligations that reach you arrive through your clients' contracts under Article 30, and, only if the European Supervisory Authorities designate you as critical, through the oversight framework in Articles 31 to 44. The distinction is the single most misread thing about DORA on the supplier side, and it is set out in the guide for suppliers.
What is machinery, not homework
Articles 32 to 44 build and run the oversight framework for designated critical providers: the Lead Overseer, its powers, inspections, fees, international cooperation. Articles 46 to 56 organise competent authorities, their cooperation, professional secrecy and data protection. Article 57 is the delegation mechanism. Articles 59 to 63 amend five earlier regulations, including EMIR, CSDR and MiFIR. None of these creates a deliverable for an ordinary financial entity, and time spent reading them is better spent on Chapters II to V.
Who the regulation applies to
Article 2(1) lists the entities in scope, from point (a) to point (u). Points (a) to (t) are collectively "financial entities" under Article 2(2): credit institutions, payment institutions, account information service providers, electronic money institutions, investment firms, crypto-asset service providers and issuers of asset-referenced tokens, central securities depositories, central counterparties, trading venues, trade repositories, managers of alternative investment funds, management companies, data reporting service providers, insurance and reinsurance undertakings, insurance and reinsurance intermediaries, institutions for occupational retirement provision, credit rating agencies, administrators of critical benchmarks, crowdfunding service providers and securitisation repositories. Point (u) adds ICT third-party service providers.
The list is closed, and the legal category decides the regime. That is why the scope tool asks for your authorisation rather than your size or your sector, and why Article 16, the simplified framework, is available only to the categories the article itself names. Being small does not get you there if your legal category is not on that list.
Where can I download the DORA regulation as a PDF?
From EUR-Lex, which publishes the Official Journal typesetting for each of the 24 official languages. The English PDF is at eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32022R2554, and the stable entry point for any language is the ELI address eur-lex.europa.eu/eli/reg/2022/2554/oj. Avoid copies hosted elsewhere: a regulation is amended and consolidated over time, and a snapshot goes stale without saying so.
Is DORA a regulation or a directive?
A regulation. Article 64 states that it is binding in its entirety and directly applicable in all Member States, so there is no national transposing law to look for. The one place national law does intervene is the administrative penalty regime: Article 50 requires Member States to lay down the rules, which is why exposure depends on your competent authority rather than on a figure in the regulation.
How many articles does DORA have?
64 articles in nine chapters, preceded by 106 recitals, with no annex. Chapter II covers ICT risk management (Articles 5 to 16), Chapter III incident management and reporting (17 to 23), Chapter IV resilience testing (24 to 27), Chapter V ICT third-party risk and the oversight framework (28 to 44), and Chapter VI information sharing (45). The rest organises competent authorities, delegation and amendments to earlier regulations.
What is the CELEX number of DORA, and what is it for?
CELEX:32022R2554. It is the identifier the EU institutions use for a legal act, and it is the most reliable way to find the right document in EUR-Lex: searching the title returns proposals, corrigenda and related acts, whereas the CELEX number returns the act itself. The ELI address, eur-lex.europa.eu/eli/reg/2022/2554/oj, is the stable URL built on the same identity.
Which version is authoritative when language versions differ?
All 24 language versions are equally authentic: none is a translation of another in legal terms. In practice, use the version of your own working language for internal documentation and contracts, since competent authorities use that terminology, and cross-check the English where a term carries consequences. If two versions genuinely diverge on a point that matters, that is a question for legal counsel, not a drafting preference.
Does the regulation itself contain the detailed technical requirements?
No. DORA sets the obligations and writes mandates into specific articles; the detail arrives through Commission Delegated and Implementing Regulations. The ICT risk management detail is in Delegated Regulation (EU) 2024/1774 on the mandate in Articles 15 and 16(3); incident classification in 2024/1772 on Article 18(3); the Register of Information template in Implementing Regulation (EU) 2024/2956 on Article 28(9). Implementing a technical standard without knowing which article it serves makes an audit trail hard to defend.
Is 17 January 2028 a DORA deadline?
No. It is the date by which, under Article 58, the Commission must carry out a review and report to the European Parliament and the Council. The review covers the CTPP designation criteria, the voluntary nature of significant cyber threat notification, and the third-country regime. It moves no obligation for a financial entity. The only date of application in the regulation is 17 January 2025.
Does DORA apply to an ICT provider that is not a financial entity?
The regulation lists ICT third-party service providers in Article 2(1)(u), but Article 2(2) reserves the term financial entity for points (a) to (t). A provider therefore does not carry the financial entity obligations. What reaches it is contractual, through the clauses its clients must impose under Article 30, and, only where the European Supervisory Authorities designate it as critical, the oversight framework in Articles 31 to 44.
Where to go next
The text tells you what is required. These pages tell you what to do about it, in the order most teams actually need it.