> 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/analytics-alerts/cortex-analytics-alert-reference.md). # Cortex Analytics Alert Reference The Cortex Analytics Alert Reference describes every Analytics alert that Cortex can raise. Use this reference to understand what an alert means and what you should do about it. ## How this reference is organized * [**Alerts by name**](/analytics-alerts/alerts-by-name.md) — every Analytics alert, listed alphabetically. Each alert page covers its synopsis (activation, training, test, and deduplication periods, required data, detection modules, MITRE ATT\&CK mapping, and severity), a description, the attacker's goals, and recommended investigative actions. Some alerts also document variations. * [**Alerts by data source**](/analytics-alerts/alerts-by-data-source.md) — the same alerts, grouped by the data source that produces them. The Analytics alerts that Cortex can raise depend on the data sources you integrate with Cortex. Some alerts require a combination of data sources, and you can improve the accuracy of some alerts by adding additional data sources. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/cortex-analytics-alert-reference.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.