> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/threat-management/analytics/identity-analytics.md).
# Identity Analytics
Use Cortex XSIAM Identity Analytics to identify anomalous user and identity-related behavior.
Cortex XSIAM enables you to investigate suspicious user activity information using Identity Analytics. When enabled, Identity Analytics aggregates and displays user profile information, activity, and issues associated with a user-based Analytics type issue and Analytics BIOC rule.
To easily track the issues and Analytics BIOC rules, Cortex XSIAM displays an **Identity Analytics** tag in the **Issues** table > **Issue Name** field and **Analytics BIOC Rules** table > **Name** field. In the **Analytics Issue View**, when selecting the **User** node, Cortex XSIAM details the Active Directory group, organizational unit, role, logins, hosts, alerts, and process executions associated with the user.
To enable Identity Analytics, you must first:
* Set Up Cloud Identity Engine (formerly Directory Sync Services (DSS))
* Activate Cortex XSIAM Analytics
After configuring your Cloud Identity Engine instance and Cortex XSIAM Analytics, select **Settings (**
**)** → **Configurations** → **Cortex XSIAM - Analytics**, and in the **Featured in Analytics** section, **Enable** Identity Analytics.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/threat-management/analytics/identity-analytics.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.