Adding Whitelisted.txt to exception to the IDM policy.

Products

• Data Loss Prevention Enforce

Issue/Introduction

Adding Whitelisted.txt to exception to the IDM policy.

Cause

While adding the profile in the policy we get the option to select Exact Match with the % (percentage), we should increase the percentage from 10 to 20 or 30 then only the Whitelisted contents will be ignored from the policy and the incident will not get generated.

Resolution

Steps to proceed with the Whitelisted.txt file for IDM profile.

 

Often sensitive documents contain standard boilerplate text that does not requires protection. In this case you can configure the system to exclude ("whitelist") this text. The Enforce Server does not index whitelisted text and thus excludes it from detection.

To exclude document content from detection, create a Whitelisted.txt file for each Document Profile you want to index. When you index the document source, the Enforce Server looks for the Whitelisted.txt file. If such a file exists, the Enforce Server copies it to Whitelisted.x.txt, where x is a unique Document Profile identification number.

Copy all the content you want to whitelist into a text file and save the file as Whitelisted.txt.

Save the file to the appropriate directory:

On Windows, save it to C:\ProgramData\Symantec\DataLossPrevention\ServerPlatformCommon\<version>\documentprofiles\whitelisted

On Linux, save it to /var/Vontu/documentprofiles/whitelisted.

By default, a file you index must contain at least 130 characters. This default setting applies to the Whitelisted.txt file as well. For whitelisted text you can change this default setting.

Save the file.

Further, While adding the profile in the policy make sure that we have selected the % (percentage) at least 20 or more. (If we select 10 then the whitelisted content will still detect and the incident will get generated).