DLP User groups and Profiled DGM rules no longer trigger matches after Enforce CPU is upgraded.

Products

• Data Loss Prevention Core Package
• Data Loss Prevention Network Email

Issue/Introduction

Enforce CPU is upgraded to a newer model and is different than the Detection server CPUs causing some DLP rules to stop triggering.

Environment

DLP 15.8 MP3

Enforce and Detection servers on VMware.

Cause

Enforce CPU hash calculation creates hash values when creating the User Group index.

When evaluated on an older cpu, these values may not match.

Resolution

Solution 1: Upgrade to DLP 16.0.2

Solution 2: Resolve CPU mismatch

1. Upgrade the Detection server CPUs to match the Enforce CPU.
2. Re-index the User Group or Profiled DGM.