Question

Contoso created an exact data match (EDM) sensitive information type based on a schema that includes CustomerID, LastName, and CreditCardNumber. Compliance analysts report that DLP is generating too many false positives because a match is triggered whenever a CreditCardNumber alone appears in a document, even without any related customer data. You need to reduce false positives by requiring that a detected CreditCardNumber must appear together with at least one other field from the same data row before it counts as an EDM match. Which EDM configuration change should you make?

Accepted Answer

Configure supporting elements (additional evidence) for the primary element in the EDM rule package so that CreditCardNumber requires a nearby matching supporting field.

Answer

Increase the confidence level of the underlying built-in Credit Card Number sensitive info type to High.

Answer

Re-upload the sensitive data table using a larger sample so the hashing algorithm becomes more selective.

Answer

Mark all three fields as primary elements so that any single field match satisfies the EDM condition.