> 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-cloud-posture-management/cases-and-issues/investigation-and-response/investigate-issues/issue-investigation-actions/query-case-and-issue-data.md).

# Query case and issue data

Query case and issue data using XQL.

Cortex Cloud uses Cortex Query Language (XQL) as the primary language for searching, analyzing, and transforming security data. XQL allows for highly efficient querying across vast amounts of security telemetry, such as:

* **Threat hunting:** Proactively search for malicious activity, anomalies, and indicators of compromise.
* **Investigation:** Drill into underlying data, affected assets, and attacker actions.
* **Forensics:** Extract event details for post-incident analysis and compliance audits.
* **Reports and dashboards:** Visualize security posture and communicate insights to stakeholders.

To use sample investigative queries, go to **Investigation & Response** → **Search** → **Query Builder** → **XQL** → **Query Library**. For more information, see [Cortex Cloud XQL](/cortex-cloud-posture-management/cortex-cloud-xql/cortex-cloud-xql.md).

You can query case and issue data in the `cases` and `issues` datasets. When using the `issues` dataset, keep in mind the following:

* Informational issues are not included in this dataset.

The `issues` dataset is categorized by domain. To query only security issues, run:

```programlisting
dataset = issues | filter issue_domain = "SECURITY"
```

To query only posture issues, run:

```programlisting
dataset = issues | filter issue_domain = "POSTURE"
```


---

# 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-cloud-posture-management/cases-and-issues/investigation-and-response/investigate-issues/issue-investigation-actions/query-case-and-issue-data.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.