PII Masking and Data Protection
Updated
Personally Identifiable Information (PII) Masking in Sprinklr refers to the process of identifying and securing sensitive personal information with the platform to ensure compliance with data privacy regulations (like GDPR, CCPA) and protect user data from unauthorized access.
It involves hiding or obfuscating personal data such as names, email addresses, phone numbers, credit card details, or any information that can identify an individual. It helps to safeguard user privacy, and reduce the risk of data breaches or misuse.
Also, Whenever PII is masked, a marker is displayed on the recording timeline at the corresponding message timestamp in the case analytics view.
Enablement Note: To learn more about getting this capability enabled in your environment, please work with your Success Manager.
Permissions
To use this functionality, you need to have the ability to view, create, edit, and delete under Masking Configuration. You may efficiently develop, manage, and mask templates in accordance with the requirements thanks to these permissions.
The following table describes the definitions of the permissions listed.
Permissions | Definition |
View | The View permission determines whether a user or role can access and view unmasked sensitive data classified as PII. The View permission is a user or role-based control. |
Create | The Create permission determines whether a user or role has the ability to define, configure, or apply new masking rules and policies for PII data within a system. This permission is critical for ensuring that masking is implemented securely and consistently across sensitive data. |
Edit | The Edit permission allows users or roles to modify existing masking rules, policies, or configurations related to protecting PII data. The permission ensures that only authorized personnel can update how sensitive data is masked, balancing flexibility with security. |
Delete | This permission allows authorized users or roles to remove existing masking rules, policies, or configurations. This permission is critical and must be tightly controlled, as deleting masking rules can expose sensitive PII data, and impact with compliance with data privacy regulations. |
Creating Masking Template
This section gives you an overview on creating a Masking Template using the following two screens:
Overview
Masking Details
Entering Overview Details
On the Launchpad, click on All Settings under the Settings option on the Platform Modules section.
2. On the Platform Settings screen, click Manage Customer from the left panel and then click Masking.
3. The Masking Templates screen lists the templates shared with the user. Based on the granted permission, you can Create, Edit or Delete a template by clicking on the three dots next to the template.
4. Click on + Add masking Template. The Create Masking Template screen is displayed.
5. Enter the Name of the Masking Template.
6. Enter a brief description of the Masking Template in the Description box.
7. Toggle the Enable for voice Channels to enable the masking for voice interactions. This toggle remains disabled if the masking is enabled for digital messages.
8. In the Message Conditions section, you can define various conditions based on which messages are filtered that require masking.
Where: Depending upon whether the Enable for voice Channels toggle is enabled or disabled, various options will get populated in the Accounts drop-down. Select Attributes, Operator, and Values. If enabled, voice accounts will get populated, else digital social accounts will apear in the dropdown.
Note: t is mandatory to select atleast one Account from the Select Values drop-down list.
+ Add Condition: Clicking on this will populate another row of filters next to AND to Select Attribute, Operator and Values. You can select one of the following attributes from the Select Attribute dropdown:
Message Type: Defines the type of messages you want to mask.
Channels: Masks messages from a specific channel.
In Fan Post: Marking it True will mask the Fan messages. Marking it False will mask the Brand messages instead.
9. Using User/User Groups drop-down, you can select the user or user groups with whom you want to share the masking details.
Entering Masking Details
Perform the following steps to select the preferred type of masking and the various approaches.
Under the Approach section, enable the AI Based toggle to involve the use of artificial intelligence to automatically identify and obscure sensitive information within user-generated content, or enable the Regex Based toggle to identify and obscure sensitive information by matching specific patterns in text.
Select a condition from the Mask after time dropdown that determines when to perform masking.
Select a masking character from the Masking Character dropdown.
Select the Type of Masking, Permanent or Conditional.
Under Additional Settings, enable the Mask Audio toggle to mask the audio along with its transcript.
The following table provides information on the parameter names and their description available on the Masking Details screen:
Parameter Name | Description |
Approach |
|
Mask after time | Select the condition that determines the time to perform masking. From the dropdown, you can select one of the following:
|
Masking Character |
|
Type | There are two types of Masking that are supported in Sprinklr:
|
Additional Settings | Mask Audio: Parts of an audio recording containing sensitive information (For example, names, phone numbers, credit card details) are automatically detected and masked with beep sounds, during or after the conversation, if the Mask Audio toggle is enabled. Additionally, visual markers appear on the recording timeline to highlight these masked segments, aligning with the PII-masked segments message in the Case Analytics view.
Access to Masking Audio for certain segment is controlled by the dynamic property. To enable this feature in your environment, contact your Success Manager. Alternatively, you can submit a request at tickets@sprinklr.com. |
Performing PII Unmasking
Perform the following steps to unmask PII:
Create a rule. Under Change Properties of Message, select the Search Pattern and Take Action and set the value to Yes.
In the associated Text field, input the specific regex pattern representing sensitive information that you wish to unmask in digital and voice conversations.
Once you've defined the pattern, click Add Action. From the list of actions, choose Unmask PII entities. This action will identify any masked sensitive information matching the specified pattern and unmask it accordingly.
Click Save.