> 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-xdr/insights-and-tips-cortex-xdr/detection-engineering-and-threat-intelligence/identity-analytics-and-itdr.md).

# Identity analytics and ITDR

Learn how Identity Analytics and ITDR detect identity threats and assess user risk in Cortex XDR.

Cortex XDR provides user and entity behavior analytics (UEBA) at two levels.

|                         | Identity Analytics                                                                     | ITDR add-on                                                                                                                                                       |
| ----------------------- | -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Availability            | Included; enable it in Analytics settings                                              | Add-on license                                                                                                                                                    |
| Focus                   | Profiles users and flags anomalous behavior in analytics issues                        | Identity threat detection, risk management, and identity posture                                                                                                  |
| User context            | User profile, Active Directory groups, logins, hosts, and issues in the analytics view | **User Risk View**, **Risk Management dashboard**, and automated **Asset Roles**                                                                                  |
| Additional capabilities | —                                                                                      | Identity detection rules, Active Directory Security Posture Management (AD-SPM), Conditional Access Policy, LDAP protection, and response and remediation content |

### Enable Identity Analytics

1. Set up the Cloud Identity Engine.
2. Activate Analytics.
3. In **Settings** → **Configurations** → **Analytics**, enable **Identity Analytics**.

See Identity Analytics and [Enable the Analytics Engine and Identity Analytics](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/configure-and-deploy-cortex-xdr/enable-the-analytics-engine-and-identity-analytics).

### ITDR

See [Identity Threat Detection and Response (ITDR)](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/identity-threat-module-itdr).

### Data sources

Identity analytics uses data from identity providers (such as Microsoft Entra ID, Okta, and Ping Identity), Active Directory, endpoints, and network logs. Third-party UEBA alerts can also be ingested through integrations.


---

# 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-xdr/insights-and-tips-cortex-xdr/detection-engineering-and-threat-intelligence/identity-analytics-and-itdr.md?ask=<question>&goal=<user_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.