Get Demo
↑

DORA Major ICT Incident Reporting: Classification, 4-Hour / 72-Hour / 1-Month Deadlines

Major ICT-related incident reporting under DORA: initial notification within 4 hours after classification (and no later than 24 hours from awareness).

Published: September 2026 Compliance · DORA 8–12 min read

Major ICT-related incidents trigger a multi-step reporting chain to competent authorities. Getting the classification decision and the clocks right is an operational design problem — not a one-page policy.

Related: DORA hub · Article 10 detection · ThreatHawk.

Reporting clocks (major ICT-related incidents): initial notification within 4 hours after the incident is classified as major, and in any case no later than 24 hours from becoming aware of the incident; intermediate report within 72 hours of the initial notification; final report within 1 month of the last intermediate report (or of classification where no intermediate applies). Align internal playbooks to Commission Delegated Regulation (EU) 2025/301 and competent-authority channels.

The Three Primary Deadlines

Step
Clock
Purpose (summary)
Initial notification
4 hours after major classification (≤24h from awareness)
Alert the competent authority early with available facts
Intermediate report
72 hours after initial
Update impact, indicators, and handling status
Final report
1 month after last intermediate (or as RTS specifies)
Root cause, remediation, and lessons learned package

Classification First

Clocks for the initial notification run from classification as major (with the hard awareness backstop). Document classification criteria, who can declare “major,” and how secondary/significant incidents escalate. RTS classification criteria and national templates apply — train the SOC and crisis team together.

Operational Prerequisites

How CyberSilo Helps

Wire Detection to the 4h / 72h / 1-Month Chain

ThreatHawk can open major-incident cases with DORA-oriented timelines; CSA stores the notification package.

Frequently Asked Questions

Is the initial notification really 4 hours?

Yes for the post-classification clock: initial notification within 4 hours after classifying the incident as major, and in any case no later than 24 hours from becoming aware — follow Delegated Regulation (EU) 2025/301 and your competent authority’s channel.

What is the intermediate deadline?

An intermediate report within 72 hours of the initial notification.

When is the final report due?

Within one month of the submission of the last intermediate report (or as specified when no intermediate report applies). Confirm the RTS wording your authority expects.

Hub · Pillars · ThreatHawk · CSA

📰 More from CyberSilo

Latest Articles

Stay ahead of evolving cyber threats with our expert insights

Fintech Compliance Automation: Multi-Jurisdiction Requirements (PCI, SOC 2, GDPR, MAS, SAMA)
Compliance
Oct 11, 2026 ⏱ 17 min

Fintech Compliance Automation: Multi-Jurisdiction Requirements (PCI, SOC 2, GDPR, MAS, SAMA)

Harmonize fintech compliance across PCI DSS, SOC 2, GDPR, MAS, and SAMA CSF with unified controls and Compliance Standards Automation.

Read Article
How MSSPs Help Clients Achieve PCI DSS Compliance at Scale
Compliance
Oct 11, 2026 ⏱ 15 min

How MSSPs Help Clients Achieve PCI DSS Compliance at Scale

Learn how MSSPs deliver PCI DSS Requirement 10 and audit-ready evidence at scale with ThreatHawk MSSP SIEM and Compliance Standards Automation.

Read Article
The 5 Biggest Operational Mistakes MSSPs Make When Managing Multiple Client SOCs
Partners
Oct 11, 2026 ⏱ 15 min

The 5 Biggest Operational Mistakes MSSPs Make When Managing Multiple Client SOCs

Avoid the top MSSP multi-tenant SOC mistakes—customization sprawl, weak isolation, alert floods, shallow QBRs, and sloppy onboarding—with ThreatHawk MSSP SIEM and Agentic SOC AI.

Read Article
What Is ISO 27001? A Practical 2026 Guide for Security and GRC Teams
Compliance
Oct 11, 2026 ⏱ 16 min

What Is ISO 27001? A Practical 2026 Guide for Security and GRC Teams

ISO/IEC 27001 explained for 2026: ISMS scope, Annex A controls, certification stages, and how continuous monitoring supports audit-ready evidence.

Read Article
What Is the NIST Cybersecurity Framework? CSF 2.0 Explained for 2026
Compliance
Oct 11, 2026 ⏱ 15 min

What Is the NIST Cybersecurity Framework? CSF 2.0 Explained for 2026

The NIST Cybersecurity Framework (CSF) 2.0 explained: six Functions, Profiles, Tiers, and how to operationalize outcomes with SIEM and GRC in 2026.

Read Article
How NIST Helps Cybersecurity Programs Mature in 2026
Compliance
Oct 11, 2026 ⏱ 14 min

How NIST Helps Cybersecurity Programs Mature in 2026

How NIST publications improve cybersecurity: CSF 2.0, SP 800-53, incident guidance, and practical ways to turn NIST outcomes into SOC metrics and audit evidence.

Read Article
✅ Link copied!