Corrupt Validators listed in Data Identifiers causing irregular detection for customers with Cloud Detection Services

Products

• Data Loss Prevention Enforce

Issue/Introduction

Detection stops working reliably for customers with Cloud Detectors, either Email or REST.

And although there are no policies using it, if the Data Identifier Validator for the "Ukraine Identity Card Check" is examined, it will appear to have corrupt fields as per the screenshot below.

The corrupt validator entries for the Ukraine Identity Card Check:

Following type of entry is present in Tomcat (localhost) log:

30 Oct 2019 15:34:09,014- Thread: 113 WARNING [com.vontu.i18n.VontuResourceBundleImpl] Could not find resource for key: policy.dataidentifier.validator.mbiNumberCheck
30 Oct 2019 15:34:09,014- Thread: 113 WARNING [com.vontu.i18n.VontuResourceBundleImpl] Could not find resource for key: policy.dataidentifier.validator.UkraineIdentityCardCheck.name
30 Oct 2019 15:34:09,014- Thread: 113 WARNING [com.vontu.i18n.VontuResourceBundleImpl] Could not find resource for key: policy.dataidentifier.validator.UkraineIdentityCardCheck.description
30 Oct 2019 15:38:40,142- Thread: 116 WARNING [com.vontu.i18n.VontuResourceBundleImpl] Could not find resource for key: policy.dataidentifier.validator.UkraineIdentityCardCheck.name

Environment

Seen in Enforce 15.0 - 15.5, with the Cloud Detection Services. Note that it is not likely to occur for on-prem Detection Servers, such as Network Prevent for Email, etc.

Cause

Corrupt entries in database for Ukraine Identity Card Check validator are interfering with the operation (and detection) of Data Identifiers at the affected Detection Server. This can be caused by importing a 15.5 policy into Enforce as well. Even if the 15.5 environment has been upgraded to 15.8 and fixed in one environment, if you take that same policy and import it into another 15.8 environment it will break the validators. Also it has been found that the Netherlands Burgerservicenummer (Citizen Service Number) is a validator that if imported can become corrupt.

Resolution

If your current Enforce list of Validators is showing this issue, please contact Technical Support for a solution for DLP 15.0-15.5 MP2.

There will also be a fix for this in the coming release of DLP, expected in version 15.7.