Question 760
At fictional Ironbridge Utilities, a European privacy professional responsible for smart metering programs is reviewing GDPR individual protections, concepts and security duties during a legal risk assessment (CIPPE-II.B-190). The reported privacy issue is: A controller waits until it can confirm every affected account before starting the authority's 72-hour breach clock. Which European data-protection principle best explains the appropriate response?
Explanation
Correct Answer
This is the governing legal or privacy principle for the case: Supervisory notifications are generally without undue delay and where feasible within 72 hours when required. The relevant response is to assess breach awareness, risk and phased notification without waiting for perfect information. The corresponding observation is that the timeline records awareness and any timely Article 33 notification or justified delay. The actual law and jurisdiction remain determinative.
Incorrect Answers
“GDPR Article 32 contemplates technical and organisational measures suited to risk.” is relevant to introduce role-based authorization and periodic access review appropriate to the processing risk, but the question is about this situation: a controller waits until it can confirm every affected account before starting the authority's 72-hour breach clock. Supervisory notifications are generally without undue delay and where feasible within 72 hours when required.
“A personal data breach can involve loss of availability as well as disclosure.” concerns another compliance assessment: assess confidentiality, integrity and availability effects on personal data and service recovery. It would not by itself resolve the described concern: a controller waits until it can confirm every affected account before starting the authority's 72-hour breach clock. Supervisory notifications are generally without undue delay and where feasible within 72 hours when required.
The compliance measure “GDPR Article 33 includes internal documentation of personal data breaches.” addresses document personal data breaches, effects and remedial steps regardless of external notification outcome. The specific issue is that a controller waits until it can confirm every affected account before starting the authority's 72-hour breach clock; supervisory notifications are generally without undue delay and where feasible within 72 hours when required.