<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Additional Information on</title><link>https://docs.protegrity.com/anonymization/1.3.0/docs/additional_info/</link><description>Recent content in Additional Information on</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 01 Apr 2026 02:33:24 +0000</lastBuildDate><atom:link href="https://docs.protegrity.com/anonymization/1.3.0/docs/additional_info/index.xml" rel="self" type="application/rss+xml"/><item><title>Best practices when using Protegrity Anonymization</title><link>https://docs.protegrity.com/anonymization/1.3.0/docs/additional_info/hide_appex_bestpract/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/anonymization/1.3.0/docs/additional_info/hide_appex_bestpract/</guid><description>&lt;ul>
&lt;li>
&lt;p>Ensure that the source file is &lt;strong>clean&lt;/strong> based on the following checks:&lt;/p>
&lt;ul>
&lt;li>A column contains correct data values. For example, a field with numbers, such as, salary, must not contain text values.&lt;/li>
&lt;li>Appropriate text as per the coding selected is present in the files. Special characters or characters that cannot be processed must not be present in the source file.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>Move the anonymized data file and the logs generated to a different system before deleting your environment.&lt;/p></description></item><item><title>Protegrity Anonymization Risk Metrics</title><link>https://docs.protegrity.com/anonymization/1.3.0/docs/additional_info/hide_risk_calculations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/anonymization/1.3.0/docs/additional_info/hide_risk_calculations/</guid><description>&lt;h2 id="definitions">Definitions&lt;/h2>
&lt;p>The following definitions are used for risk calculations:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Data Provider or Custodian&lt;/strong>: The custodian of the data, responsible for controlling the process of sharing by anonymizing the data as well as putting in place other controls which prevents data from being misused and or re-identified.&lt;/li>
&lt;li>&lt;strong>Data Recipient&lt;/strong>: Person or institution who receives the data from the data provider.&lt;/li>
&lt;li>&lt;strong>Dataset&lt;/strong>: The collection of all records containing the data on subjects.&lt;/li>
&lt;li>&lt;strong>Adversary&lt;/strong>: Data recipient who has the motives to attempt and means to succeed the re-identification of the data and intends to use the data in ways which may be harmful to individuals contained in the dataset.&lt;/li>
&lt;li>&lt;strong>Target&lt;/strong>: Person whose details are in the dataset who has been selected by the adversary to focus the re-identification attempt on.&lt;/li>
&lt;/ul>
&lt;h2 id="types-of-risks">Types of risks&lt;/h2>
&lt;p>Protegrity Anonymizationuses the Prosecutor, Journalist and Marketer risk models to access probability of re-identification attacks. A description of these risks are provided here.&lt;/p></description></item></channel></rss>