> 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/reference-and-developer-docs/role-based-access-control/inventory-agent-permissions/agent-prevention-policies.md).

# Agent Prevention Policies

Agent Prevention Policies define the security posture for endpoints.

| Permissions | Description                                                                                                                                                                                   | Roles Example                                                                                                                                                                                                                                                                                           |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None        | Cannot view the Policy Rules page (**Inventory** → **Endpoints** → **Policy Management** → **Prevention** → **Policy Rules**), which includes endpoint details, or view policy effectiveness. |                                                                                                                                                                                                                                                                                                         |
| View        | View the Prevention Policies menu, including viewing the policies list, details, protection settings, and viewing assigned groups.                                                            | <ul><li>SOC Tier-1 Analyst: Understanding policies helps explain why actions were blocked or allowed.</li><li>SOC Tier-2 Analyst: Policy visibility is essential for understanding protection posture</li><li>Threat Hunter: Understanding prevention policies helps identify detection gaps.</li></ul> |
| View/Edit   | All view capabilities plus creating, editing, deleting, and copying policies, assigning, and setting policy priority.                                                                         | <ul><li>SOC Tier 3 Analyst: May provide input on policy improvements, but changes should go through change management.</li><li>Security Engineer: Primary responsibility for policy development and implementation.</li></ul>                                                                           |

**Required and recommended permissions**

Consider adding the following permissions:

| Permission            | Permission Level | Reason                                                                                                                                                                                                                                                                          |
| --------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Agent Groups          | View             | Required for policy assignment.                                                                                                                                                                                                                                                 |
| Agent Administrations | View             | Strongly recommended. View endpoints to validate policy deployment and verify protection status after changes.                                                                                                                                                                  |
| Global Exceptions     | View             | Strongly recommended. Exceptions modify policy behavior. Understanding active exceptions is essential for accurate policy assessment. View/Edit. Required. Policy changes often require corresponding exception updates. Without exception access, policy tuning is incomplete. |
| Host Insights         | View             | Recommended for viewing policy effectiveness.                                                                                                                                                                                                                                   |
| Agent Profiles        | View             | Strongly recommended. Prevention profiles define the detailed security settings within policies. Understanding profiles is essential for effective policy design.                                                                                                               |
| Cases & Issues        | View             | Recommended. Review security events to inform policy tuning decisions. Understanding what threats are being detected helps optimize policies.                                                                                                                                   |


---

# 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/reference-and-developer-docs/role-based-access-control/inventory-agent-permissions/agent-prevention-policies.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.