search cancel

Custom ID not triggering on Endpoint Discover scan

book

Article ID: 223627

calendar_today

Updated On:

Products

Data Loss Prevention

Issue/Introduction

When doing an Endpoint Discover scan, some policies will not trigger that contain a custom DI

Cause

A trailing , at the end of the validator in the Custom DI can cause missed detections.

Resolution

Verify the validators in the custom DI do not contain a trailing , at the end. 

For example:

You have a "Exclude beginning character" validator with the text "111,222," or "Exclude prefix" with text "something,something,".  In both of these cases remove the trailing , at the end of the text.  So in this case you would have "111,222" and "something,something".