Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Are Supplier Incident Notification Duties?

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.

Illustration for the cybersecurity term Supplier Incident Notification Duties
Home / Blog / Cybersecurity Terms / What Are Supplier Incident Notification Duties?
17 November 2026

What Are Supplier Incident Notification Duties?

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.

The Statutory Layer

ObligationWho notifies whomDeadline
UK GDPR Article 33(2)Processor to controllerWithout undue delay after becoming aware
UK GDPR Article 33(1)Controller to the ICO72 hours from awareness, where reportable
UK GDPR Article 34Controller to data subjectsWithout undue delay, where high risk to individuals
PECR regulation 5APublic electronic communications service providers to the ICO24 hours
NIS Regulations 2018Operators and relevant digital service providers to the competent authority72 hours from awareness
DORA (EU financial entities)Entity to its competent authorityInitial 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.

What the Contract Must Fix

Six clauses do most of the work:

Where This Falls Apart

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.

Your Duties Downstream

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.

FAQ – Frequently Asked Questions

How Quickly Must a Processor Tell Us About a Breach?

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.

Does Every Supplier Incident Need Reporting to the ICO?

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 Should a Supplier’s First Notification Contain?

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.

Can We Require Suppliers to Notify Us of Incidents That Do Not Involve Our Data?

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.

Related Terms

You May Be Interested In These

What Are WPS Vulnerabilities?

Cybersecurity Terms

17 November 2026

What Are WPS Vulnerabilities?

Read More
What Is a Denial-of-Service Attack?

Cybersecurity Terms

17 November 2026

What Is a Denial-of-Service Attack?

Read More
What Is a Honeypot?

Cybersecurity Terms

5 July 2021

What Is a Honeypot?

Read More