> 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/exposure-and-vulnerability-management-permissions/exposure-management-permissions.md).

# Exposure Management permissions

Exposure Management permissions provide a risk-based approach to prioritizing and remediating security exposures across your organization. Exposure Management ties together vulnerability data, attack-surface context, and security-control posture to provide actionable risk prioritization.

{% hint style="info" %}

### Notice

Requires the Exposure Management license. To enable Exposure Management, contact Customer Support.
{% endhint %}

The permissions control access to Security Controls (tracking the effectiveness of compensating controls against vulnerabilities) and Effectiveness Rules (configurable rules defining how control effectiveness is measured)

For more information, see [Exposure Management](/cortex-xsiam/detect-investigate-and-respond-to-threats/exposure-management.md).

| Permission | Description                                                                                                      | Roles Example                                                                                                                                                                                                                                                                            |
| ---------- | ---------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None       | No access to Exposure Management features; Security Controls hidden.                                             |                                                                                                                                                                                                                                                                                          |
| View       | Read-only access to Exposure Management, such as Security Controls, effectiveness data, and exposure dashboards. | <ul><li>SOC Tier 1, 2, and 3 Analysts: Needs visibility into exposures and vulnerabilities for initial triage; should not modify rules or policies.</li><li>Threat Hunter: Needs read access for threat research and correlation; typically does not modify rules or policies.</li></ul> |
| View/Edit  | Full access to manage Exposure Management, including Security Controls.                                          | Security Engineer: Configures exposure remediation workflows.                                                                                                                                                                                                                            |

**Required and recommended permissions**

To effectively prioritize risk and assess control effectiveness, administrators and analysts require deep visibility into the underlying cases, vulnerabilities, and asset inventories. Consider adding the following permissions:

| Permission               | Permission Level  | Reason                                                                                                                                                                                                                                                                                      |
| ------------------------ | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cases & Issues           | View or View/Edit | <ul><li>View: Strongly recommended to view issues linked to exposure findings. Without this, users can see security controls, but cannot see the issues that triggered them.</li><li>View/Edit: Recommended to actively triage and respond to issues linked to exposure findings.</li></ul> |
| Vulnerability Management | View or View/Edit | <ul><li>View: Required for the Effectiveness Rules view and vulnerability issue integration.</li><li>View/Edit: Strongly recommended for control effectiveness overrides.</li></ul>                                                                                                         |
| Attack Surface Rules     | View              | Recommended. Provides context on attack surface rules that feed into exposure data. Useful for understanding the source of exposure findings.                                                                                                                                               |
| Asset Inventory          | View              | Recommended to access the broader asset inventory. Provides context on the assets affected by security control gaps.                                                                                                                                                                        |


---

# 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/exposure-and-vulnerability-management-permissions/exposure-management-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.