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

# Associated assets and artifacts

Review assets and artifacts associated with a case.

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](https://1107972533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHpcayc1yGiwVhvGJ7DK1%2Fuploads%2Fgit-blob-3e8ae02b4e15e23f4919dffcad400975b6326dbc%2Fca45e39855d338b79d844848bdcccad282ac2b1de2ba09db06f9ff9908ecedb2.png?alt=media) 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-cloud-posture-management/cases-and-issues/investigation-and-response/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 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/cortex-cloud-posture-management/cases-and-issues/analyze-and-resolve-cases/analyze-case-details/associated-assets-and-artifacts.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.