> 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-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/investigate-issues/issue-investigation-actions/add-a-file-path-to-a-malware-profile-allow-list.md).

# Add a file path to a malware profile allow list

{% hint style="info" %}
Requires Cortex XSIAM Enterprise, Premium, or any other XSIAM license that includes endpoints or Cortex Cloud Runtime Security.
{% endhint %}

During investigation, if you deem a file path to be safe, you can add the file path to an existing malware profile allow list directly from the **Issues** table.

1. In the **Issues** table, select the **Initiator Path**, **CGO path**, and/or **File Path** field values you want to add to your malware profile allow list.
2. Right-click and select **Add \<path type> to malware profile allow list**.
3. In the **Add \<path type> to malware profile allow list** dialog, select from your existing **Profiles** and **Modules** to which you want to add the file path to the allow list.
4. (Optional) View your Malware profile allow list.
   1. Go to Inventory+Endpoints → Policy Management → Prevention → **Profiles** and locate the malware profile you selected.
   2. Right-click, select **Edit Profile** and locate in the **Files / Folders in Allow List** section the path file you added.

For more information about malware prevention profiles, see **Set up malware prevention profiles**.


---

# 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-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/investigate-issues/issue-investigation-actions/add-a-file-path-to-a-malware-profile-allow-list.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.