> 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-xdr-5.x/reference-and-developer-docs/role-based-access-control/configuration-permissions/auditing-permissions.md).

# Auditing permissions

Provides access to view audit logs that track all administrative and operational activities within Cortex XDR:

* Management Audit Logs: Track user actions, role modifications, and administrative operations. Go to **Settings** → **Management Audit Logs**.
* Agent Audit Logs: Track endpoint agent activities and related activities. Go to **Settings** → **Agent Audit Logs**.
* XDR Collector Audit Logs: Track XDR collector activities and data collection events. Go to **Settings** → **XDR Collector Audit Logs**.

{% hint style="warning" %}

### Caution

The Auditing module is intentionally restricted to View-only access. Audit logs are immutable records designed to maintain compliance and forensic integrity. They cannot be modified or deleted by any user.
{% endhint %}

| Permission | Description                                                                                                                                                                                                  | Roles Example                                                                                                                                                                                                                     |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None       | No access to any audit logs.                                                                                                                                                                                 | SOC Tier-1 Analyst: No Need for visibility into system activities, unless context is required.                                                                                                                                    |
| View       | <p>Read-only access to all audit log data.</p><p>Auditing is intentionally view-only. Audit logs are immutable records that cannot be modified or deleted to maintain compliance and forensic integrity.</p> | <ul><li>SOC Tier-2 and 3 Analysts, and Threat Hunters: Required for case investigation and understanding event timelines.</li><li>Security Engineer: Required for troubleshooting and validating configuration changes.</li></ul> |

### Required and recommended permissions

Consider adding the following permissions:

| Permission            | Permission Level | Reason                                                                                    |
| --------------------- | ---------------- | ----------------------------------------------------------------------------------------- |
| Cases & Issues        | View             | Provides context for audit events related to cases. Strongly recommended.                 |
| Query Center          | View             | Enables XQL queries against audit datasets. Strongly recommended.                         |
| Dashboards            | Enabled          | View audit-related dashboards for operational visibility. Recommended.                    |
| Agent Administrations | View             | Understand agent-related audit events in the context of endpoint management. Recommended. |
| Host Insights         | View             | Correlate audit events with host-level context and asset information. Recommended.        |


---

# 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-xdr-5.x/reference-and-developer-docs/role-based-access-control/configuration-permissions/auditing-permissions.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.