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

> EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA (EU-DORA-2022-2554) refers to an institutional financial benchmark and regulatory standard monitored by ESMA / EBA / EIOPA Joint RTS (EU), currently calibrated at 4 Hours (Major ICT Incident Alert) as of October 2026.

Canonical: https://regtechcodex.org/definitions/eu-dora-2022-2554-eu-digital-operational-resilience-act-dora-ict-risk-4-hour-incident-sla
Last updated: 2026-10-22T08:14:17.363Z

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

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

EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA (EU-DORA-2022-2554) refers to an institutional financial benchmark and regulatory standard monitored by ESMA / EBA / EIOPA Joint RTS (EU), currently calibrated at 4 Hours (Major ICT Incident Alert) as of 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 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.
- [US SEC Regulation S-P Amendments (2024–2026) & Form 8-K Item 1.05: 4-Day & 30-Day Cyber Clocks](https://regtechcodex.org/briefings/sec-regulation-s-p-amendments-form-8-k-item-1-05-cyber-rules) — Dora Operational Ict Compliance. US broker-dealers, Registered Investment Advisers, and public financial issuers face an interlocking triad of SEC cyber clocks: Form 8-K Item 1.05 (4 business days), amended Regulation S-P (72-hour service-provider notice & 30-day customer notice), and proposed/adopted Reg SCI & Rule 10.
- [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 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.
- [NYDFS 23 NYCRR Part 500 (Second Amendment): Class A Audits, 72h Cyber & 24h Extortion Notices](https://regtechcodex.org/briefings/nydfs-23-nycrr-500-ciso-attestation-72h-ransom-extortion-rules) — Dora Operational Ict Compliance. New York’s Department of Financial Services enforces the strictest prescriptive cybersecurity code in the US: 23 NYCRR Part 500 Second Amendment binds NY branches, banks, and BitLicense exchanges with personal CEO + CISO certifications and 24-hour extortion alerts.
- [MiFID II RTS 6 Algorithmic Trading & DORA Resilience: Kill Switches, Collars & Order-to-Trade Ratios](https://regtechcodex.org/briefings/algorithmic-trading-rts-6-dora-article-17-kill-switch-resilience) — Dora Operational Ict Compliance. Runaway trading algorithms can bankrupt an investment firm in 45 minutes (Knight Capital’s $440M loss)—which is why European supervisors now audit MiFID II RTS 6 kill switches, pre-trade risk collars, and Direct Electronic Access gates jointly with EU DORA ICT resilience.
- [Singapore MAS TRM & Notice PSN05/644 vs Australia APRA CPS 230: APAC Operational Resilience Map](https://regtechcodex.org/briefings/mas-trm-guidelines-apra-cps-230-apac-operational-resilience-map) — Dora Operational Ict Compliance. Singapore MAS Notices 644, CMG-N03, and PSN05 enforce a 60-minute initial incident alert and a strict 4-hour rolling 12-month critical-system downtime cap, while Australia’s APRA CPS 230 went live July 1, 2025 alongside EU DORA.
- [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
