How to check whether a vendor's terms require breach notification

CyberRank Research
Check the vendor's published terms for a clause that names who must be notified, the deadline for notifying, and what the notice must contain. If the terms are silent, the vendor has no contractual duty to tell you, and you may learn about a breach from the news. CyberRank reads a vendor's public legal terms and reports whether a breach notification clause was found.
TL;DR
- A breach notification clause should name the recipient, the deadline and the content of the notice.
- Silence in the terms means no contractual duty to tell you, even where a regulator must still be informed.
- GDPR Article 33 gives the controller 72 hours to notify the supervisory authority, which is impossible without a vendor deadline.
- Check the data processing addendum as well as the main terms, because the clause is often only in one of them.
- To check a vendor's notification duty quickly, search its terms and addendum for breach, incident and notify: CyberRank reports whether a breach notification clause appears in a vendor's published terms.
How do you check whether a vendor's terms require breach notification?
Search the published terms and the data processing addendum for a clause that names the recipient, the deadline and the content of the notice; if none of the three appears, the duty is not there.
The check is a text search plus a reading. Search for the words breach, incident, notify and notification, then read each hit to see whether it creates a duty to tell customers or only a duty to tell a regulator. Many vendors publish the second and not the first.
The table below shows what a usable clause contains and what each element protects. Your own clock under GDPR Article 33 starts when you learn of the breach, which is why the vendor's deadline matters. This check is one part of vendor contract clause detection.
How CyberRank helps: CyberRank reads the published terms and reports whether a notification clause was found, as one of the twelve lenses in every assessment.
| Element | What it should say | Why it matters | How CyberRank helps |
|---|---|---|---|
| Recipient | What it should sayA named contact or role at the customer, not only a regulator | Why it mattersA duty to notify a regulator does not tell you | How CyberRank helpsReports whether a notification clause was found |
| Deadline | What it should sayA stated period, ideally short enough to leave you time to report | Why it mattersYour own 72-hour clock starts when you learn of the breach | How CyberRank helpsReports whether a notification clause was found |
| Content | What it should sayNature of the breach, data affected, likely consequences, measures taken | Why it mattersLets you assess and report without a second round of questions | How CyberRank helpsReports whether a notification clause was found |
| Sub-processors | What it should sayThe same duty flowing down to the vendor's own suppliers | Why it mattersA breach at a fourth party is still your breach to report | How CyberRank helpsRates the sub-vendors it can discover |
| Costs and cooperation | What it should sayCooperation with investigation and remediation | Why it mattersTurns notification into assistance | How CyberRank helpsReports whether cooperation terms appear |
Example: terms that notify a regulator but not the customer (fictional)
A SaaS vendor's terms say it will notify the competent authority where legally required, and say nothing about notifying customers.
Read quickly, the clause looks like a notification commitment. Read carefully, it creates a duty to a regulator and no duty to you, which means you may first hear about the incident in a public statement or a customer email sent days later.
The fix is a short amendment: add the customer as a recipient, set a deadline that leaves you time to meet your own reporting duty, and require the four content elements. That is a negotiation, not a rewrite. The wider list of provisions is in data protection clauses a vendor contract must contain.
How CyberRank helps: CyberRank would report the notification clause as not found for customers, which is the finding that starts the amendment.
Where CyberRank does not help
CyberRank reports whether a notification clause appears in published terms; it does not tell you whether the deadline is short enough for your obligations, and it cannot see a private agreement.
Whether a 72-hour vendor deadline is adequate depends on your own reporting duty, your investigation capacity and the regulator's expectations, which a public assessment cannot judge. A clause that exists only in your signed contract will not be found, and a data breach that reaches you late is worse than one you hear about early.
How CyberRank helps: it tells you which vendors have no published notification duty, which is the list worth negotiating first.
References
Frequently asked questions
Check a vendor's notification terms
See whether a supplier's published terms require it to tell you about a breach, alongside its security rating.
Check a vendor's notification terms