Skip to content

Right to Privacy

Prerequisites

  1. Ensure all prerequisites outlined in the prerequisites are completed.
  2. Before configuring the Right to Privacy (RTP) policy under a Data Zone, ensure you have followed the steps outlined here to create and manage a Data Zone.

Table of Contents

Section Description
Introduction Overview of RTP and its significance
Supported Connectors List of supported connectors for RTP
Supported File Formats File formats supported by RTP
Steps for Configuration Step-by-step guide to configuring RTP
Right to Privacy Policy Fields Key fields used in the RTP policy
Validation of Right to Privacy Policy How RTP policies are validated

Introduction

The Right to Privacy (RTP) Policy, also known as the Right to Be Forgotten, is designed to help organizations comply with data protection regulations such as GDPR (General Data Protection Regulation). This policy enforces static data masking techniques to safeguard sensitive information, including Email, US-Phone, and US-Address, by replacing original values with masked values using literal or scheme-based mapping.

By referencing a lookup file, the RTP policy ensures that sensitive data is anonymized or replaced, allowing organizations to comply with user rights under GDPR and similar regulations. It is particularly valuable for ensuring that users’ personal data is protected or erased upon request in accordance with legal mandates.

The policy supports JDBC and FileSystem connectors, making it applicable across structured and unstructured data sources in an organization’s ecosystem.

Process Flow

The following steps must be performed to ensure the RTP Policy operates as expected:

  1. Source Data Scanning:

    • The source data must be scanned first.

    • During scanning, Discovery classifies the data and assigns Tags to relevant fields.

  2. Record Matching with Lookup File:

    • Each record in the source data is evaluated based on its tagged fields.

    • Tagged fields in the source data are compared with the corresponding fields in the lookup file.

    • If a tagged field’s value in the current record matches a value in the lookup file, that record is considered for further action.

  3. Matching Conditions:

    • If multiple tagged fields exist in a record, all of them must match corresponding values in the lookup file for the record to be considered for encryption.

    • This follows an AND condition, meaning every specified tag must match for a record to qualify for encryption.

  4. Lookup File Format & Field Matching:

    • The lookup file must be in CSV format.

    • The column headers in the lookup file are matched with the Tag names to identify the relevant fields for comparison.

    • Extra fields in the lookup file are ignored unless their column headers match a Tag name.

Key Considerations

  1. Scanning is mandatory before applying the RTP Policy.

  2. Only tagged fields are used for matching; other fields in the lookup file are ignored.

  3. If more than one tag is specified in the “Search for Tags” field, all matching tagged fields in the record must match (AND condition) for the record to be considered for policy enforcement.

Example

You can apply this policy to JDBC and FileSystem connectors. For example, when using AWS S3 as a FileSystem, if you have a resource like source_data_file.csv stored in an AWS S3 location and need to encrypt sensitive information using the RTP policy, follow these steps:

source_data_file.csv

Download source_data_file.csv or create with below sample data.

Text Only
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
ID,Person Name,Email,SSN,US_Phone,Address,Account ID,ZipCode
1,Nancy,nancy@yahoo.com,201-99-5532,856-232-9702,939 Park Avenue,159635478,33317
2,Gene,gene@google.us,202-99-5532,954-583-0575,303 Johnston Blvd,236854569,95202
3,Edward,edward@facebook.com,203-99-5532,209-626-9041,130 Hollister,365412985,60173
4,Pearlene,pearlene@gmail.com,204-99-5532,708-471-6810,17 Warren Rd,452189732,90017
5,James,james@cuvox.de,205-99-5532,661-338-6787,898 Newport Gray Rd,517836427,94041
6,Pamela,pamela@cuvox.de,206-99-5532,650-526-5259,861 Strick Rd,685231473,80214
7,Donna,donna@fleckens.hu,207-99-5532,303-239-4282,1784 S Shore Dr,789563258,1730
8,Amy,amy@gustr.com,208-99-5532,774-553-4736,9522 Apple Valley Dr,854126945,55102
9,Adam,adam@teleworm.us,209-99-5532,651-297-1448,745 Old Springville Rd,965412381,43201
10,Lucille,lucille@armyspy.com,210-99-5532,740-320-1270,4223  Midway Road,785651236,89102
11,Edard,edu@gustr.com,211-99-5532,702-257-8796,3659  Dye Street,965121354,53207
12,Nick,nick@jourrapide.com,212-99-5532,414-483-8638,2966  Nutters Barn Lane,563515264,72764
13,Brian,brian@einrot.com,213-99-5532,479-872-9783,3300  Worthington Drive,654621233,91303
14,Stella,stella@jourrapide.com,214-99-5532,818-596-6681,1893  Ingram Road,261613654,35816
15,Leona,leona@dayrep.com,215-99-5532,256-250-5413,4244  Burnside Court,986513211,75069

lookup.csv

Download lookup.csv or create with below sample data.

Text Only
1
2
3
4
5
EMAIL,SSN
nancy@yahoo.com,201-99-5532
gene@google.us,202-99-5532
edward@facebook.com,203-99-5532
pearlene@gmail.com,204-99-5532

  1. Scan the source_data_file.csv file in the AWS S3 location using the outlined scanning steps, either through offline or real-time scanning.
  2. Create a lookup file lookup.csv in .csv format under the AWS S3 location, ensuring that EMAIL and SSN is a column header.
  3. Configure a Data Zone and an RTP policy by following the provided steps.
  4. Add the source_data_file.csv resource to the Data Zone, specifying the AWS S3 location, and initiate re-evaluation.
  5. After approximately 60 seconds, verify that the sensitive data in source_data_file.csv has been encrypted.

Note

  1. The column headers in the lookup file must match those in the scanned resource and align with the tags defined in the RTP policy.
  2. The resource must be scanned before applying the RTP policy.
  3. RTP policy are not applied during real-time or offline scans; they are enforced only when the Re-evaluate option is selected for the Data Zone resource.

Supported Connectors

For a list of supported connectors, refer to Supported Connectors for Discovery Compliance Policies.

Supported File Formats

For a list of file formats supported by the Right to Privacy policy, see Supported File Formats.

Steps for Configuration

To configure the RTP policy, follow the steps outlined in Steps for Configuration.

Right to Privacy Policy Fields

Field Name Description
Name Specifies the name of the RTP policy.
Type Defines the policy type. For RTP, select Right to Privacy.
Alert Level Select the severity level of the alert High, Medium, or Low created after the policy is applied on resource.
Description (Optional) Provides details about the RTP policy and its purpose.
Status Enables or disables the RTP policy (enabled by default).
Application Select the connector where the RTP policy will be enforced. For the above example, source_data_file.csv is an AWS S3 file, so select AWS S3.
Lookup Application Select the appropriate filesystem connector where lookup file is stored. For the above example, lookup.csv is an AWS S3 file, so select AWS S3.
Lookup File Location Provide the path to the lookup.csv file. The lookup file must be in .csv format, with header column names matching with the tag names.
Archive Location (Optional) Specify the archive location. For file systems, an archive folder is created automatically. For JDBC connectors, an existing database or schema must be provided.
Search for Tags Specifies one or more tags used to identify and encrypt sensitive data. In the above example, the tag EMAIL and SSN should be mentioned here. If multiple Tags are specified, then they all are matched(AND condition) with the corresponding source data record.
Apply Encryption Schemes Choose the required tag and corresponding encryption schemes from the list. You can view scheme mapping here.
Auto Run (Optional) This feature is now deprecated and will be removed from the UI in future updates. Users are advised to updated policies as applicable.

Note

  1. For connectors like Snowflake and Databricks Unity Catalog, use the [Db].[Schema].[Table] and [Catalog].[Schema].[Table] structures, respectively. When specifying the archive location for these connectors, ensure the format is [Db].[Schema] or [Catalog].[Schema], as applicable.
  2. Verify that the [Db].[Schema] or [Catalog].[Schema] exists prior to executing the RTP policy for JDBC connectors.
  3. The lookup file must be stored on a file storage system. While the policy can be applied to other types of connectors, the lookup file will always be saved on the file storage system.

Validation of Right to Privacy Policy

After executing a Re-evaluate on the Data Zone, use the following steps to validate the RTP policy:

  1. Ensure that sensitive data in the scanned resource is encrypted according to tag matching from the lookup file, as defined in the policy configuration.
  2. If an archive location is specified, the original copy of the source resource is stored there.
  3. The classification appears in the Data Inventory > Classifications section.
  4. Policy alerts appear on the Compliance > Alerts Dashboard and on the Data Inventory > Classifications > Resource Detail > ALERTS DETAILS tab.

Important

• When the RTP policy is executed multiple times on the same dataset with the same configuration, encryption is applied based on tag matching from the lookup file.

• For each match found, the policy encrypts the identified data and saves a copy of the original file in the archive location.

• Repeated execution of the policy with identical settings will overwrite previously archived files with newly processed versions.

• As a result, only the most recent original file copies are retained in the archive, ensuring that the latest encryption is consistently applied to the matching data.

Comments