What counts as a personal-data breach
GDPR defines a personal-data breach as a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, personal data. That covers three overlapping failure modes: a confidentiality breach (unauthorized access or disclosure), an integrity breach (unauthorized alteration), and an availability breach (loss of access to, or destruction of, the data).
The availability case is the one teams often miss. Ransomware that encrypts a database of personal data is a breach even if nothing is exfiltrated, because the data has been rendered unavailable. The trigger is the compromise of personal data, not whether an attacker walked out with a copy.
The 72-hour rule
The clock runs from awareness, the point at which you have a reasonable degree of certainty that a security incident has compromised personal data, not from when the breach happened. From that moment, a controller must notify the competent supervisory authority without undue delay and, where feasible, within 72 hours, unless the breach is unlikely to result in a risk to the rights and freedoms of individuals. Where a breach is unlikely to result in such a risk, notification to the authority is not required, though you should still document the breach and your reasoning.
A notification does not have to be complete on day one. GDPR allows information to be provided in phases, and if you notify later than 72 hours the notification must be accompanied by the reasons for the delay. At a minimum it should describe the nature of the breach, the categories and approximate numbers of data subjects and records affected, the name and contact of your data protection officer or other contact point, the likely consequences, and the measures taken or proposed to address it.
GDPR is a regulation, so it applies directly with no national transposition. UK GDPR has the same rule. A proposal in the EU Digital Omnibus to change 72 hours to 96 hours is not law. This is informational, not legal advice: verify the specifics that bind you with qualified counsel.
When you must tell the individuals
Notifying the authority is a separate duty from notifying the people affected. Where a breach is likely to result in a high risk to the rights and freedoms of individuals, the controller must communicate it to the affected data subjects without undue delay, in clear and plain language. There are limited exceptions: where the data was protected by measures such as encryption that render it unintelligible to anyone unauthorized, where you have since taken steps ensuring the high risk is no longer likely to materialize, or where individual communication would involve disproportionate effort, in which case a public communication or similar measure can substitute.
Processors, controllers, and vendors
Responsibility for notifying the authority sits with the controller. But a processor (a vendor handling personal data on your behalf) must notify the controller without undue delay after becoming aware of a breach, and GDPR sets no hour count for that step. In practice that means a large share of breaches reach you second-hand, from a supplier, and your 72-hour clock effectively depends on how quickly they tell you. That makes vendor selection, contract terms, and due diligence part of your breach-notification readiness, not a separate exercise. The GDPR solution page covers how classifying vendors by the personal data they hold surfaces exactly which processors sit inside this obligation.
Rarely the only clock
A single incident that exposes personal data at a regulated firm can trigger more than one regime. At a financial entity it can be a GDPR breach and a DORA major incident; at a non-financial essential entity, a GDPR breach and a NIS2 significant incident. The deadlines run in parallel but not from one start: GDPR and NIS2 count from awareness, DORA from classification with a 24-hour backstop from awareness. Our incident clocks guide lays the three regimes side by side, and the coordination that keeps them all on time is the substance of cyber incident management.