> 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/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-issues/causality-view/cloud-causality-view.md).

# Cloud causality view

On the cloud causality view you can analyze and respond to Cortex XDR issues and cloud audit logs. 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 cloud causality view presents the event identity and /or IP address and the actions performed by the identity on the cloud resource. On each node in the CI chain, Cortex XDR provides information to help you understand what happened around the event.

The following sections describe the different areas of the cloud 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 view presents a single event CI chain. The CI chain is built from Identity and Resource nodes. The Identity node represents for example keys, service accounts, and users, while the Resource node represents for example network interfaces, storage buckets, or disks. When available, the chain might also include an IP address and issue that were triggered on the Identity and Cloud Resource.

Causality data is displayed as follows:

* **Identity node:** Displays the name of the identity, generated issue information, and if available the associated IP address.
* **IP address node:** Displays the IP address associated with the Identity.
* **Operations:** Lists the type of operations performed by the identity on the cloud resources. Hover over the operation to display the original operation name as provided by the cloud Provider.
* **Cloud resource node:** Displays the referenced resource on which the operation was performed. For more information about the cloud resources icons, see [Key of cloud resource icons](#key-of-cloud-resource-icons).

**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 ![causality-view-reset-icon.png](/files/3PKn3dZbKcKFOFbwkLwB) in the lower-right of the CI graph.

</details>

<details>

<summary>Information Overview</summary>

Summarizes information about the issue you are analyzing, including the type of Cloud Provider, Project, and Region on which the event occurred. Select **View Raw Log** to view the raw log as provided by the Cloud Provider in JSON format.

</details>

<details>

<summary>All Events table</summary>

Displays up to 100,000 related events and up to 1,000 related issues. In the **All Events** table, Cortex XDR displays detailed information about each of the related events. To simplify your investigation, Cortex XDR scans your Cortex XDR data aggregating the events that have the same Identity or Resource and displays the entry with an ![cloud-causality-aggregated-events.png](/files/fV4AHkx6Fki5jKPmK9Bl) aggregated icon. Right-click and select **Show Grouped Events** to view the aggregated entries.

Entries highlighted in red indicate that the specific event created an issue. To continue the investigation, right-click to **View in XQL**. To continue the investigation, in the **Issues** table, right-click an issue to see the available actions.

</details>

<details>

<summary>Key of cloud resource icons</summary>

The following table lists the cloud resource icons:

<table><thead><tr><th width="147">Icon</th><th>Type of Resource</th></tr></thead><tbody><tr><td><img src="/files/0U8FqnMP83bfu06EwVJK" alt="cloud-causality-compute-instance.png"></td><td>Compute instance resource</td></tr><tr><td><img src="/files/Ov4bnMln5qNpg8eDOwv2" alt="cloud-causality-disks.png"></td><td>Disk resource</td></tr><tr><td><img src="/files/KDqOlO7aGi83MWsePz29" alt="cloud-causality-general.png"></td><td>General resource</td></tr><tr><td><img src="/files/TlmQB3q59uvBLjAhWJyF" alt="cloud-causality-images.png"></td><td>Image resource</td></tr><tr><td><img src="/files/kxYkSSPEoBf4V60Y5Gb1" alt="cloud-causality-network-interface.png"></td><td>Network interface resource</td></tr><tr><td><img src="/files/orqsMm8rsbHRBnLe6zwd" alt="cloud-causality-fw.png"></td><td>Security group (FW rule) resource</td></tr><tr><td><img src="/files/21bJ2CEDWivDEVdGzNC4" alt="cloud-causality-bucket.png"></td><td>Storage bucket resource</td></tr><tr><td><img src="/files/7ha7mhesAW4m0PF0Bjd4" alt="cloud-causality-vpc.png"></td><td>Virtual private cloud (VPC) resource</td></tr></tbody></table>

</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-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-issues/causality-view/cloud-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.