Skip to content
RegTech Codex
Directory

Dora Operational Ict Compliance

EU DORA Regulation (EU) 2022/2554 Master Guide: ICT Risk, 4h/72h Reporting, RoI & TLPT (2026)

Fully applicable across 22,000+ European financial entities since January 17, 2025, Regulation (EU) 2022/2554 (DORA) replaces fragmented national IT outsourcing guidance with a binding five-pillar law backed by Joint ESA Regulatory Technical Standards and direct CTPP oversight.

By Victoria Ashworth, LL.M, CAMSReview not recorded
EU DORA Regulation (EU) 2022/2554 Master Guide: ICT Risk, 4h/72h Reporting, RoI & TLPT (2026) — RegTech Codex 2026 quantitative & supervisory data card
RegTech Codex (EU DORA Third-Party ICT Risk, Incident Reporting Timelines & TLPT Testing): Five-pillar DORA architecture: RTS ICT controls, 4h/72h/1m incident SLAs, xBRL-CSV RoI, TLPT, and CTPP oversight.Source: RegTech Codex Institutional Research DeskLicense: CC-BY-4.0

On January 17, 2025, European financial technology compliance crossed a permanent watershed: Regulation (EU) 2022/2554 on Digital Operational Resilience for the Financial Sector (DORA)—together with over a dozen binding Level-2 Regulatory Technical Standards (RTS) and Implementing Technical Standards (ITS) drafted jointly by the European Banking Authority, ESMA, and EIOPA—entered direct legal force across all 27 EU Member States. Supervised on-the-ground by the European Central Bank, France ACPR, AMF, Netherlands DNB, AFM, and Poland KNF under EU DORA Regulation 2022/2554 Core Standards, DORA 4-Hour Incident SLA Rules, and 2026 DORA Benchmark Controls, global financial groups operating EU entities—including Coinbase, Anycoin Direct, CMC Markets, ICAP, and Exness—must demonstrate continuous code-level, cloud-level, and contract-level resilience. Explore every engineering workstream across our EU DORA & ICT compliance topic hub.

Five-Pillar Statutory Architecture of Regulation (EU) 2022/2554 (DORA)#

Unlike high-level principles guidelines (legacy EBA/GL/2019/02 Outsourcing), DORA codifies granular technical schemas, stopwatch reporting deadlines, and personal management-body liability:

Quantitative Distribution · Core Articles & Level-2 RTS/ITS
Core Articles & Level-2 RTS/ITSPrimary Engineering Deliverable
01Pillar 1: ICT Risk Manageme…Arts. 5–16 + RT…02Pillar 2: ICT Incident Repo…Arts. 17–23 + R…03Pillar 3: Digital Resilienc…Arts. 24–27 + T…04Pillar 4: ICT Third-Party R…Arts. 28–44 + I…05Pillar 5: Threat Intel Shar…Art. 45 (FS-ISA…
DORA Statutory PillarCore Articles & Level-2 RTS/ITSPrimary Engineering DeliverableSupervisory Gate / Penalty LeverCross-Border Global Equivalent
Pillar 1: ICT Risk ManagementArts. 5–16 + RTS (EU) 2024/1774Board-approved ICT Risk Framework, asset inventory, cryptographic key lifecycle (Art. 9), immutable backup DR (Art. 11–12), Art. 16 simplified trackNCA administrative fines + personal Art. 5 management-body accountabilityNYDFS 23 NYCRR 500, MAS TRM
Pillar 2: ICT Incident ReportingArts. 17–23 + RTS (EU) 2024/1772 & 2025/301Automated Major Incident classifier (7 criteria), <=4h Initial / <=72h Intermediate / <=1m Final NCA reports + significant cyber threat sharingMandatory client notification if financial interests harmed (Art. 19(3))SEC Reg S-P / Form 8-K Item 1.05
Pillar 3: Digital Resilience TestingArts. 24–27 + TLPT RTS (TIBER-EU)Annual vulnerability/source-code/gap scans (Art. 25) + 3-year live-production TLPT Purple/Red-Teaming (Art. 26) for systemic entitiesNCA TLPT Attestation Certificate (blocks uncertified internal-only red teams)UK CBEST, HKMA iCAST, CORIE
Pillar 4: ICT Third-Party Risk (TPRM)Arts. 28–44 + ITS (EU) 2024/2956 (RoI)15-template xBRL-CSV Register of Information (RoI), mandatory Art. 30 contract clauses, exit drills, RTS subcontracting chains, Joint ESA CTPP OversightCTPP penalty up to 1% daily global turnover (Art. 35); NCA order to terminate vendor!UK Critical Third Parties (CTP), APRA CPS 230
Pillar 5: Threat Intel SharingArt. 45 (FS-ISAC / MISP / STIX 2.1)Trusted financial-community IOC & TTP sharing enclaves under TLP traffic-light & GDPR/competition guardrailsNCA notification when joining/leaving Art. 45 intelligence-sharing circleUS CISA AIS, UK CiSP
End-to-end EU DORA operational compliance architecture linking asset inventories, RoI xBRL-CSV, SIEM 4h/72h incident reporting, and TIBER-EU TLPT
End-to-end EU DORA operational compliance architecture linking asset inventories, RoI xBRL-CSV, SIEM 4h/72h incident reporting, and TIBER-EU TLPTVerified Exhibit

Our engineering team decomposed every Level-2 RTS/ITS and cross-border divergence into dedicated operational runbooks:

Quantitative DORA Major-Incident Classification & Composite Readiness Formula#

Under Commission Delegated Regulation (EU) 2024/1772, an ICT-related incident classifies as Major automatically whenever Critical Services Affected == 1 AND either Malicious Unauthorized Access to Critical Data == 1 OR >= 2 of 6 Secondary Materiality Thresholds (Clients/Counterparties > 10% or > 100,000, Transactions > 10% value/volume, Duration > 2h downtime or > 24h incident, Data Loss, Reputational, Economic > EUR 100k + Cross-Border) breach:

Formula or model from the articleNot independently verified
Is_Major_DORA_Incident = I( Critical_Services_Affected == 1 ) * max( I( Malicious_Critical_Data_Breach == 1 ), I( sum_(m=1..6) Threshold_Hit(m) >= 2 ) )
  • TInitialDeadline = min( TDetect + 24h, TClassified_Major + 4h )
  • TIntermedDeadline = TInitialSubmitted + 72h
  • TFinalDeadline = TIntermedSubmitted + 1CalendarMonth
  • DORAReadinessScore = 0.25 * RTS1774Controls + 0.25 * RoIxBRLValid + 0.20 * SLA4hDrillPass + 0.15 * Art30Contracts + 0.15 * DRImmutablePass
Top EU DORA supervisory dry-run and Day-1 inspection deficiencies identified by ESAs and National Competent Authorities (2024-2026)
Top EU DORA supervisory dry-run and Day-1 inspection deficiencies identified by ESAs and National Competent Authorities (2024-2026)Verified Exhibit

Why the Joint ESA Dry-Run Rejected 93.5% of Initial Registers of Information#

During the European Supervisory Authorities' landmark DORA Dry-Run across nearly 1,000 banks, insurers, brokers, and market infrastructures, 93.5% of initial Register of Information (RoI) packages failed automated data-quality checks—primarily because procurement teams stored PDF contracts in SharePoint lacking valid active 20-character GLEIF LEIs (or European Unique Identifiers EUID for EU vendors) for US/Asian SaaS suppliers and fourth-party cloud hosts, or broke relational foreign-key integrity between RT.02.01 (contractual arrangements) and RT.05.02 (ICT service supply chains)!

Synchronizing EU DORA With MiCA Crypto Custody, CASS 10 & Recordkeeping#

Connect your DORA operational resilience program directly across MiCA Article 75 HSM custody & statutory hack liability, FCA CASS 10 insolvency-proof IT resolution packs, and EMIR Refit / MiFIR automated trade-reporting failover.

Frequently asked questions

Which financial entities fall within the mandatory scope of EU DORA Article 2?

Article 2(1) captures 21 regulated entity types operating in the EU: credit institutions, payment and e-money institutions, MiFID investment firms, MiCA crypto-asset service providers (CASPs), CSDs, CCPs, trading venues, trade repositories, AIFMs, UCITS management companies, insurers, credit rating agencies, and statutory crowdfunding providers.

Does the 4-hour DORA initial incident notification clock start at detection or at Major classification?

Under Commission Delegated Regulation (EU) 2025/301 (RTS on incident reporting timelines), the 4-hour countdown starts from the moment the financial entity CLASSIFIES the incident as Major (provided classification happens promptly upon detection, and no later than 24 hours after initial detection when automated data collection requires validation).

What is the DORA Register of Information (RoI) and how do NCAs collect it?

Under DORA Article 28(3) and Commission Implementing Regulation (EU) 2024/2956 (ITS), every financial entity must maintain a relational 15-template Register of Information (RT.01 to RT.99) mapping all ICT third-party contracts, LEIs, critical functions, and nth-party subcontractors, submitted annually to NCAs in xBRL-CSV plain-CSV packages.

How does EU DORA interact with NIS2 Directive (EU) 2022/2555 for banks and brokers?

Under DORA Article 1(2) and NIS2 Article 4, DORA operates as lex specialis (sector-specific overriding law) for in-scope financial entities—meaning financial firms comply with DORA’s ICT risk, incident reporting, and supervisory rules instead of duplicative general NIS2 provisions.

Publication record

Published
14 November 2026
Updated
14 November 2026
Author
Victoria Ashworth, LL.M, CAMS
Review
Review not recorded
Automated fact check
Passed in the stored pipeline record
Source URLs
4 recorded

AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.

Academic & Institutional Attribution

Cite This Research & Embed Live Data Card

Open Attribution License (CC BY 4.0)

Standard academic & institutional research paper citation format.

Victoria Ashworth, LL.M, CAMS. (2026, November 14). EU DORA Regulation (EU) 2022/2554 Master Guide: ICT Risk, 4h/72h Reporting, RoI & TLPT (2026). RegTech Codex. https://regtechcodex.org/briefings/eu-dora-regulation-2022-2554-ict-risk-tlpt-compliance-hub-2026
Explore Dora Operational Ict Compliance Hub (20) →

RegTech Codex Data, Benchmarks & Contributor Records

EU DORA Regulation 2022/2554 Compliance Master Guide (2026) | RegTech Codex