Linkage attack: Difference between revisions
tag as incomplete |
mNo edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Delete|No references, AI generated contributions}} | |||
{{Incomplete|Issue 1=No references}} | {{Incomplete|Issue 1=No references}} | ||
Latest revision as of 19:50, 17 August 2025
⚠️ A deletion request has been made for this article
There has been a deletion request for this page for the following reason:
No references, AI generated contributions
This request will be reviewed and acted upon by the wiki moderation team within one week of the template being added.
⚠️ Article status notice: This article has been marked as incomplete
This article needs additional work for its sourcing and verifiability to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues. In particular:
- No references
This notice will be removed once the issue/s highlighted above have been addressed and sufficient documentation has been added to establish the systemic nature of these issues. Once you believe the article is ready to have its notice removed, visit the discord and post to the #appeals
channel.
Learn more ▼
A linkage attack (also known as a record linkage or de-anonymization attack) occurs when anonymized data is combined with one or more external datasets to re-identify individuals. In essence, overlap in quasi-identifying details—like ratings, timestamps, demographic traits, or behavioral patterns—can act like a fingerprint that links a supposedly anonymous record back to a real person.
For example, researchers demonstrated that by matching Netflix’s anonymized movie ratings (ratings, dates, movie IDs) with the same user’s public IMDb ratings, they could re-identify specific users from the Netflix dataset. This minor overlap in non-identifying data enabled them to connect the dots despite the lack of explicit identifiers.