> 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/analyze-and-resolve-cases/analyze-case-details/associated-assets-and-artifacts.md).

# Associated assets and artifacts

This section displays the technical entities involved in the case, such as endpoints, hosts, IP addresses, and files. Assets and artifacts are organized by class, such as User, Hash, or IP. Malicious artifacts as identified by WildFire are highlighted red.

Hover over an asset or artifact to see key details about the entity. Click on an asset to see full details in the asset card.

To investigate further, click **Ask AI** next to an asset or artifact to open the **Agentic Assistant** with an automatically generated prompt tailored to the selected entity. You can also use the **Actions** ![Actions\_icon.png](/files/cLGeogsMVfdpnqVMdFCh) menu next to an asset or artifact to drill down to dedicated views or take direct actions on the asset or artifact.

{% hint style="info" %}

### Note

If you do not have permissions to access an asset of a case (which is shown as grayed out and locked), check your scoping permissions in **Manage Users** or **Manage User Groups**.
{% endhint %}

For more information about dedicated asset and artifact views, see [Investigate artifacts and assets](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-artifacts-and-assets.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/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/analyze-and-resolve-cases/analyze-case-details/associated-assets-and-artifacts.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.