> 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/xsoar-6-administrator-guide/6.15/investigate-and-respond-to-threats/day-to-day-tasks-in-cortex-xsoar/incident-management/evidence-handling.md).

# Evidence Handling

Add and manage investigation evidence in the Cortex XSOAR 6.15 War Room.

You can view or designate any entity as evidence, which enables you to reconstruct attack chains and piece together key pieces of verification for root cause discovery.

In the War Room, you can mark any entity as evidence by clicking the flag next to each entry. You can view the evidence in the War Room or open the evidence entry from the Evidence Board. When adding evidence, you need to add a description that should contain enough details that can be used for future reference. Adding a tag helps you to find the evidence by searching for the tag. You can also add an occurrence date and time.

{% hint style="info" %}
Adding tags to evidence from the Evidence Board does not create the same tags in the War Room.
{% endhint %}

### **Custom Evidence Fields**

To create custom evidence fields, go to **Settings** → **Objects Setup** → **Incidents** → **Evidence Fields** → **New Field**. When you mark entities as evidence in the War Room, you have the option to enter data for your custom evidence fields.

### **Evidence Board**

The Evidence board stores key artifacts for current and future analysis. You can view and manage evidence entities that were detected in the **War Room** and designated as Evidence.

You can search for evidence and select the date range when the evidence occurred.

Evidence can be viewed in **Table View** or **Summary View**. In the **Table View**, you can remove, export, or show in the **War Room**. In the **Summary View** you can remove or edit the evidence.


---

# 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/xsoar-6-administrator-guide/6.15/investigate-and-respond-to-threats/day-to-day-tasks-in-cortex-xsoar/incident-management/evidence-handling.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.