The CISO has attempted to generate a User Risk Summary report, but it is blank despite User Reporting privileges. What is the probable reason?

The CISO has attempted to generate a User Risk Summary report, but it is blank despite User Reporting privileges. What is the probable reason?

• A. User attributes have been incorrectly mapped to Active Directory accounts.
• B. The LDAP plugin is disabled.
• C. The report requires a higher data retention.
• D. The license does not include User Risk reporting.

Answer: (A)

The main idea this question tests is how user risk data is linked to individual identities in the system. A User Risk Summary pulls together risk events and ties them to specific users by matching the events to user identities stored in Active Directory (or another directory). That linkage depends on mapping user attributes (like user ID, login name, email) in the DLP system to the corresponding AD accounts. If those attributes are mapped incorrectly, the system cannot resolve which user each risk event belongs to. Even though you have the right privileges to view the report, there’s nothing for the report to display because every risk event remains orphaned without a correct user association. That’s why the summary comes up blank. Other possibilities, like the LDAP plugin being disabled, would generally disrupt directory access more broadly and likely affect other directory-dependent features as well, not just a single user risk summary. Licensing or data retention issues could prevent some features from appearing or show stale data, but they don’t explain a complete blank result when identity mapping is the root cause.

The main idea this question tests is how user risk data is linked to individual identities in the system. A User Risk Summary pulls together risk events and ties them to specific users by matching the events to user identities stored in Active Directory (or another directory). That linkage depends on mapping user attributes (like user ID, login name, email) in the DLP system to the corresponding AD accounts.

If those attributes are mapped incorrectly, the system cannot resolve which user each risk event belongs to. Even though you have the right privileges to view the report, there’s nothing for the report to display because every risk event remains orphaned without a correct user association. That’s why the summary comes up blank.

Other possibilities, like the LDAP plugin being disabled, would generally disrupt directory access more broadly and likely affect other directory-dependent features as well, not just a single user risk summary. Licensing or data retention issues could prevent some features from appearing or show stale data, but they don’t explain a complete blank result when identity mapping is the root cause.