What configuration change is most likely required to produce data in User Risk Summary reports?

What configuration change is most likely required to produce data in User Risk Summary reports?

• A. User attributes have been incorrectly mapped to Active Directory accounts.
• B. The LDAP plugin is disabled.
• C. The report requires extra licensing.
• D. The user is not assigned to a project.

Answer: (A)

User Risk Summary reports depend on linking each risk event to a specific user by identity attributes drawn from the directory. If those user attributes aren’t correctly mapped to the corresponding Active Directory accounts, the system can’t associate events with the right users, so the report shows little or no data. The necessary change is to fix the user attribute mappings in the directory integration so that DLP uses the correct AD identifiers (for example, mapping the DLP user field to AD’s userPrincipalName or sAMAccountName). Once the mappings align, risk data will populate per user in the reports. Disabling the LDAP plugin would stop directory data from being imported altogether, which is broader than the targeted fix here, and licensing or project assignment wouldn’t specifically resolve the issue of correctly linking events to user identities.

User Risk Summary reports depend on linking each risk event to a specific user by identity attributes drawn from the directory. If those user attributes aren’t correctly mapped to the corresponding Active Directory accounts, the system can’t associate events with the right users, so the report shows little or no data. The necessary change is to fix the user attribute mappings in the directory integration so that DLP uses the correct AD identifiers (for example, mapping the DLP user field to AD’s userPrincipalName or sAMAccountName). Once the mappings align, risk data will populate per user in the reports. Disabling the LDAP plugin would stop directory data from being imported altogether, which is broader than the targeted fix here, and licensing or project assignment wouldn’t specifically resolve the issue of correctly linking events to user identities.