> 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/cloud-security-and-posture-management-permissions/application-security-permissions/configurations-application-security-permissions.md).

# Configurations - Application Security permissions

Configure Application Security configuration permissions in Cortex XSIAM.

Application Security Configurations controls access to the Application Security settings under **Settings** → **Configurations** → **Application Security**, which includes the following:

* Application Configuration: Controls SLA target settings (Critical, High, Medium, Low severity target days and approaching SLA threshold), and the auto-refresh toggle for related application assets.
* AppSec Issues Configuration: Controls whether SBOM (Software Bill of Materials) findings are treated as new vulnerabilities. When enabled, all detected SBOM findings are treated as new vulnerabilities. When disabled, the baseline for identifying new SBOM vulnerabilities starts with the next scan, excluding previously identified findings.

{% hint style="info" %}

### License

Requires the Application Security add-on in addition to Cloud Posture Security, Cloud Runtime Security, or Cortex XSIAM Premium license.
{% endhint %}

| Permission | Description                                                                 | Roles Example                                                                                                                                                                                      |
| ---------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None       | No access to Application Security configuration pages.                      | <ul><li>SOC Tier-1, 2, and 3 Analysts: AppSec configuration is not part of the primary SOC workflow.</li><li>Threat Hunter: AppSec configuration is outside the scope of threat hunting.</li></ul> |
| View/Edit  | Full access to view and modify Application Security configuration settings. | Security Engineer: May need to configure SLA targets and SBOM behavior as part of AppSec posture management.                                                                                       |

**Required and recommended permissions**

To understand the impact of modifying SLA targets and SBOM baselines, administrators should have visibility into the actual AppSec issues queues and the related application assets these settings affect.

| Permission                  | Permission Level | Reason                                                                                                                                                                                                                                                                    |
| --------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Application Security Issues | View             | Strongly Recommended. Configurations made on this page directly dictate how SBOM findings appear and how SLA deadlines are calculated. Access to the Issues queue allows administrators to verify that their configuration changes produce the desired tracking behavior. |
| Asset Inventory             | View             | Recommended. The configurations include an auto-refresh toggle for related application assets. Asset Inventory visibility helps administrators understand which assets are being affected by this setting.                                                                |


---

# 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-xsiam/reference-and-developer-docs/role-based-access-control/cloud-security-and-posture-management-permissions/application-security-permissions/configurations-application-security-permissions.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.