DORA's 4-Hour Incident Reporting Clock: Why Financial Services Need a Reporting-First Culture
· Regonance Cybersecurity · 9 min read
The Digital Operational Resilience Act (DORA) requires financial entities to submit an initial notification to their national financial authority within 4 hours of classifying an ICT incident as major. That is the tightest incident reporting window in EU regulation — substantially faster than NIS2's 24 hours or GDPR's 72 hours. For financial services organisations, this means the time between an employee spotting a suspicious email and the organisation classifying the incident is mission-critical. A structured reporting culture is the only way to consistently meet the 4-hour deadline.
What DORA Requires: The Three-Phase Reporting Cascade
DORA (Regulation (EU) 2022/2554) has applied across the EU financial sector since 17 January 2025. Its incident management framework, primarily Articles 17 to 23, creates a uniform framework for identifying, classifying, and reporting major ICT-related incidents.
Phase 1: Initial Notification — Within 4 Hours
The initial notification must be submitted within 4 hours of the entity classifying the incident as major. The purpose is speed — regulators need to know that a significant event is unfolding in the financial system.
The 4-hour clock starts from the moment of classification, not from detection or discovery. This distinction matters enormously in practice: your triage-to-classification process is the bottleneck, not your detection capability.
Phase 2: Intermediate Report — Within 72 Hours
The intermediate report provides a more complete picture: impact assessment, containment status, estimated financial impact, and data sensitivity evaluation. The 72-hour deadline runs from the initial notification, not from the incident itself.
Phase 3: Final Report — Within One Month
The final report covers root cause analysis, remediation actions, and process improvements. If the incident is fully resolved before the 72-hour intermediate deadline, entities may submit a combined intermediate/final report.
| Phase | Deadline | Key Content |
|---|---|---|
| Initial notification | 4 hours from classification as major | Incident type, affected services, initial impact |
| Intermediate report | 72 hours from initial notification | Severity, financial impact, data sensitivity, containment |
| Final report | 1 month from intermediate report | Root cause, remediation, lessons learned |
Why 4 Hours Is Structurally Difficult
Twenty-four hours sounds manageable. Four hours does not. According to a 2025 Deloitte survey, 67% of financial entities reported that meeting the 4-hour initial notification deadline was the single most challenging operational requirement under DORA.
The difficulty is not detection — modern SIEMs detect anomalies in near-real-time. The difficulty is classification. Determining whether an ICT incident qualifies as "major" under DORA requires understanding its scope, impact, and data sensitivity. Manual investigation workflows typically consume 75 to 135 minutes per incident before a classification decision can be made.
That leaves, at best, two to three hours for report preparation and submission. If the incident occurs outside business hours — and DORA does not provide for weekend or business-hour exceptions for the initial notification — the window is even tighter.
This is why the pre-classification pipeline matters as much as the post-classification process. The faster an organisation moves from detection to classification, the more time remains for a compliant notification. Employee reporting of suspicious emails is the front end of that pipeline.
How Employee Email Reporting Shortens Time-to-Classification
In a phishing attack against a financial institution, the typical sequence is:
- Phishing email arrives in employee inbox
- Employee interacts (clicks a link, opens an attachment) or employee reports (forwards to security team)
- Technical controls detect anomalous activity (credential theft, malware execution, unusual access patterns)
- Incident response investigates and determines scope
- Classification decision — major or non-major under DORA Article 18
- 4-hour clock starts
The critical gap is between steps 1 and 4. When employees delete suspicious emails or simply ignore them, step 3 (technical detection) becomes the sole trigger — and it often fires only after the attacker has achieved their objective. By the time technical controls detect credential misuse or data exfiltration, the incident is further advanced, the scope is larger, and classification takes longer.
When employees report suspicious emails immediately:
- The security team is alerted before or alongside technical detection, gaining time for triage
- The original phishing email is preserved with headers and metadata, accelerating analysis
- The scope assessment begins earlier — how many employees received similar emails? Who may have clicked?
- Classification happens faster because the team has more context from the start
The practical effect: employee reporting can move the classification decision forward by hours — which, in a 4-hour window, is the difference between compliance and violation.
Business Email Compromise: DORA's Highest-Stakes Scenario
Business email compromise (BEC) is particularly dangerous in financial services because the attack vector — a trusted email requesting a financial transaction — directly targets the organisation's core operations.
A typical BEC attack against a financial entity follows this pattern:
- Attacker compromises or spoofs a vendor, executive, or client email
- Fraudulent email requests a payment, wire transfer, or account change
- Employee processes the request, believing it legitimate
- Financial loss occurs before the compromise is detected
Under DORA, a BEC attack that causes material financial loss or affects critical services is almost certainly a major ICT incident requiring 4-hour notification. The challenge is that BEC attacks often bypass technical controls entirely — there is no malware, no malicious link, no payload for security tools to catch. The only detection mechanism is the human who recognises that something about the email doesn't feel right.
Building a culture where employees report uncertain emails — not just obviously malicious ones — is the single most effective control against BEC in financial services.
The Regulatory Triple-Bind: DORA, NIS2, and GDPR
Financial entities subject to DORA are almost always also subject to NIS2 and GDPR. When a phishing attack compromises customer data, three reporting clocks start simultaneously:
| Regulation | Clock Starts | Deadline | Authority |
|---|---|---|---|
| DORA | Classification as major ICT incident | 4 hours | National financial authority |
| NIS2 | Awareness of significant incident | 24 hours | National CSIRT |
| GDPR Art. 33 | Awareness of personal data breach | 72 hours | Data protection authority |
Each notification goes to a different authority with different content requirements. A single suspicious email report, properly preserved and triaged, produces the evidence base for all three.
Building a DORA-Ready Reporting Culture
Financial entities that take DORA seriously need more than an incident response plan — they need a reporting culture that feeds the classification pipeline:
1. Make reporting frictionless. A dedicated reporting channel — a button in the email client, a dedicated address, or both — must be available to every employee. If reporting requires more than two clicks, adoption will be poor.
2. Set a classification SLA. Design your triage-to-classification process to complete within 1-2 hours, leaving 2-3 hours for report preparation and submission within the 4-hour window.
3. Train for reporting, not just recognition. Traditional security awareness training focuses on spotting phishing. DORA demands more: employees must report what they see, even when they're unsure. The value of reporting an email that turns out to be legitimate is far higher than the cost of investigating a false positive.
4. Rehearse the full cascade. The 4-hour clock does not accommodate a first attempt. Run tabletop exercises that walk through the entire sequence: employee report → triage → classification → notification preparation → submission to the financial authority. Time it. Fix the bottlenecks.
5. Automate where possible. Automated classification against DORA's materiality criteria can reduce the triage bottleneck. But automation requires structured input — which, again, comes from well-preserved employee reports.
Frequently Asked Questions
This article is part of the Every Report Matters knowledge series by Regonance Cybersecurity. For the complete methodology and implementation guidance, explore the Reporting Readiness Kit, the Complete Reporting Playbook, or the Organisational Implementation Package.
Related articles:
NIS2 Incident Reporting: How Suspicious Email Reporting Fits the 24/72-Hour Timeline
NIS2 requires a 24-hour early warning and 72-hour notification for significant incidents. Learn how structured suspicious email reporting helps you meet these deadlines.
· 11 min read
Read article →CRA Article 14 Is Live: What the September 2026 Reporting Deadline Means for Your Organisation
CRA Article 14 has been binding since 11 September 2026. Manufacturers must report actively exploited vulnerabilities within 24 hours. Here's what you need to know.
· 9 min read
Read article →GDPR Article 33 Meets Email Reporting: How a Structured Process Protects Your 72-Hour Window
GDPR Article 33 requires breach notification within 72 hours of awareness. A structured suspicious email reporting process creates the evidence trail and speed you need.
· 9 min read
Read article →Email Reporting for Financial Services: Meeting DORA, NIS2, and GDPR Simultaneously
Financial services face DORA (4h), NIS2 (24h), and GDPR (72h) reporting clocks for the same incident. A single reporting lifecycle satisfies all three.
· 8 min read
Read article →Download the free Every Report Matters Methodology Brief — understand the full methodology before you implement. → Download (email required)