> 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/application-security/settings/about-settings.md).

# About Settings

The settings within the Configurations menu provide security administrators with the operational controls to establish baselines for Application Security and Supply Chain Security.

These tenant and repository-level settings define how Cortex Cloud handles security data, allowing you to:

* Establish scanning baselines to determine exactly what gets scanned
* Set remediation SLAs based on vulnerability severity
* Manage findings by configuring retention windows and backlog classifications
* Verify signatures by registering trusted Cosign public keys for build artifact attestation

**Scope**: Configurations determine how findings are reported, classified, and tracked, but they do not run scans or block workflows themselves. Enforcement—such as blocking a pull request or generating an issue—is handled separately by [Application Security policies](https://cortex-docs.paloaltonetworks.com/application-security/application-security-posture-management-aspm/unified-application-security-policies.md).

### Prerequisites

* A Cortex Cloud base license with the Application Security add-on.
* At least one onboarded version control integration, so that scan configuration has repositories to govern

### Available settings

Navigate to **Settings** > **Configurations**. Settings are organized by context.

#### **Application Security**

Scroll down to **Application Security** to access:

* **Application Configuration**: Set auto-refresh behaviors, issue target SLAs, and approaching SLA thresholds. See [Configure application settings](vscode-webview://0ef8dspgbi87jv3f6acifog39jqb5muuji0dego93o5lchfbr93t/index.html?id=93230be5-4295-47e1-a49d-7cd5d18d6714\&parentId=1\&origin=f4a9d72e-d48e-42a9-b318-86d290ea1e3f\&swVersion=6\&extensionId=PaloAltoNetworks.cortex-ai\&platform=electron\&vscode-resource-base-authority=vscode-resource.vscode-cdn.net\&parentOrigin=vscode-file%3A%2F%2Fvscode-app\&mountId=b244976f-1976-4a59-a58d-2562a7393176#configure-application-settings).
* **Issues and Finding Configurations**: Manage SBOM finding classification and PR and CI finding retention windows. See [Configure issues and findings settings](vscode-webview://0ef8dspgbi87jv3f6acifog39jqb5muuji0dego93o5lchfbr93t/index.html?id=93230be5-4295-47e1-a49d-7cd5d18d6714\&parentId=1\&origin=f4a9d72e-d48e-42a9-b318-86d290ea1e3f\&swVersion=6\&extensionId=PaloAltoNetworks.cortex-ai\&platform=electron\&vscode-resource-base-authority=vscode-resource.vscode-cdn.net\&parentOrigin=vscode-file%3A%2F%2Fvscode-app\&mountId=b244976f-1976-4a59-a58d-2562a7393176#configure-issues-and-findings-settings).
* **Global Scan Configuration**: Establish your tenant scan baseline. See [Configure scan settings](vscode-webview://0ef8dspgbi87jv3f6acifog39jqb5muuji0dego93o5lchfbr93t/index.html?id=93230be5-4295-47e1-a49d-7cd5d18d6714\&parentId=1\&origin=f4a9d72e-d48e-42a9-b318-86d290ea1e3f\&swVersion=6\&extensionId=PaloAltoNetworks.cortex-ai\&platform=electron\&vscode-resource-base-authority=vscode-resource.vscode-cdn.net\&parentOrigin=vscode-file%3A%2F%2Fvscode-app\&mountId=b244976f-1976-4a59-a58d-2562a7393176#configure-scan-settings).

**Note**: Custom scan settings for individual repositories are not in this group. They are set on each repository, from **Data Sources & Integrations**. See [Configure custom repository scan settings](vscode-webview://0ef8dspgbi87jv3f6acifog39jqb5muuji0dego93o5lchfbr93t/index.html?id=93230be5-4295-47e1-a49d-7cd5d18d6714\&parentId=1\&origin=f4a9d72e-d48e-42a9-b318-86d290ea1e3f\&swVersion=6\&extensionId=PaloAltoNetworks.cortex-ai\&platform=electron\&vscode-resource-base-authority=vscode-resource.vscode-cdn.net\&parentOrigin=vscode-file%3A%2F%2Fvscode-app\&mountId=b244976f-1976-4a59-a58d-2562a7393176#configure-custom-repository-scan-settings).

#### **Supply Chain Security**

**Attestation**: Register, rotate, and delete trusted Cosign public keys. See [Supply Chain Security settings](vscode-webview://0ef8dspgbi87jv3f6acifog39jqb5muuji0dego93o5lchfbr93t/index.html?id=93230be5-4295-47e1-a49d-7cd5d18d6714\&parentId=1\&origin=f4a9d72e-d48e-42a9-b318-86d290ea1e3f\&swVersion=6\&extensionId=PaloAltoNetworks.cortex-ai\&platform=electron\&vscode-resource-base-authority=vscode-resource.vscode-cdn.net\&parentOrigin=vscode-file%3A%2F%2Fvscode-app\&mountId=b244976f-1976-4a59-a58d-2562a7393176#supply-chain-security-settings).

### Who uses these settings

* AppSec Admin (governance). Decides SLA targets, whether pre-existing dependency vulnerabilities enter as new work, and the tenant scan baseline. Each decision changes what every dashboard and SLA report shows
* DevSecOps engineer (operations). Applies custom scan settings to individual repositories, registers signing keys that pipelines use, and automates key management through the API

### Roles and access

Access to Application Security settings and tasks requires the following specific roles and permissions:

* **Open the Application Security settings group**: Requires an administrator role or the AppSec Admin role
* **View Global Scan Configuration**: Requires the Asset Inventory permission.
* E**dit the tenant scan baseline**: Requires the Application Security Global Scan View/Edit permission; without it, the page is read-only
* **Open and save a repository's Scan Configuration**: Requires the Asset Inventory permission and access to Data Sources (this includes switching the repository between Global and Custom)
* **Attestation**: Register, rotate, and delete attestation public keys - Requires the AppSec Admin role

IMPORTANT: Any user with the Asset Inventory permission can move a repository off the tenant baseline by switching the repository to Custom.

### <br>

<br>


---

# 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/application-security/settings/about-settings.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.
