Data Redaction Security Guide

Welcome to the OneTrust Data Redaction overview and security document. Data Redaction is available as a purchased add-on for the Privacy Rights Automation module. 

OneTrust Data Redaction is a powerful feature set that allows privacy and IT teams tasked with privacy request fulfillment to use the power of Azure natural language processing (NLP) models to redact third-party and sensitive information from data sets prepared for access requests. Data Redaction not only helps reduce the manual overhead of data redaction and aggregation involved in privacy request fulfillment but also the risk of inadvertently causing a data breach. 

As part of Privacy Rights Automation, the Data Redaction add-on includes enhanced security measures, as well as encryption of personal data in transit and at rest. Access to any such personal data is strictly controlled using roles-based access and organizational hierarchy inside the OneTrust application.

Each piece of PII used for Data Redaction is encrypted at rest and in transit. An independent encryption service is called every time data is retrieved or stored in the database.

An environment-specific Primary Key and a tenant-specific Operational Key are both required to properly decrypt data maintained in the OneTrust database. Operational keys are encrypted via the environment's primary encryption key using AES 256. The primary encryption key is stored in a Java key store.

The OneTrust application and Privacy Portal uses TLS 1.2 for encrypting data in transit and a web application firewall to prevent malicious access and provide secure transport between the application and your browser. All data transported between the OneTrust application and your browser session are encrypted and rendered un-usable to an unauthorized user. Any links provided in results which may be concealed as phishing attempts are removed and replaced with ‘dummy’ links so a user does not open and become exposed to malicious consent.

Data subjects can only log in to the Privacy Portal by using the email address submitted with the web form. Email addresses can be independently verified by your privacy team before any access to the Privacy Portal is given.

Data subjects access the Privacy Portal using a secure link sent via email that is provided whenever a member of your organization posts a public reply to the request. The link is not provided in the initial request submission confirmation email. This link can be clicked up to 10 times for re-entry.

Before entering the Privacy Portal, data subjects will be prompted to request a one-time access code that will be sent to their verified email. They will also need to complete the Captcha validation.

Data subjects can select the Remember this device setting to remain signed into the Privacy Portal for specific number of days, which is configured in the Privacy Rights Automation Global Settings menu. Data subjects can remain in the Privacy Portal as long as they remain active. Once data subjects exit the Privacy Portal, they will need to enter their email again to request a new one-time access code to enter the Privacy Portal.