> 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-5.x/configure-cortex-xdr/configure-and-deploy-cortex-xdr/enable-the-analytics-engine-and-identity-analytics.md).

# Enable the Analytics Engine and Identity Analytics

Learn how to enable the Analytics Engine and Identity Analytics.

Cortex XDR - Analytics includes the following:

* **Cortex XDR Analytics Engine:** Analyzes your endpoint data to develop a baseline and raise Analytics and Analytics BIOC alerts when anomalies and malicious behaviors are detected.
* **Identity Analytics:** Allows the Cortex XDR Analytics engine to aggregate and display user profile details, activities, and alerts related to a user-based Analytics type alert and Analytics BIOC rule during an investigation.

{% hint style="warning" %}

### Prerequisite

**Analytics Engine**

To create a baseline for enabling analytics, Cortex XDR requires a minimum of one of the following data sets:

* EDR or Network logs from at least 30 endpoints over a minimum of 2 weeks
* Cloud audit logs over a minimum of 5 days

**Identity Analytics**

* Cortex XDR - Analytics must be activated.
* Cloud Identity Engine must be set up. For more information, see [Set up Cloud Identity Engine](/cortex-xdr-5.x/configure-cortex-xdr/configure-and-deploy-cortex-xdr/set-up-cloud-identity-engine.md).
  {% endhint %}

How to enable analytics

1. Select **Settings** → **Configurations** → **Cortex XDR - Analytics**.
2. Click **Enable**. Creating a baseline can take up to three hours.

   Adding Windows DHCP logs can enhance the Analytics Engine. For more information, see Ingest Windows DHCP Logs with an XDR Collector Profile.
3. Activate **Identity Analytics** by turning on the toggle.


---

# 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-5.x/configure-cortex-xdr/configure-and-deploy-cortex-xdr/enable-the-analytics-engine-and-identity-analytics.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.