What evidence do auditors commonly ask for on Art.33 Notification of a personal data breach to the supervisory authority?

The internal breach register covering all breaches including those assessed as not notifiable, with the risk assessment recorded for each; The awareness timestamp per incident and the basis for it, since the 72 hours runs from awareness and not from confirmation or containment; Notifications as submitted, checked against the four content elements Article 33(3) requires; The methodology used to decide notifiability, and evidence it was applied rather than the decision reached first and documented after; Processor contract terms requiring notification without undue delay, and the notification times actually achieved.

What is the most common gap auditors find on Art.33?

The awareness clock started at the end of the investigation rather than at the point of reasonable certainty that a breach had occurred

GDPR · Chapter IV - Controller and Processor

`Art.33` Notification of a personal data breach to the supervisory authority

On becoming aware of a personal data breach, notify it to the competent supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons; a notification made later than 72 hours must be accompanied by the reasons for the delay. A processor must notify its controller without undue delay after becoming aware of a breach. The notification must at least describe the nature of the breach including, where possible, the categories and approximate number of data subjects and of personal data records concerned, give the name and contact details of the data protection officer or other contact point, describe the likely consequences, and describe the measures taken or proposed including any measures to mitigate adverse effects. Information may be provided in phases where it cannot all be given at once. Document every personal data breach, including the facts, its effects and the remedial action taken, so the supervisory authority can verify compliance with this Article.

Source: GDPR, Art.33. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open GDPR in the compliance library.

Many articles apply only where their condition is met (a data protection officer under Article 37, an impact assessment under Article 35, a representative under Article 27); the condition is in each statement.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

The internal breach register covering all breaches including those assessed as not notifiable, with the risk assessment recorded for each · Policy repository / GRC workspace
The awareness timestamp per incident and the basis for it, since the 72 hours runs from awareness and not from confirmation or containment · HR system / LMS
Notifications as submitted, checked against the four content elements Article 33(3) requires · Document repository
The methodology used to decide notifiability, and evidence it was applied rather than the decision reached first and documented after · Document repository
Processor contract terms requiring notification without undue delay, and the notification times actually achieved · Vendor register / contract repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

The awareness clock started at the end of the investigation rather than at the point of reasonable certainty that a breach had occurred
Breaches judged not notifiable with no documented assessment, leaving nothing for the authority to verify under Article 33(5)
The register recording only breaches that were notified, so the unlikely to result in a risk decisions are invisible
Processor notification terms that say promptly or within a commercially reasonable time, which cannot support the controller's 72 hours

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

Art.32 Security of processing · Art.34 Communication of a personal data breach to the data subject