Question 900
At fictional Northgate Publishers, a European privacy professional responsible for online reader subscriptions is reviewing GDPR individual protections, concepts and security duties during a supplier onboarding assessment (CIPPE-II.A-225). The reported privacy issue is: A European SaaS firm considers a corporate entity itself to be a GDPR data subject for ordinary business records. Which ongoing control most directly reduces the risk of repeating this issue?
Explanation
Correct Answer
This recurring safeguard is to distinguish entity-level and individual-level fields in supplier databases. It directly addresses the risk that a European SaaS firm considers a corporate entity itself to be a GDPR data subject for ordinary business records. The associated corrective decision is to identify whether information relates to natural persons rather than only a legal person; success is shown when the records map corporate contact entries to identifiable employees where applicable.
Incorrect Answers
“Verify anonymization claims through documented identifiability assessment.” is relevant to keep pseudonymized activity inside applicable safeguards where reasonable identification remains possible, but the question is about this situation: a European SaaS firm considers a corporate entity itself to be a GDPR data subject for ordinary business records. This recurring safeguard is to distinguish entity-level and individual-level fields in supplier databases.
This option focuses on classify tokenised records as potentially pseudonymous when a key permits reidentification rather than the precise legal problem: a European SaaS firm considers a corporate entity itself to be a GDPR data subject for ordinary business records. This recurring safeguard is to distinguish entity-level and individual-level fields in supplier databases.
“Review identifiers and reasonably available linkage in data-mapping exercises.” concerns another compliance assessment: evaluate whether the identifier can single out an identifiable natural person. It would not by itself resolve the described concern: a European SaaS firm considers a corporate entity itself to be a GDPR data subject for ordinary business records. This recurring safeguard is to distinguish entity-level and individual-level fields in supplier databases.