> 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-xsoar-8-on-prem/8.13/investigate-and-respond-to-threats/threat-intel-management/indicator-management/query-indicators.md).

# Query indicators

Query indicators in Cortex XSOAR 8.13 On-prem.

You can access Threat Intel data through the following methods:

* On the **Threat Intel** page, select an indicator to start investigating.
* When investigating an incident, select an extracted indicator. The **Quick View** shows basic information about the indicator in Cortex XSOAR. **Full view** shows the full Cortex XSOAR indicator summary.
* On the **Threat Intel** page, query an indicator.

  The Threat Intel library is a centralized space for all indicators, whether they are found in an incident, brought in as a feed, or added manually. You can view in-depth information on collected indicators and filter the library based on common attributes.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>You can search or look up indicators. A search, which can include wildcards and complex queries, can return multiple results. Lookups are exact values and can only return one result.</p></div>

**Indicator query fields**

You can search for indicators using any of the available search fields. This is a partial list of the available search fields.

| Field                       | Description                                                                                                          |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| **`type`**                  | The type of the indicator, such as File or Email.                                                                    |
| **`verdict`**               | <p>The reputation of the indicator:</p><ul><li>Malicious</li><li>Suspicious</li><li>Benign</li><li>Unknown</li></ul> |
| **`aggregatedReliability`** | Searches for indicators based on a reliability score such as **`A - Completely reliable`**.                          |
| **`sourceBrands`**          | Indicator feed or enrichment integrations.                                                                           |
| **`sourceInstances`**       | A specific instance of an indicator feed or enrichment integration.                                                  |
| **`expirationSource`**      | The source (such as script or manual.) that last sets the indicator's expiration status.                             |
| **`tags`**                  | Tags applied to indicators.                                                                                          |
| **`comments`**              | Search for keywords within indicators’ comments.                                                                     |
| **`isShared`**              | (*Multi-tenant*) Whether the indicator is shared with the tenant.                                                    |

You can use a wildcard query, which finds indicators containing terms that match the specified wildcard. For example, the **`*`** pattern matches any sequence of 0 or more characters, and **`?`** matches any single character. For a regex query, use the following value:

`"/.*\\?.*/"`


---

# 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-xsoar-8-on-prem/8.13/investigate-and-respond-to-threats/threat-intel-management/indicator-management/query-indicators.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.