> 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-xpanse/incidents-and-alerts/alerts.md). # Alerts An *alert* is a potential security risk identified by Cortex Xpanse on your services and assets. Alerts are triggered by attack surface rules, which define the risks Xpanse is looking for and the severity assigned to those risks. Xpanse groups alerts into incidents, which are collections of alerts related to a single service or asset. View all your alerts in a table format on the **Alerts** page, where you can filter, sort, and search alerts. To view the **Alerts** page, go to **Incident Response** → **Alerts**. Refer to the following resources for additional information: * See [Filter Page Results](/cortex-xpanse/reference/list-view-options/filter-page-results.md) for information about filtering tables. * See [Search Page Results](/cortex-xpanse/reference/list-view-options/search-page-results.md) for details about how to search within tables. * See [Alert Fields](/cortex-xpanse/incidents-and-alerts/alerts/alert-fields.md) for descriptions of the fields in the Alerts table. Select an alert in the table to open the alert details page on a separate tab in your browser. The alerts details page includes most of the information you need to investigate and remediate an alert, including the owner of the related incident, service and website details, relevant asset details, and remediation guidance. You can also view alerts in the context of an incident on the **Incidents** page. The **Alerts** tab in an incident provides detailed information about each alert in the incident. --- # 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/cortex-xpanse/incidents-and-alerts/alerts.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.