Which method BEST reduces the risk related to sharing of personal data between a software as a service (SaaS) customer and the third party storing it?

The correct answer is D. Data anonymization. Anonymization permanently removes or irreversibly destroys all identifiers and quasi-identifiers that could link data back to an individual, such that re-identification is no longer technically feasible. Once data is truly anonymized, it falls outside the scope of most data…

Privacy Architecture

Question

Options

AData hashing
BData encryption
CData pseudonymization
DData anonymization

How the community answered

(66 responses)

A
12% (8)
B
6% (4)
C
3% (2)
D
79% (52)

Explanation

Anonymization permanently removes or irreversibly destroys all identifiers and quasi-identifiers that could link data back to an individual, such that re-identification is no longer technically feasible. Once data is truly anonymized, it falls outside the scope of most data privacy regulations entirely, eliminating the privacy risk associated with sharing it with a third party. Pseudonymization (C) replaces identifiers with tokens but is reversible, so the data remains personal data under regulations like GDPR. Encryption (B) protects data in transit and at rest but is fully reversible by the key holder. Hashing (A) is one-way for arbitrary data but can be reversed for low-entropy values like email addresses or government IDs through brute-force or rainbow table attacks.

Topics

#Data anonymization#Privacy-enhancing technologies (PETs)#Data sharing#Risk reduction

Community Discussion

No community discussion yet for this question.

Full CDPSE Practice