Notification Clocks
What starts a breach reporting deadline, not only how long it runs.
A general reference compiled from the primary texts on each row. It is not legal advice. What applies depends on where an organization operates, its sector and its contracts, and these rules change.
Read the column for what starts the clock first. Two regimes with the same 72 hours can have deadlines days apart, because one starts at awareness and the other at a materiality decision.
10 rows.
| Rule | What starts the clock | Deadline |
|---|---|---|
| GDPR: personal data breach | Becoming "aware" of a personal data breach. Awareness means a reasonable degree of certainty that a breach occurred, not certainty about its full scope, so the clock generally starts before the investigation finishes. | 72 hours to the supervisory authority. Data subjects "without undue delay" where the risk to them is high. |
| UK GDPR / Data Protection Act 2018 | Awareness of a personal data breach, on the same standard as EU GDPR. | 72 hours to the ICO. Individuals without undue delay where the risk is high. |
| NIS2 Directive | Becoming aware of a significant incident. | Early warning within 24 hours, incident notification within 72 hours, final report within one month. |
| DORA | Classification of an ICT-related incident as major. | Initial notification, then intermediate and final reports on the timetable set by the regulatory technical standards. |
| HIPAA Breach Notification Rule | Discovery of a breach of unsecured PHI. Discovery is the first day it is known, or would have been known with reasonable diligence, which means "we had not looked" does not delay the clock. | 60 days to individuals. Breaches of 500+ records: HHS and prominent media in the state within 60 days. Under 500: HHS annually, within 60 days of year end. |
| SEC cybersecurity disclosure | Determining that an incident is material. Note the shape: the clock starts at the materiality determination, and that determination must itself be made without unreasonable delay after discovery. | Form 8-K Item 1.05 within four business days of the materiality determination. |
| CIRCIA | Reasonable belief that a covered cyber incident has occurred; separately, making a ransom payment. | 72 hours for a covered incident; 24 hours for a ransom payment. |
| US state breach notification laws | Discovery of unauthorised acquisition of personal information, defined slightly differently in every state. | Most say "without unreasonable delay". A number set an outer bound, commonly 30, 45 or 60 days. Several also require notifying the state attorney general above a record threshold. |
| PCI DSS | Suspected or confirmed compromise of cardholder data. | Immediately, per the card brands' own programs. Contractual rather than statutory. |
| Australia: Notifiable Data Breaches | Awareness of reasonable grounds to believe an eligible data breach occurred, or grounds to suspect one. | Where suspected, assess within 30 days. Once believed, notify as soon as practicable. |