> 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-xpanse/reference/management-audit-logs.md).

# Management Audit Logs

View and export management audit logs in Cortex Xpanse.

Management audit logs display a log of all administrative user interactions within Cortex Xpanse. The logs are sorted by date and list which users interacted in what way with system objects, and associated data. Cortex Xpanse stores management audit logs for 365 days.

{% hint style="info" %}

### Note

The audit logs do not include actions performed in the Alert War Room. These actions are documented in the Alert War Room.
{% endhint %}

Xpanse enables you to monitor administrative activity through management audit log notifications. See [Configure Notification Forwarding](/cortex-xpanse/onboard-and-configure-cortex-xpanse/post-deployment-steps/log-forwarding.md#UUID-534f996e-cdb3-cfeb-e61d-17bc2f4434a9) to forward your management audit logs to an email distribution list, Syslog server, or Slack channel.

To view management audit logs, navigate to Settings → **Management Audit Logs**. Use the filter to narrow your results based on specific fields. You can also save your filters for later use.

To export the management audit logs as a **`.tsv`** file, click the **Export to file** button.

The table below describes the management audit log fields.

| Field       | Description                                                                                                                                                                                                           |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Description | Descriptive summary of the administrative action.                                                                                                                                                                     |
| Host Name   | Name of any relevant affected hosts.                                                                                                                                                                                  |
| Result      | The result of the action: **Success**, **Fail**, or **N/A**                                                                                                                                                           |
| Severity    | <p>Severity associated with the log:</p><ul><li><strong>Critical</strong></li><li><strong>High</strong></li><li><strong>Medium</strong></li><li><strong>Low</strong></li><li><strong>Informational</strong></li></ul> |
| Subtype     | Subcategory of action.                                                                                                                                                                                                |
| Timestamp   | Time and date of the action.                                                                                                                                                                                          |
| Type        | Type of action logged.                                                                                                                                                                                                |
| User Name   | Name of the user who performed the action.                                                                                                                                                                            |


---

# 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-xpanse/reference/management-audit-logs.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.
