> 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/prebuilt-detections-by-data-source.md).

# Prebuilt detections by data source

Explore Cortex XDR prebuilt detections by data source and review detection coverage in your tenant.

Cortex XDR includes a large, continuously updated library of prebuilt detections, including analytics detectors, analytics BIOCs, and correlation rules. Palo Alto Networks adds and tunes detections in content updates, so the count for each data source changes over time.

### See the detections for a data source

The [Analytics alerts reference](https://cortex-docs.paloaltonetworks.com/analytics-alerts/cortex-analytics-alert-reference) lists every analytics detection, organized two ways:

* [Alerts by data source](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-data-source): for example, Cortex XDR agent, AWS, Azure, and GCP audit logs, Okta, Microsoft Entra ID, Microsoft 365, Google Workspace, Palo Alto Networks firewalls, and third-party firewalls and VPNs.
* [Alerts by name](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name): each entry describes the activity, required data sources, MITRE ATT\&CK mapping, and learning requirements.

### See coverage in your tenant

The **MITRE ATT\&CK** coverage dashboard shows the detection rules and protection modules that apply to your tenant, mapped to tactics and techniques, together with the status of the contributing data sources. See [Review MITRE ATT\&CK framework coverage](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/threat-management/analytics/review-mitre-att-and-ck-framework-coverage).

{% hint style="info" %}
A data source with **active** status doesn't mean that every related detector is active. Some detectors need specific fields, log types, or learning periods.
{% endhint %}


---

# 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/prebuilt-detections-by-data-source.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.