> 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-agentix/reference-and-developer-docs/cortex-agentix-xql/build-xql-queries/legacy-query-builder/query-across-all-entities.md).

# Query across all entities

Query across all entities with Legacy Query Builder in Cortex AgentiX.

***

Use the **Query Builder** to search hosts and processes across file, network, registry, and process events. You can also search Windows event logs and Linux system authentication logs.

For example, you can search for:

* All activity on a host.
* All activity initiated by a process on a host.

How to build a query

1. From Cortex AgentiX, select **Investigation & Response** → **Search** → **Query Builder**.
2. Select **ALL ACTIONS**.
3. Optional: Limit the scope to a specific acting process.

   Select **Add Process**. Then specify one or more attributes for the acting parent process.

   Use a pipe (`|`) to separate values. Use an asterisk (`*`) to match any characters.

   * **NAME**: Parent process name.
   * **PATH**: Parent process path.
   * **CMD**: Parent process command line, including arguments, up to 128 characters.
   * **MD5**: Parent process MD5 hash.
   * **SHA256**: Parent process SHA256 hash.
   * **USER NAME**: User who executed the process.
   * **SIGNATURE**: Parent process signing status.
   * **SIGNER**: Entity that signed the parent process certificate.
   * **PID**: Parent process ID.
   * **Run search on process, Causality and OS actors**: Applies the criteria to initiating processes. Clear this option to configure different attributes.
4. Optional: Limit the scope to an endpoint or its attributes.

   Select **Add Host**. Then specify one or more attributes:

   * **HOST**: **HOST NAME**, **HOST IP** address, **HOST OS**, **HOST ADDRESS**, or **INSTALLATION TYPE**.
   * **INSTALLATION TYPE**: Agent or data collector.
   * **PROCESS**: **NAME**, **PATH**, **CMD**, **MD5**, **SHA256**, **USER NAME**, **SIGNATURE**, or **PID**.

   Use a pipe (`|`) to separate values. Use an asterisk (`*`) to match any characters.
5. Specify the event time period.

   Select **Last 24H**, **Last 7D**, **Last 1M**, or **Custom**.
6. Choose when to run the query.

   Select the calendar icon to schedule it. Select **Run** to run it immediately. View results in the **Query Center**.

   You can leave the page while the query runs. You receive a notification when it completes. You can also **Cancel** the query or run a new query.
7. Review the query results.


---

# 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-agentix/reference-and-developer-docs/cortex-agentix-xql/build-xql-queries/legacy-query-builder/query-across-all-entities.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.