> 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/detection-readiness-and-learning-period.md).

# Detection readiness and learning period

Learn when Cortex XDR detections activate and how analytics learning periods establish baselines.

Detections in Cortex XDR start at different times depending on the type of detection.

| Detection type                                   | When it starts                                        |
| ------------------------------------------------ | ----------------------------------------------------- |
| Agent prevention (malware, exploits, ransomware) | As soon as the agent installs and receives its policy |
| IOC, BIOC, and correlation rules                 | As soon as relevant data is ingested                  |
| Analytics (behavioral) detectors                 | After each detector's activation and training periods |

### Analytics learning periods

Analytics detectors need data to build a baseline before they can flag anomalies. Each detector has:

* An **activation period**, to gather enough data before it starts running.
* A **training period**, used to build and continuously tune the baseline.
* A **test period**, used to compare recent activity against the baseline.

The periods are detector-specific, and they start when relevant data begins to arrive, not when the full deployment is complete. Onboard high-value sources early so their baselines are ready sooner. See [Analytics detection time intervals](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/threat-management/analytics/analytics-detection-time-intervals) and the [Analytics alerts reference](https://cortex-docs.paloaltonetworks.com/analytics-alerts/cortex-analytics-alert-reference) for the requirements of each detector.


---

# 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/detection-readiness-and-learning-period.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.