> 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/reference/list-view-options/search-page-results.md).

# Search Page Results

You can search the content in the Alerts and Incidents tables.

Cortex Xpanse supports the ability to search the content in alert and incident tables. On the **Alerts** page, Cortex Xpansesearches key alert fields and fields for assets related to the alert, including Alert Name, Attack Surface Rule, Country, City, IP/IP Prefix/ CIDR, Domain Name, certificate characteristics, and specific pieces of scan data such as banners, version information, and other details on the service and website (i.e. service classification and web technologies). On the **Incidents** page, Cortex Xpanse searches incident fields and fields for related alerts and assets.

To perform a search, navigate to the **Alerts** or **Incidents** page, enter a search term in the search bar above the table, and hit enter. Note the following search guidelines:

* You can use search and filters together. When you use both search and a filter, Cortex Xpanse processes them with an "and" operator. For example, if you search alerts for "RDP" and filter for **Resolution Status = New**, the search results will have **New** alerts that contain "RDP".
* XQL doesn't work in the search bar.
* The following characters are treated as delimiters:

  \[ ] < > ( ) { } | ! ; , ' " \* & ? + / = @ - $ % \ \_ \n \r \s \t

  If you use these characters in a search string, Cortex Xpanse will separate the string into separate search terms.
* Partial prefix string matching is supported. That means a search for "micro" will return results for Microsoft, but a search for "soft" will not return results for Microsoft.
* You can search for IPv4 addresses using CIDR notation, wildcard notation, and exact strings.


---

# 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-xpanse/reference/list-view-options/search-page-results.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.