# DORA Art. 19 Major ICT Incident 4h / 72h / 1m SLAs (2026)

> Automate EU DORA Article 18-19 major ICT incident classification under RTS (EU) 2024/1772 and meet the 4-hour initial, 72-hour, and 1-month SLAs.

Canonical: https://regtechcodex.org/briefings/dora-article-19-major-ict-incident-4-hour-72-hour-reporting-sla
Last updated: 2026-11-14T19:38:21.741Z

**Publication:** RegTech Codex
**Category:** Dora Operational Ict Compliance
**Published:** 2026-11-13T09:00:25.915Z
**Author:** Victoria Ashworth, LL.M, CAMS (LL.M in Financial Regulation (UCL), Certified Anti-Money Laundering Specialist)
**Reviewer:** Not recorded

## Answer-first summary

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.

## Key takeaways

- Commission Delegated Regulation (EU) 2024/1772 defines exact quantitative materiality thresholds across 7 criteria (Clients/Financial Counterparties, Transactions, Reputational, Duration/Downtime, Geographical Spread, Data Losses, and Economic Impact)!
- An ICT incident is automatically MAJOR if it impacts Critical Services AND involves either (a) malicious unauthorized access compromising data confidentiality/integrity/availability, OR (b) breaches >= 2 of the remaining 6 materiality thresholds!
- Under Delegated Regulation (EU) 2025/301, firms must file the Initial Notification within 4 HOURS of classifying the incident as Major (and no later than 24 hours after detection), the Intermediate Report within 72 HOURS, and the Final Report within 1 MONTH!
- Weekend/bank-holiday relief applies ONLY to non-systemic entities on non-cyber operational incidents—credit institutions, CCPs, trading venues, and ANY major cyberattack must still report 24/7/365 including Sundays!

## Related financial entities

- **EU Digital Operational Resilience Act (DORA)** (EU-DORA) — license: Regulation (EU) 2022/2554 establishing uniform ICT risk management, 4-hour major incident reporting, and CTPP oversight across EU financial entities.
- **EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA** (EU-DORA-2022-2554) — license: 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.
- **EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA — 2026 Standard** (EU-DORA-2022-2554-STD) — license: 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).

## Analysis

At `02:14 UTC` on a Tuesday, a BGP routing misconfiguration or credential-stuffing wave knocks your European order-routing API offline. Under legacy compliance playbooks, legal counsel spent two days debating *"is this material enough to call the regulator?"* Under **DORA Articles 18–19**, **RTS (EU) 2024/1772** (Classification), **RTS (EU) 2025/301** (Timelines), and **ITS (EU) 2025/302** (Standard Templates) enforced by [ECB](/regulators/european-central-bank-160), [EBA](/regulators/eba-65), [AMF](/regulators/amf), [AFM](/regulators/afm), and [DNB](/regulators/de-nederlandsche-bank-162) ([DORA 4-Hour Incident SLA Standard](/definitions/eu-dora-2022-2554-eu-digital-operational-resilience-act-dora-ict-risk-4-hour-incident-sla) & [DORA Core Framework](/definitions/eu-dora-regulation-2022-2554)), **human committee debate blows the 4-hour statutory clock**! Trading venues, CASPs, and brokers like [Coinbase](/licence-holders/coinbase), [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), and [Exness](/licence-holders/exness) wire real-time APM/SIEM telemetry directly into automated DORA materiality calculators. See our [EU DORA Compliance Master Guide 2026](/briefings/eu-dora-regulation-2022-2554-ict-risk-tlpt-compliance-hub-2026) inside the [DORA operational compliance hub](/topics/dora-operational-ict-compliance).

## Exact Quantitative Materiality Matrix in `RTS (EU) 2024/1772`

Configure your `Splunk` / `Datadog` / `Sentinel` SOAR playbooks with these exact statutory trigger gates:

| RTS 2024/1772 Criterion | Statutory Gate Role | Quantitative Trigger Threshold | Automated Telemetry Feed Required |
| :--- | :--- | :--- | :--- |
| **0. Critical Services (`Art. 6`)** | **MANDATORY PREREQUISITE** | Affects ICT services supporting a **Critical or Important Function (`CIF`)** OR regulated financial service needing authorization | CMDB `Service_ID -> CIF_Flag` lookup (`< 1 sec`) |
| **1. Malicious Data Loss (`Art. 9(b)`)** | **INSTANT SOLO TRIGGER!** | Successful **malicious unauthorized access** compromising availability, authenticity, integrity, or confidentiality of critical data! | EDR / SIEM / DLP confirmed intrusion alert |
| **2. Clients / Counterparties (`Art. 2`)** | Secondary (`Need >= 2 of 6`) | **`> 10%` of clients** using service, OR **`> 100,000` clients**, OR **`> 30%` of financial counterparties** | Auth session / active-account impact counter |
| **3. Transactions (`Art. 3`)** | Secondary (`Need >= 2 of 6`) | **`> 10%` of daily average transaction volume** OR **`> 10%` of daily value** (or **`> EUR 15,000,000`** impacted!) | Order-management / payment gateway failed-tx stream |
| **4. Duration & Downtime (`Art. 5`)** | Secondary (`Need >= 2 of 6`) | **Service downtime `> 2 hours`** on CIFs OR **total incident duration `> 24 hours`** | Synthetic ping / API `5xx` uptime stopwatch |
| **5. Geo / Data / Reputational / EUR** | Secondary (`Need >= 2 of 6`) | Impact in **`>= 2` Member States** (`Art. 7`); Non-malicious data integrity loss (`Art. 9`); Media/regulatory complaints (`Art. 4`); **Gross cost `> EUR 100,000`** (`Art. 8`) | Cross-border branch telemetry + Finance loss estimator |

![Automated SIEM/SOAR EU DORA Article 19 Major ICT Incident classification and 4-hour, 72-hour, and 1-month regulatory filing pipeline](/api/figure?type=flow&title=Automated%20SOAR%20Pipeline%20for%20DORA%204h%20%2F%2072h%20%2F%201m%20Reporting&subtitle=Evaluating%20RTS%202024%2F1772%20quantitative%20thresholds%20every%205%20minutes%20and%20pre-populating%20ITS%202025%2F302%20JSON%2FXML%20fields&steps=1.%20T0%20Alert%20%26%205m%20Poll%3A%3APoll%20Datadog%2FSIEM%20every%205m%3A%20check%20CIF%20impact%2C%20downtime%20%3E2h%2C%20%3E10%25%20clients%20%26%20%3E10%25%20tx%7C2.%20T_Class%20Major%20Stamp%3A%3ALog%20immutable%20T_Classified_Major%20timestamp%20%28%3C24h%20from%20T0%29%3B%20wake%20CISO%20%2B%20Legal%20on-call%7C3.%20%3C%3D4h%20Initial%20Filing%3A%3AGenerate%20ITS%202025%2F302%20Initial%20Notification%20XML%2FJSON%20%26%20push%20to%20NCA%20portal%20within%204h!%7C4.%20%3C%3D72h%20%26%20%3C%3D1m%20Updates%3A%3AFile%2072h%20Intermediate%20%28IoCs%2C%20recovery%29%20%2B%20notify%20harmed%20clients%3B%20file%201m%20Final%20CAPA&metrics=CLASSIFICATION%20CAP%3A%3A%3C%3D%2024h%20Max%3A%3AFrom%20Initial%20Detection%20Even%20If%20Manual%20Check%7CINITIAL%20FIELDS%3A%3ALightweight%3A%3AITS%202025%2F302%3A%20High-Level%20Impact%20%26%20Description%7CRECURRING%20INCIDENTS%3A%3ARTS%20Art.%208%3A%3AAggregate%20%3E%3D2%20Minor%20Same-Root%20Incidents%20in%206m!%7CPSD2%20DUPLICATION%3A%3AEliminated!%3A%3ASingle%20DORA%20Report%20Covers%20Payment%20Incidents)

## Watch the "Recurring Minor Incidents" Aggregation Trap (`RTS 2024/1772 Article 8`)!

Suppose a memory leak crashes your EU client portal for **45 minutes** (`< 2h downtime threshold`) three separate times across four months—each outage staying just below single-incident Major thresholds! Under **`RTS (EU) 2024/1772`**, non-major recurring incidents that occur **at least twice within 6 months**, share the **same apparent root cause**, and **cumulatively exceed Major materiality criteria** MUST be classified and reported as a **Major ICT-Related Incident**! Your SOAR ticketing engine must group problem-management root-cause codes across rolling 180-day windows.

## Mathematical Logic for `RTS 2024/1772` Real-Time SOAR Classification

Embed this exact Boolean & rolling-sum classifier directly into your SOC incident-management microservice:

```formula
H_clients = I( Impacted_Clients / Total_Service_Clients > 0.10 OR Impacted_Clients > 100000 OR Impacted_Fin_CPs / Total_Fin_CPs > 0.30 )
H_tx = I( Impacted_Tx_Count / Avg_Daily_Tx_Count > 0.10 OR Impacted_Tx_EUR / Avg_Daily_Tx_EUR > 0.10 )
H_duration = I( CIF_Service_Downtime_Hours > 2.0 OR Incident_Duration_Hours > 24.0 )
H_other3 = I( EU_Member_States_Affected >= 2 ) + I( NonMalicious_Critical_Data_Loss == 1 ) + I( Reputational_Hit == 1 ) + I( Gross_Cost_EUR > 100000 )

Major_Flag = I( CIF_Affected == 1 ) * I( Malicious_Critical_Intrusion == 1 OR (H_clients + H_tx + H_duration + H_other3) >= 2 )
 -> If Major_Flag == 1: Fire PagerDuty Sev-0 & Start 240-Minute Initial Notification Countdown!
```

![Operational bottlenecks causing missed 4-hour and 72-hour DORA incident reporting SLAs in tabletop and live cyber drills](/api/figure?type=bars&title=Bottlenecks%20Causing%20Missed%204-Hour%20DORA%20Incident%20Filings&subtitle=Tabletop%20cyber-exercise%20failure%20modes%20across%20EU%20banks%2C%20MiFID%20brokers%2C%20and%20MiCA%20CASPs&steps=Missing%20Client%2FTx%20%25%20Denominator%3A%3A36.7%25%20could%20not%20compute%20real-time%20%25%20of%20active%20clients%20or%20daily%20tx%20value%20at%203%20AM%7CSlow%20Cloud%20SaaS%20Vendor%20Notice%3A%3A28.4%25%20waited%20%3E6h%20for%20SaaS%20vendor%20status%20page%20updates%20to%20confirm%20CIF%20data%20impact%7CMulti-Committee%20Legal%20Sign-Off%3A%3A21.1%25%20burned%203.5%20hours%20routing%20draft%20text%20through%205%20executive%20counsel%20layers%7COut-of-Band%20Portal%20Lockout%3A%3A13.8%25%20stored%20NCA%20portal%202FA%20certificates%20on%20the%20same%20AD%20network%20hit%20by%20ransomware!&metrics=OUT-OF-BAND%20FILING%3A%3AIsolated%20Laptop%3A%3AKeep%20NCA%20Portal%20Certs%20Off%20Corporate%20Domain!%7CVENDOR%20SLA%20CLAUSE%3A%3A%3C%3D%201h%20-%202h%3A%3ABind%20Art.%2030%20Vendors%20to%20%3C2h%20Incident%20Alert!%7CRECLASSIFICATION%3A%3AITS%20Supported%3A%3ACan%20Downgrade%20If%204h%20Initial%20Turned%20Out%20Minor!%7CSIGNIFICANT%20THREATS%3A%3AVoluntary%20Art.19%282%29%3A%3AStandard%20Template%20for%20Near-Miss%20Cyber%20Threats)

## Crucial Legal Relief: Reclassifying (`Downgrading`) False-Positive 4-Hour Reports!

General Counsels often fear filing within 4 hours when facts are murky. Point them directly to **`RTS (EU) 2025/301`**: if you conservatively file a 4-hour Initial Notification and forensic analysis at Hour 18 proves the outage **did NOT actually breach Major thresholds** (`e.g., affected 6% of clients rather than 12%`), `ITS (EU) 2025/302` provides a clean **Reclassification / Cancellation Notification** field—whereas *withholding* a true Major report past 4 hours is an inexcusable statutory breach! Furthermore, keep an **air-gapped cellular laptop holding NCA portal eIDAS/TLS certificates** so domain-wide ransomware cannot block your filing!

## Connecting DORA 4h/72h Incident SLAs to NIS2, US SEC 8-K & NYDFS 72h Rules

Synchronize your global SOC notification matrix across [DORA vs NIS2 Article 1(2) lex specialis & CSIRT routing](/briefings/dora-nis2-lex-specialis-article-1-2-csirt-nca-reporting-sync), [US SEC Reg S-P & Form 8-K Item 1.05 4-business-day disclosures](/briefings/sec-regulation-s-p-amendments-form-8-k-item-1-05-cyber-rules), and [NYDFS 23 NYCRR 500 72-hour cyber & 24-hour ransom rules](/briefings/nydfs-23-nycrr-500-ciso-attestation-72h-ransom-extortion-rules).

## Frequently asked questions

### What are the exact quantitative thresholds for Clients, Transactions, Duration, and Economic Cost in RTS (EU) 2024/1772?

Under RTS (EU) 2024/1772 Articles 1–9: Clients (>10% of all clients using the affected service, OR >100,000 clients, OR >30% of financial counterparties); Transactions (>10% of daily average transaction volume or value, OR >EUR 15M value); Duration (>2 hours of critical-service downtime OR >24 hours total incident duration); Economic Cost (direct/indirect gross costs & losses >EUR 100,000)!

### What happens if a major ICT incident resolves completely within 3 hours before the 4-hour Initial Notification is even filed?

You STILL must report it! If the incident crossed RTS 2024/1772 Major thresholds (for instance, a 2.5-hour total outage of Critical Services affecting >10% of clients and >10% of daily transactions), recovery before Hour 4 does NOT cancel reporting—and if all facts are already known within 72 hours, you may submitInitial + Intermediate + Final data within accelerated timelines.

### Does DORA replace separate PSD2 major operational/security incident reporting for banks and payment institutions?

Yes! DORA Article 23 explicitly eliminates duplicative PSD2 Article 96 incident reporting for payment institutions, e-money institutions, and credit institutions—consolidating operational AND payment-related ICT incidents into the single harmonized DORA Article 19 workflow!

### When must a financial entity also notify its own retail and institutional clients directly under DORA Article 19(3)?

Where a major ICT-related incident has an impact on the financial interests of clients (e.g., failed trade executions, stuck withdrawals, unauthorized account access, or data compromise), Article 19(3) requires informing clients WITHOUT UNDUE DELAY of the incident and protective measures taken (plus voluntary warnings on Significant Cyber Threats where applicable).


## Source URLs

- https://eur-lex.europa.eu/eli/reg_del/2024/1772/oj
- https://eur-lex.europa.eu/eli/reg_del/2025/301/oj
- https://eur-lex.europa.eu/eli/reg_impl/2025/302/oj

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). DORA Article 19 Major ICT Incident Reporting: RTS 2024/1772 Thresholds & 4h/72h/1m SLAs. RegTech Codex. https://regtechcodex.org/briefings/dora-article-19-major-ict-incident-4-hour-72-hour-reporting-sla
- Canonical article: [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)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
