> 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/configuration-permissions/network-scanners-permissions.md).

# Network Scanners permissions

Located under Settings → Configurations → Network Scanning, this permission allows administrators to set up scan definitions, manage credentials for authenticated scans, configure targets, and view results.

Requires either the ASM and the Exposure Management add-ons, or a Cortex XSIAM Premium license with the Exposure Management add-on.

For more information, see [Cortex Network Scanner](/cortex-xsiam/detect-investigate-and-respond-to-threats/exposure-management/cortex-network-scanner.md).

While configured under Integrations, Network Scanners serve as the active discovery engine for the broader vulnerability lifecycle. Data generated here directly populates the Vulnerability Management and Exposure Management modules.

| Permission | Description                                                                                               | Role Example                                                                                               |
| ---------- | --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| None       | Users cannot access the Network Scanners page.                                                            | SOC Tier-1 and 2 Analysts: No scanning responsibilities.                                                   |
| View       | Users can view existing scanner configurations and scan results, but cannot create, run, or modify scans. | <ul><li>SOC Tier-3 Analyst: Review scan configurations.</li><li>Threat Hunter: Review scan data.</li></ul> |
| View/Edit  | Full control to create, configure, run, and delete network scan configurations                            | Security Engineer: Configure vulnerability scanning.                                                       |

#### Required and recommended permissions

Vulnerability scanning is deeply integrated with asset discovery and infrastructure. Consider adding the following permissions:

| Permission                                   | Permission Level  | Reason                                                                                                        |
| -------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------- |
| Vulnerability Testing (under Attack Surface) | View or View/Edit | Core permission to access Network Scanners pages. Required.                                                   |
| Credentials                                  | View/Edit         | Strongly recommended to manage scan authentication credentials used for authenticated vulnerability scanning. |
| Broker Service                               | View/Edit         | Required if using Broker VM as the scanning infrastructure.                                                   |
| Cases & Issues                               | View              | Recommended to view vulnerability-related cases and issues generated from scan results.                       |
| Query Center                                 | View              | Recommended to query scan results and vulnerability data via XQL.                                             |


---

# 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/configuration-permissions/network-scanners-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.