> 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-xdr-5.x/reference-and-developer-docs/cortex-xdr-xql/build-xql-queries/legacy-query-builder/create-network-connections-query.md). # Create network connections query From the Query Builder, you can investigate network events stitched across endpoints and the Palo Alto Networks Next-Generation Firewall logs. Some examples of a network query you can run include: * Source and destination of a process. * Network connections that included a specific App ID * Processes that created network connections. * Network connections between specific endpoints. ### How to build a network connection query 1. From Cortex XDR, select **Investigation & Response** → **Search** → **Query Templates**. 2. Select **NETWORK CONNECTIONS**. 3. Enter the search criteria for the network events query. * Network attributes: Define any additional process attributes for which you want to search. Use a pipe (**`|`**) to separate multiple values (for example **`80|8080`**). By default, Cortex XDR will return the events that match the attribute you specify. To exclude an attribute value, toggle the **`=`** option to **`=!`**. Options are: * **APP ID**: App ID of the network. * **PROTOCOL**: Network transport protocol over which the traffic was sent. * **SESSION STATUS** * **FW DEVICE NAME**: Firewall device name. * **FW RULE**: Firewall rule. * **FW SERIAL ID**: Firewall serial ID. * **PRODUCT** * **VENDOR** To specify an additional exception (match this value except), click the **+** to the right of the value and specify the exception value. 4. (Optional) To limit the scope to a specific source, click the **+** to the right of the value and specify the exception value. Specify one or more attributes for the source. Use a pipe (**|**) to separate multiple values. Use an asterisk (**\***) to match any string of characters. * **HOST NAME**: Name of the source. * **HOST IP**: IP address of the source. * **HOST OS**: Operating system of the source. * **PROCESS NAME**: Name of the process. * **PROCESS PATH**: Path to the process. * **CMD**: Command-line used to initiate the process, including any arguments, up to 128 characters. * **MD5**: MD5 hash value of the process. * **SHA256**: SHA256 hash value of the process. * **PROCESS USER NAME**: User who executed the process. * **SIGNATURE**: Signing status of the parent process: Signature Unavailable, Signed, Invalid Signature, Unsigned, Revoked, Signature Fail. * **PID**: Process ID of the parent process. * **IP**: IP address of the process. * **PORT**: Port number of the process. * **USER ID**: ID of the user who executed the process. * **Run search for both the process and the Causality actor**: The causality actor—also referred to as the causality group owner (CGO)—is the parent process in the execution chain that the app identified as being responsible for initiating the process tree. Select this option if you want to apply the same search criteria to the causality actor. If you clear this option, you can then configure different attributes for the causality actor. 5. (Optional) Limit the scope to a destination. Use a pipe (**|**) to separate multiple values. Use an asterisk (**\***) to match any string of characters. Specify one or more of the following attributes: * **REMOTE IP**: IP address of the destination. * **COUNTRY**: Country of the destination. * Destination **TARGET HOST**,**NAME**, **PORT**, **HOST NAME**, **PROCESS USER NAME**, **HOST IP**, **CMD**, **HOST OS**, **MD5**, **PROCESS PATH**, **USER ID**, **SHA256**, **SIGNATURE**, or **PID** 6. Specify the time period for which you want to search for events. Options are **Last 24H** (hours), **Last 7D** (days), **Last 1M** (month), or select a **Custom** time period. 7. Choose when to run the query. Select the calendar icon to schedule a query to run on or before a specific date or **Run** to run the query immediately and view the results in the **Query Center**. While the query is running, you can always navigate away from the page and a notification is sent when the query completes. You can also **Cancel** the query or run a new query, where you have the option to **Run only new query (cancel previous)** or **Run both queries**. 8. When you are ready, view the results of the query. For more information, see [Review XQL query results](/cortex-xdr-5.x/reference-and-developer-docs/cortex-xdr-xql/build-xql-queries/how-to-build-xql-queries/review-xql-query-results.md). --- # 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-xdr-5.x/reference-and-developer-docs/cortex-xdr-xql/build-xql-queries/legacy-query-builder/create-network-connections-query.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.