> 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-profiles.md).
# Agent Profiles
Defines agent behavior and configuration settings, including agent communication settings and proxy configurations.
| Permissions | Description | Roles Example |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None | Cannot view the **Prevention Profiles** page (**Inventory** → **Endpoints** → **Policy Management** → **Prevention** → **Profiles** and is limited to the profile name when viewing the profile in endpoint details. | SOC Tier-1 Analyst: Profile details are typically not needed for basic triage. Although it may be useful for understanding why certain agent features are enabled/disabled on specific endpoints |
| View | View the Agent Profiles menu and read-only access for the Profiles list, details, settings, and view assigned groups. | - SOC Tier-2 Analyst: Understanding agent profiles helps explain agent behavior and capabilities during investigations. Profiles determine what data the agent collects and reports
- SOC Tier-3 Analyst: Full profile visibility needed for advanced analysis and understanding agent configuration. Critical for determining if an agent was properly configured during a case.
- Threat Hunter: Profile visibility helps understand agent capabilities and potential detection gaps. Hunters need to know what telemetry is available from each endpoint.
|
| View/Edit | All view capabilities, plus managing profiles, assigning to groups, and configuring all settings. | Security Engineer: Responsible for profile configuration and optimization. Creates and maintains profiles for different endpoint types. |
**Required and recommended permissions**
Consider adding the following permissions:
| Permission | Permission Level | Reason |
| ------------------------- | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Agent Groups | View | Required. Profiles are assigned to groups. Without group visibility, users cannot understand which endpoints use which profiles. |
| Agent Administrations | View | Required. Must see endpoints to validate profile deployment and verify agent configuration after changes. |
| Agent Prevention Policies | View | Strongly recommended. Profiles define settings within policies. Understanding policy context prevents conflicting configurations. |
| Network Configuration | View | Strongly recommended. Profiles include proxy and network settings. Network configuration visibility ensures profile settings align with network infrastructure. |
| Agent Installations | View | Recommended. Profile settings may depend on the agent version. Installation visibility helps ensure profile compatibility. |
---
# 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-profiles.md?ask=&goal=
```
`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.