Hub
  • Software
  • Blog
  • Forum
  • Events
  • Documentation
  • About KNIME
  • KNIME Hub
  • Nodes
  • Anonymity Assessment
NodeNode / Manipulator

Anonymity Assessment

Community Nodes Privacy
Drag & drop
Like
Copy short link

The anonymity assessment node considers two types of risks, quasi-identifiable re-identification and attacker risks. The output is an analysis of these two risks. To get additional insight if two tables are provided an additional columns with the same risks assessment results are provided in the output tables. This is helpful for comparing non-anonymized and anonymized data.

  1. Quasi-identifiable re-identification risks
    Combinations of quasi-identifiers that can be analyzed regarding associated risks of re-identification. The output table provides information about the degree to which combinations of variables separate the records from each other and to which degree the variables make records distinct. Risk Analysis
  2. Attacker risks
    There are different types of attackers that are assessed. The output table is an estimation of three different attacker models:

    a) [prosecutor scenario] The risk that a specific person in the dataset can be re-identified when the attacker knows this person is in the dataset.

    b) [journalist scenario] The risk that there exists at least one person in the dataset who can be re-identified. The point is to prove that someone can be re-identified. In this case, the goal of the re-identification is frequently to embarrass or discredit the organization that performed the de-identification.

    c) [marketer scenario] The percentage of identities in the dataset that can be correctly re-identified.

    Mode Details
If two tables are provided then, additional columns are shown in the output tables.

Node details

Input ports
  1. Type: Table
    Non-anonymized table
    Non-anonymized table
  2. Type: Table
    Anonymized table
    Anonymized table
Output ports
  1. Type: Table
    Quasi-identifiers re-identification risks
    Quasi-identifiers re-identification risks
  2. Type: Table
    Attacker models re-identification risks
    Attacker models re-identification risks

Extension

The Anonymity Assessment node is part of this extension:

  1. Go to item

Related workflows & nodes

  1. Go to item
    Just Knime It-CH9
    anilks > Just Knime It Challenges > Just Knime It Challenge > Just Knime It-009
  2. Go to item
    JustKNIMEit_Challenge9_Anonymization_JeromeTreboux
    Justknimeit-9 Challenge9 Anonymization
    Just KNIME it! Challenge 9 - Anonymization - Jérôme Treboux You would like to post a ques…
    trj > Public > Just KNIME it! Challenge > JustKNIMEit_Challenge9_Anonymization_JeromeTreboux
  3. Go to item
    Redfield_Privacy_extension_example
    Privacy Anonymization Redfield
    +1
    The workflow gives an example of how the Privacy extension nodes are used for data anonym…
    redfield > Public > Redfield_Privacy_extension_example
  4. Go to item
    Redfield_Privacy_extension_example
    Privacy Anonymization Redfield
    +1
    The workflow gives an example of how the Privacy extension nodes are used for data anonym…
    jwienstroeer > Public > Redfield_Privacy_extension_example
  5. Go to item
    Anonymization workshop by Redfield
    redfield > Public > Anonymization workshop by Redfield
  6. Go to item
    02.1_Data_Anonymization
    Best practices Data engineer Data engineering
    +1
    The company has two branches: one in the United States and another one in Europe. New US …
    knime > Education > Courses > L4-DE Best Practices for Data Engineering > solutions > Session_2_ETL_Processing_II > 02.1_Data_Anonymization
  7. Go to item
    02.2 Database update
    Best practices Data engineer Data engineering
    +1
    The company has two branches: one in the United States and another one in Europe. New US …
    knime > Education > Courses > L4-DE Best Practices for Data Engineering > exercises > Session_2_ETL_Processing_II > 02.2_Database_update
  8. Go to item
    02.2 Database update
    Best practices Data engineer Data engineering
    +1
    The company has two branches: one in the United States and another one in Europe. New US …
    knime > Education > Courses > L4-DE Best Practices for Data Engineering > solutions > Session_2_ETL_Processing_II > 02.2_Database_update
  9. Go to item
    04.1_ETL_Customers
    Best practices Data engineer Data engineering
    +1
    The company has two branches: one in the United States and another one in Europe. New US …
    knime > Education > Courses > L4-DE Best Practices for Data Engineering > exercises > Session_4_Orchestration > 04.1_ETL_Customers
  10. Go to item
    04.1_ETL_Customers
    Best practices Data engineer Data engineering
    +1
    The company has two branches: one in the United States and another one in Europe. New US …
    knime > Education > Courses > L4-DE Best Practices for Data Engineering > solutions > Session_4_Orchestration > 04.1_ETL_Customers

No known nodes available

KNIME
Open for Innovation

KNIME AG
Hardturmstrasse 66
8005 Zurich, Switzerland
  • Software
  • Getting started
  • Documentation
  • E-Learning course
  • Solutions
  • KNIME Hub
  • KNIME Forum
  • Blog
  • Events
  • Partner
  • Developers
  • KNIME Home
  • KNIME Open Source Story
  • Careers
  • Contact us
Download KNIME Analytics Platform Read more on KNIME Server
© 2022 KNIME AG. All rights reserved.
  • Trademarks
  • Imprint
  • Privacy
  • Terms & Conditions
  • Credits