# EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA — 2026 Standard

> EU-DORA-2022-2554 2026 Institutional Benchmark Framework is defined as the standardized quantitative and compliance methodology published by ESMA / EBA / EIOPA Joint RTS governing EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA across EU capital markets (4 Hours Major ICT Incident Alert, October 2026).

Canonical: https://regtechcodex.org/definitions/eu-dora-2022-2554-2026-benchmark-standard
Last updated: 2026-10-22T08:14:17.363Z

## EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA — 2026 Standard (EU-DORA-2022-2554-STD)

- Type: license
- Jurisdiction: EU
- Regulatory body: ESMA / EBA / EIOPA Joint RTS
- Wikidata: Q53536

EU-DORA-2022-2554 2026 Institutional Benchmark Framework is defined as the standardized quantitative and compliance methodology published by ESMA / EBA / EIOPA Joint RTS governing EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA across EU capital markets (4 Hours Major ICT Incident Alert, October 2026).

### Recorded metadata

| Field | Value |
| --- | --- |
| verifiedDate | 2026-10-22 |
| regulatoryBody | ESMA / EBA / EIOPA Joint RTS |
### Related research

- [EU DORA Regulation (EU) 2022/2554 Master Guide: ICT Risk, 4h/72h Reporting, RoI & TLPT (2026)](https://regtechcodex.org/briefings/eu-dora-regulation-2022-2554-ict-risk-tlpt-compliance-hub-2026) — Dora Operational Ict Compliance. 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.
- [DORA Article 28 & ITS (EU) 2024/2956: 15-Template xBRL-CSV Register of Information Guide](https://regtechcodex.org/briefings/dora-article-28-its-2024-2956-register-of-information-templates) — Dora Operational Ict Compliance. Under DORA Article 28(3) and Commission Implementing Regulation (EU) 2024/2956, financial entities must submit a relational 15-table Register of Information in xBRL-CSV format—feeding the Joint ESAs’ quantitative engine that designates Critical ICT Third-Party Providers.
- [DORA Article 19 Major ICT Incident Reporting: RTS 2024/1772 Thresholds & 4h/72h/1m SLAs](https://regtechcodex.org/briefings/dora-article-19-major-ict-incident-4-hour-72-hour-reporting-sla) — Dora Operational Ict Compliance. When a production outage, DDoS wave, or ransomware intrusion strikes an EU financial entity, DORA Articles 18 and 19 start two unforgiving regulatory clocks: quantitative Major classification under RTS 2024/1772 followed by a 4-hour Initial Notification and 72-hour Intermediate Report.
- [DORA Article 26 Threat-Led Penetration Testing (TLPT): TIBER-EU Live Production & Purple Teaming](https://regtechcodex.org/briefings/dora-article-26-tlpt-tiber-eu-purple-teaming-3-year-cadence) — Dora Operational Ict Compliance. Standard staging-environment penetration tests do not satisfy DORA Article 26: systemically important banks, CCPs, trading venues, and top-tier brokers/CASPs must undergo intelligence-led TIBER-EU Red and Purple Team exercises directly against live production systems every three years.
- [DORA Critical ICT Third-Party Providers (CTPPs): Designation Math, Lead Overseers & 1% Daily Fines](https://regtechcodex.org/briefings/critical-ict-third-party-providers-ctpp-lead-overseer-powers) — Dora Operational Ict Compliance. For the first time in European regulatory history, DORA Articles 31 through 44 place hyperscale cloud, market-data, and core-ledger tech giants under direct on-site inspection and penalty jurisdiction of EBA, ESMA, and EIOPA Lead Overseers.
- [DORA Article 30 ICT Contractual Clauses: Two-Tier SaaS Repapering, Audit Rights & Exit Plans](https://regtechcodex.org/briefings/dora-article-30-ict-contractual-clauses-audit-exit-strategies) — Dora Operational Ict Compliance. Every single ICT service agreement signed by an EU financial entity—from core matching engines down to standard non-critical HR SaaS—must contain explicit written clauses mandated under DORA Article 30(2), expanding dramatically under Article 30(3) for Critical Functions.
- [UK Operational Resilience (FCA PS21/3 & PRA SS2/21) vs EU DORA: Cross-Mapping Dual Programs](https://regtechcodex.org/briefings/uk-fca-ps21-3-pra-ss2-21-impact-tolerances-vs-eu-dora-mapping) — Dora Operational Ict Compliance. March 31, 2025 ended the UK’s three-year operational resilience transition period—requiring FCA and PRA firms to remain strictly within Impact Tolerances across all Important Business Services just ten weeks after EU DORA took full legal effect across the Channel.
- [DORA vs NIS2 Directive (Article 1(2) Lex Specialis): Dual-Scope Financial Groups & CSIRT Sync](https://regtechcodex.org/briefings/dora-nis2-lex-specialis-article-1-2-csirt-nca-reporting-sync) — Dora Operational Ict Compliance. While DORA acts as sector-specific lex specialis overriding NIS2 for regulated banks, brokers, and CASPs, mixed corporate groups containing unregulated IT holding companies, data centers, or cloud subsidiaries frequently trigger BOTH DORA and NIS2 simultaneously!
- [DORA Subcontracting RTS (EU) 2025/532: Nth-Party ICT Supply-Chain Monitoring & Exit Triggers](https://regtechcodex.org/briefings/nth-party-ict-subcontracting-rts-critical-function-chain-risk) — Dora Operational Ict Compliance. Adopted on March 24, 2025 as Commission Delegated Regulation (EU) 2025/532, DORA’s Subcontracting RTS closes the fourth-party blind spot—forcing financial entities to assess chain complexity before contract signature and hold contractual termination rights over material subcontractor changes.
- [AI & LLM Governance in Trade Surveillance & AML: EU AI Act (2024/1689), DORA & SR 11-7](https://regtechcodex.org/briefings/ai-ml-model-governance-trade-surveillance-eu-ai-act-dora-audit) — Dora Operational Ict Compliance. Deploying machine-learning anomaly detectors and generative-AI SAR narrative copilots inside banks and brokerages triggers overlapping mandates across EU AI Act Regulation (EU) 2024/1689, ESMA’s MiFID II AI Statement, DORA third-party ICT rules, and US SR 11-7.
- [DORA Article 29 Cloud Concentration Risk: Multi-Region vs Multi-Cloud RTO/RPO Engineering](https://regtechcodex.org/briefings/multi-cloud-concentration-risk-active-active-failover-rto-rpo) — Dora Operational Ict Compliance. Does EU DORA Article 29 force every bank and broker to run simultaneous active-active workloads across AWS AND Azure? No—but claiming "easy substitutability" on paper without container portability, DNS decoupling, and live region-evacuation drills fails supervisory scrutiny.
- [DORA RTS (EU) 2024/1774 Articles 6 & 7: Encryption, HSM Key Lifecycle & Post-Quantum Readiness](https://regtechcodex.org/briefings/dora-rts-ict-risk-management-encryption-cryptographic-key-life) — Dora Operational Ict Compliance. Delegated Regulation (EU) 2024/1774 turns cryptographic hygiene into binding statute: Articles 6 and 7 require financial entities to encrypt data at rest, in transit, and where necessary in use, maintain a Key Register, and build Post-Quantum agility.
- [DORA Article 16 Simplified ICT Risk Framework & Microenterprise Proportionality Carve-Outs](https://regtechcodex.org/briefings/dora-simplified-ict-risk-framework-article-16-exempt-entities) — Dora Operational Ict Compliance. Small and non-interconnected MiFID Class-3 investment firms, exempt payment institutions, and microenterprises (<10 staff and <EUR 2M turnover) do NOT face the exact same DORA burden as global universal banks—provided they map Article 2(3), Article 4, and Article 16 accurately!
- [DORA Articles 11 & 12 Ransomware Recovery: Immutable Air-Gapped Vaults & Clean-Room Restore](https://regtechcodex.org/briefings/dora-article-11-ict-business-continuity-ransomware-immutable-dr) — Dora Operational Ict Compliance. Modern ransomware crews delete cloud snapshots, poison Active Directory domain controllers, and lurk inside backup catalogs for 45 days before detonating—which is why DORA Article 12 mandates physically and logically segregated immutable backups tested via clean-room restoration.
- [DORA Article 45 Cyber Threat Intelligence Sharing: STIX 2.1, TAXII, MISP & GDPR/Antitrust Guardrails](https://regtechcodex.org/briefings/dora-article-45-cyber-threat-intelligence-sharing-tlp-stix-taxii) — Dora Operational Ict Compliance. Pillar 5 of EU DORA (Article 45) creates a clear statutory safe-harbor framework encouraging financial entities to exchange Indicators of Compromise, TTPs, and cyber alerts via trusted FS-ISAC, CIISI-EU, and MISP communities—subject to strict GDPR, TLP, and NCA notification rules.
- [DORA Article 5 Management Body Liability: Board ICT Training, Budgets & CISO Independence](https://regtechcodex.org/briefings/dora-article-5-management-body-ict-liability-budget-governance) — Dora Operational Ict Compliance. Under EU DORA Article 5, the Management Body (Board of Directors) cannot delegate away ultimate legal accountability for ICT risk: directors must personally approve digital resilience strategies, ring-fence sufficient ICT budgets, and complete ongoing mandatory cybersecurity training.
- [EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA: Statutory Capital Floors, Prudential Ratios & Licensing Thresholds (4 Hours Major ICT Incident Alert Benchmark)](https://regtechcodex.org/briefings/eu-dora-2022-2554-statutory-thresholds-and-capital-floors) — EU MiCA & DORA Compliance. EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA (EU-DORA-2022-2554) stands at 4 Hours (Major ICT Incident Alert) (Source: ESMA / EBA / EIOPA Joint RTS, 2026-10-20), governing initial permanent
