Importing Regular Expressions via a TSV File
In this section, we will guide you through the process of importing regular expressions using a TSV (Tab-Separated Values) file and integrating them into the PDLP. We'll cover the basics of preparing your TSV file for regular expressions and the steps to import them effectively into the PDLP.
Structure of the TSV File
Only UTF-8 file encoding is supported.
Each regular expression should be represented on a single line. The format of each line could be:
<NAME> <TAB> <RegEX>
<RegEX>
NAME: Should not exceed 64 characters and may contain alphanumeric characters and underscores ([a-zA-Z0-9_]).
- If the NAME is not provided, a default will be generated in the format: CUSTOM_FILE_REGEX_<line number>.
SEPARATOR: A TAB character will be used
REGULAR EXPRESSION: Everything following the TAB character is treated as the regular expression. If the NAME and TAB are not present, the entire line will be considered as the regular expression.
Enabling Importing Regular Expression
Policies > Workflow rules > "Workflow name" > Proactive DLP > Check for regular expressions > Load regular expressions from file

Let's discuss each section and provide an example:
- Regular expression file: Path to TSV formatted regular expression file
- After updating the file, either by a new file or editing the existing one, the PDLP engine should be restarted. This can be done by disabling and then enabling the engine under Inventory > Modules > Proactive DLP.
- In the event of an error, non-compliance with the specified format, or incorrect regex, we will ignore the problematic line and record the error in the engine logs. If the provided regex does not function as expected, please consult the logs to determine if there are any errors in the file you provided.
Below is an example of a regular expressions file you can use