> 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-assets-permissions/compliance-legacy-permissions.md).

# Compliance (Legacy) permissions

Cloud Compliance (Legacy) under **Inventory** → **Endpoints** → **Cloud Compliance** provides a read-only view of CIS benchmark compliance violations for cloud assets.

{% hint style="info" %}

### Notice

Requires a Cortex XSIAM Enterprise Plus license. If you have a Cloud Posture Security, Cloud Runtime Security, or Cortex XSIAM Premium license, see [Compliance - Cloud permissions](/cortex-xsiam/reference-and-developer-docs/role-based-access-control/cloud-security-and-posture-management-permissions/compliance-cloud-permissions.md).
{% endhint %}

| Permissions | Description                                                              | Roles Example                                                                                                                                                                     |
| ----------- | ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None        | Cannot view the Compliance menu or any related pages.                    | SOC Tier-1 Analyst and Threat Hunter: Compliance monitoring is not part of daily triage/relevant to threat hunting.                                                               |
| View        | Read-only permission to view CIS compliance violations for Cloud assets. | <ul><li>SOC Tier-2 and 3 Analysts: May reference compliance status/data during investigations/advanced analysis.</li><li>Security Engineer: Monitor compliance posture.</li></ul> |

**Required and recommended permissions**

Consider adding the following permissions:

| Permission      | Permission Level | Reason                                                                   |
| --------------- | ---------------- | ------------------------------------------------------------------------ |
| Asset Inventory | View             | Highly recommended to view assets associated with compliance violations. |
| Host Insights   | View             | Highly recommended to view endpoint details for the compliance context.  |
| Dashboards      | Enabled          | Enabled: Recommended to view endpoint details for compliance context.    |
| Query Center    | View             | Recommended to run XQL queries on network data.                          |


---

# 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-assets-permissions/compliance-legacy-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.