> 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/protect-your-endpoints/endpoint-security/install-and-manage-endpoints/manage-endpoint-protection/view-information-about-your-endpoint-prevention-profiles.md).

# View information about your endpoint prevention profiles

View Cortex XSIAM endpoint prevention profiles and their configured protection settings.

The following table displays the fields that are available on the **Prevention Profiles** page, in alphabetical order. The table includes both default fields and additional fields that are available in the column manager. To view this page, go to **Inventory → Endpoints → Policy Management → Prevention → Profiles**.

| Field                  | Description                                                                                                           |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Associated Targets** | The endpoints or endpoint groups to which the profile is assigned                                                     |
| **Created By**         | The administrator who created the prevention profile                                                                  |
| **Created Time**       | The date and time at which the prevention profile was created                                                         |
| **Description**        | An optional description entered by an administrator to describe the prevention profile                                |
| **Modification Time**  | The date and time at which the prevention profile was modified                                                        |
| **Modified By**        | The administrator who modified the prevention profile                                                                 |
| **Name**               | The prevention profile name                                                                                           |
| **Profile ID**         | The ID assigned to to the profile by Cortex XSIAM                                                                     |
| **Summary**            | Summary of prevention profile configuration                                                                           |
| **Type**               | The prevention profile type, such as Malware or Agent Settings                                                        |
| **Usage Count**        | The number of policy rules that use the profile. If you want to delete a profile, ensure that this cell displays "0". |


---

# 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-xsiam/protect-your-endpoints/endpoint-security/install-and-manage-endpoints/manage-endpoint-protection/view-information-about-your-endpoint-prevention-profiles.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.