Question 660
At fictional Beacon Hospitals, a European privacy professional responsible for clinic patient communications is reviewing GDPR territorial scope, accountability and regulatory supervision during a supplier onboarding assessment (CIPPE-IV.B-165). The reported privacy issue is: A controller has written privacy-by-design principles but its testing pipeline accepts unrestricted production personal data by default. Which next privacy compliance action most directly addresses the specific issue?
Explanation
Correct Answer
The most directly responsive compliance action is to build safer testing defaults using minimization, masking and authorized access. In this fictional situation, the concern is: A controller has written privacy-by-design principles but its testing pipeline accepts unrestricted production personal data by default. The expected evidence is: Test environments use necessary limited data with restricted access and retention. The governing rationale is that default privacy protections apply to operational settings as well as policy documents. Relevant facts and local-law conditions should be checked before applying this guidance.
Incorrect Answers
This option focuses on an adjacent privacy obligation rather than the precise legal problem: a controller has written privacy-by-design principles but its testing pipeline accepts unrestricted production personal data by default. Default privacy protections apply to operational settings as well as policy documents.
“Assign remediation, evidence of completion and independent follow-up.” concerns another compliance assessment: an adjacent privacy obligation. It would not by itself resolve the described concern: a controller has written privacy-by-design principles but its testing pipeline accepts unrestricted production personal data by default. Default privacy protections apply to operational settings as well as policy documents.
The compliance measure “Apply ongoing role-appropriate guidance and evidence-based compliance checks.” addresses an adjacent privacy obligation. The specific issue is that a controller has written privacy-by-design principles but its testing pipeline accepts unrestricted production personal data by default; default privacy protections apply to operational settings as well as policy documents.