> 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-xsoar-8-on-prem/8.14/investigate-and-respond-to-threats/incidents-and-indicators-investigation/investigate-an-incident/investigate-an-incident-using-the-canvas.md).

# Investigate an incident using the canvas

While you're investigating an incident, you can use the canvas to create a visual map of the incident and it's associated incidents and indicators. This enables you to analyze the threat landscape of the investigation. Using the canvas, you and other team members can produce threat hunting activities to enhance the organization's security defenses.

To access the investigation canvas, click **Canvas** from the incident you want to investigate. The incident or indicator appears on the canvas display. In the **Add entity to canvas** section, Cortex XSOAR provides suggested indicators and incidents that might be related or relevant to the current incident for you to add to the canvas.

**Incident Suggestions**

The incidents are calculated according to the related incidents algorithm, which are based on several factors:

* Common labels
* Common indicators
* Common incident custom fields

You can add the incidents by dragging and dropping the incident onto the canvas.

**Indicator Suggestions**

The indicators are determined according to the following factors (in this order):

1. Indicators with a malicious verdict from the original incident (the incident that initiated the investigation).
2. Indicators that are shared between incidents that you added to the canvas.
3. The malicious ratio, which is the ratio between the indicators that appear in incidents with a malicious verdict, compared to the total number of incidents in Cortex XSOAR.

You can add the indicators by dragging and dropping the indicators onto the canvas.

**Key Features**

You can do the following:

* **Quick view of the incident and indicator**: Click the incident or indicator to view details.
* **Connect incidents**: Connect each incident by linking each incident and use comments on entity connections to communicate important information with team members by adding notes to connectors between entities.
* **Adding notes**: You can add notes on the connection. Using notes enables you and other team members to collaborate on important issues. The note also shows the last user to edit the note and the time it was edited.
* **Dynamic Connections**: When you rearrange entities on the canvas, the connections dynamically move with the entities. Connections that are dotted lines indicate that the indicator is part of the investigation, or two incidents are defined as related incidents. These connections are dynamic, which means if one entity is an IP address and you add that IP address to the allow list after it was added to the canvas, the dotted-lined connection is automatically removed.
* **Capture the Canvas as an image**: Capture and study the incident by clicking **Export to PNG** or **Export snapshot to War Room**.
* **Relationships**: You can expand or add relationships. From the entity, right-click and select **Expand Relationships**.
* **Search**: You can search by incident or indicator fields or values.
* **Highlight**: Right-click the selected incident or indicator and select **Highlight**.


---

# 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-xsoar-8-on-prem/8.14/investigate-and-respond-to-threats/incidents-and-indicators-investigation/investigate-an-incident/investigate-an-incident-using-the-canvas.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.