> 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-runtime-security/cases-and-issues/investigation-and-response/investigate-issues/causality-view/network-causality-view.md).

# Network causality view

On the network causality view you can analyze and respond to stitched firewall and endpoint issues. On this view you can see the causality (cause and effect) of events of the entire process execution chain that led up to the issue. The network causality view presents the network processes that triggered the issue, generated by Cortex Cloud, Palo Alto Networks next-generation firewalls, and supported sources, such as 3rd party network sources.

On each node in the CI chain, Cortex Cloud provides information to help you understand what happened around the issue. The CI chain visualizes the firewall logs, endpoint files, and network connections that triggered issues connected to a security event.

{% hint style="info" %}

### Note

The network causality view displays only the information it collects from the detectors. It is possible that the CI may not show some of the firewall or agent processes.
{% endhint %}

The following sections describe the different areas of the network causality view:

<details>

<summary>Causality instance chain</summary>

Includes the graphical representation of the Causality Instance (CI) along with other information and capabilities to enable you to conduct your analysis.

The Causality View presents a CI chain for each of the processes and the network connection. The CI chain is built from process nodes, events, and issues. The chain presents the process execution and might also include events that these processes caused and issues that were triggered by the events or processes. The Causality Group Owner (CGO) is displayed on the left side of the chain. The CGO is the process that is responsible for all the other processes, events, and issues in the chain. You need the entire CI to fully understand why the issue occurred.

The color of a process node correlates to the WildFire verdict.

#### **Navigation**

You can move the chain, extend it, and modify it. To adjust the appearance of the CI chain, use the size controls on the right. You can also move the chain by selecting and dragging it. To return the chain to its original position and size, click <img src="/files/jFSo35iktmOab6DPrIKV" alt="causality-view-reset-icon.png" data-size="line"> in the lower-right of the CI graph.

#### **Actions**

Hover over a process node to display a **Process Information** pop-up listing useful information about the process. From any process node, you can also right-click to display additional actions that you can perform during your investigation:

* **Show parents and children:** If the parent is not presented by default, you can display it. If the process has children, Cortex Cloud opens a dialog displaying the **Children** **Process Start Time**, **Name**, **CMD**, and **Username** details.
* **Hide branch:** Hide a branch from the causality view.
* **Add to block list or allow list, terminate, or quarantine a process:** If after investigating the activity in the CI chain, you want to take action on the process, you can select the desired action to allow or block the process across your organization.

  In the causality view of a **Detection (Post Detected)** type issue, you can also **Terminate process by hash**.

</details>

<details>

<summary>Information Overview</summary>

Summarizes information about the issue you are analyzing, including the host name, the process name on which the issue was raised, and the host IP address. For issues raised on endpoint data or activity, this section also displays the endpoint connectivity status and operating system.

</details>

<details>

<summary>Host isolation</summary>

You can choose to isolate the host, on which the issue was triggered, from the network or initiate a live terminal session to the host to continue investigation and remediation.

</details>

<details>

<summary>All Events table</summary>

Displays all related events for the process node which match the issue criteria that were not triggered in the issue table but are informational. You can also export the table results to a tab-separated values (TSV) file.

For the Behavioral Threat Protection table, right-click to add to allow list or block list, terminate, and quarantine a process.

{% hint style="info" %}

### Tip

To view statistics for files on VirusTotal, you can pivot from the Initiator MD5 or SHA256 value of the file on the Files tab.
{% endhint %}

</details>


---

# 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-cloud-runtime-security/cases-and-issues/investigation-and-response/investigate-issues/causality-view/network-causality-view.md?ask=<question>&goal=<endgoal>
```

`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.
