Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Supplier incident notification duties are the contractual and legal obligations that decide how fast a supplier must tell you about a security incident, and what they must tell you.

What Are Supplier Incident Notification Duties?
When a supplier is breached, the clock that matters is usually yours, not theirs. UK GDPR gives a controller 72 hours from becoming aware of a reportable personal data breach to notify the ICO. If the processor holding your data takes five working days to pick up the phone, that window is already gone and the explanation falls to you.
Supplier incident notification duties are the set of obligations, some statutory and some purely contractual, that govern this chain: who must tell whom, how quickly, and with what information.
| Obligation | Who notifies whom | Deadline |
|---|---|---|
| UK GDPR Article 33(2) | Processor to controller | Without undue delay after becoming aware |
| UK GDPR Article 33(1) | Controller to the ICO | 72 hours from awareness, where reportable |
| UK GDPR Article 34 | Controller to data subjects | Without undue delay, where high risk to individuals |
| PECR regulation 5A | Public electronic communications service providers to the ICO | 24 hours |
| NIS Regulations 2018 | Operators and relevant digital service providers to the competent authority | 72 hours from awareness |
| DORA (EU financial entities) | Entity to its competent authority | Initial report within 24 hours of awareness, intermediate within 72 hours, final within one month |
Note the asymmetry in the first two rows. The processor’s duty is “without undue delay”, an elastic phrase, while the controller’s is a hard 72 hours. That gap is exactly what a contract has to close.
Six clauses do most of the work:
Three failure patterns recur. The first is discovery by headline: the supplier tells the press, or a security researcher does, before telling customers, which the 2023 managed file transfer compromises illustrated repeatedly. The second is notification to the wrong person, typically an account manager who forwards it days later, which is why contracts should name a security contact and require notification to a monitored mailbox rather than to an individual. The third is a supplier who notifies promptly but will share nothing further, leaving you unable to tell the ICO whether personal data was accessed.
Test the chain before you need it. Including a supplier in a tabletop exercise, or simply asking a critical supplier to describe what they would do in the first four hours, surfaces these problems while they are still cheap.
The obligations run in both directions. If you are the supplier, you hold the processor duty, and your customers’ regulatory deadlines depend on your speed. Build the notification step into the incident response plan itself, with the contact list, the contractual deadline per customer, and a prepared template, rather than treating it as something the account team handles after the technical work is done. Legal review of a first notification is sensible; waiting for certainty before sending anything is not, since initial notifications are expected to be incomplete and may be supplemented later.
Financial entities should note that DORA also requires contractual provisions on incident reporting for ICT third-party arrangements, and UK firms face similar expectations through PRA Supervisory Statement SS2/21 and FCA notification rules. Those obligations rest with the regulated firm regardless of which party discovered the incident.
If you want these timelines rehearsed with your critical suppliers in the room, our cyber exercise services run scenarios that include the third parties your response depends on.
UK GDPR Article 33(2) says without undue delay after becoming aware, with no fixed number of hours. Because the controller has only 72 hours to report to the ICO, contracts should specify a concrete deadline, commonly 24 hours or less. Without that figure, you are relying on the supplier’s interpretation of an elastic phrase during the worst week of their year.
No. The duty applies to personal data breaches likely to result in a risk to the rights and freedoms of individuals. An incident at a supplier who holds none of your personal data does not trigger it, though it may still require action under your contract and continuity plans. Where you cannot yet tell, record the assessment and reasoning, since the ICO expects documented decisions either way.
What is known so far, when the supplier became aware, which of your data or systems may be affected, the containment steps already taken, and a named contact leading their response. Regulators accept that early notifications are incomplete, so the priority is speed and a commitment to update. Contracts should specify this content so the first message is useful rather than reassuring.
Yes, and for critical suppliers it is worth doing. A ransomware event elsewhere in their estate may affect service availability or indicate a wider compromise that later reaches your data. Define the trigger carefully so the obligation is workable: typically any incident materially affecting the services provided to you, or any compromise of systems connected to those services.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.