I. Overview

%%{init: { 'theme': 'base', 'themeVariables': { 'edgeLabelBackground': '#fff' }}}%%
flowchart LR
    A["Identifiable\ninformation"] -- "applying the 5 core\npseudonymization techniques" --> B["Pseudonymized\n(de-identified) data"]
    style A fill:#f9f9f9,stroke:#333,stroke-width:3px
    style B fill:#e1f5fe,stroke:#01579b,stroke-width:3px

Definition: Pseudonymization techniques are technical methods that delete or substitute part of personal information so that a specific individual cannot be identified without additional information.

Core value and purpose:
( Data Utility ) Preserves the data’s statistical properties and quality ( Utility ) so it still fits the intended analysis purpose.
( Privacy Protection ) Minimizes re-identification risk to safeguard data subjects’ privacy rights.
( Risk Management ) Secures legal compliance through technical measures and cuts off the risk of a security incident (re-identification) at the source.

II. Mechanism & Components

The 5 Core Pseudonymization Techniques and Their Sub-Methods

flowchart LR
    A["Original\npersonal information"] --> T1["1. Deletion"]
    A --> T2["2. Rounding"]
    A --> T3["3. Masking"]
    A --> T4["4. Substitution"]
    A --> T5["5. Aggregation"]

    T1 --> B["Pseudonymized data\nbalancing Utility\nand Privacy"]
    T2 --> B
    T3 --> B
    T4 --> B
    T5 --> B
Pseudonymization TechniqueDetailed DescriptionConcrete Example
1. DeletionDirectly deletes fields containing identifiers, or removes specific itemsFully deleting name, resident registration number, phone number
2. RoundingConverts numerical data into a range (bucket) or rounds itAge 26 → “20s”; salary 3.54 million won → “3-4 million won”
3. MaskingReplaces part of the data with a special character such as an asterisk (*) to prevent identificationHong Gil-dong → Hong *dong; Gangnam-gu, Seoul → **-gu, Seoul
4. SubstitutionReplaces an identifier with an arbitrary unique or virtual numberResident registration number → replaced with a serial number (A-001)
5. AggregationProcesses data as a group total or average rather than individual recordsIndividual income → converted to average income by department

III. Comparison & Application

Pseudonymization techniques are more often mixed according to the characteristics of the data than used alone, and the resulting dataset is typically validated against one of the following privacy-protection models.

ModelCore ConceptBest FitWeakness
k-AnonymityAt least k records share the same attributesBaseline defense against linking attacksVulnerable to homogeneity attacks within a k-group
l-DiversityAt least l distinct sensitive values per k-groupDatasets where the sensitive value needs variation within each groupCan noticeably reduce data utility
t-ClosenessA group’s sensitive-value distribution stays close to the overall distributionHighest-assurance releases against skewness and similarity attacksComplex and costly to implement correctly

Don’t pick a model based on which one is easiest to implement — pick it based on which attack the dataset is actually exposed to. A dataset with a skewed sensitive attribute, such as a rare condition concentrated in one subgroup, needs t-closeness or it isn’t meaningfully protected even after it passes k-anonymity and l-diversity checks; teams that stop at k-anonymity because it’s simplest are often defending against the attack that was already the least likely one.

Last updated 18 Aug 2026, 00:00 UTC. history