> 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/supply-chain-security-settings.md).

# Supply Chain Security settings

Supply Chain Security settings currently contain **Attestation** settings. Use the Attestation settings page to manage the public key registry—which includes registering, rotating, and removing keys, as well as setting rotation policies—and to view all Cosign public keys Cortex Cloud uses to verify signed container images.

The registry only declares which signers Cortex Cloud trusts; it does not perform the signing itself. Signing must occur within your CI/CD pipeline using a private key that matches a registered public key.

Consequently, signature results appear directly on the artifact rather than in the registry. To review a signature, open a container asset and check the Signature status and Used predicates values under the Trust Score factors.

For more details on accessing these values and understanding how signing contributes to the score, refer to Artifact Trust Score.

## Prerequisites

Before you begin:

* Fulfill all requirements in [About Settings](https://cortex-docs.paloaltonetworks.com/application-security/settings/about-settings.md#prerequisites)
* **Ensure you have a conforming Cosign public key file** (ED25519 or ECDSA P-256 curve, .pub extension, 4 KB or smaller)
* **Required role**: **AppSec Admin**. This role can configure all attestation settings, including registering, updating, rotating, and deleting public keys

## Register a public key

Follow these steps to register a new public key and declare a trusted signer in Cortex Cloud:

1. Navigate to **Settings > Configuration > Supply Chain Security > Attestation**.
2. Click **+ Register public key** (or click the registration action on the empty state if no keys are registered yet).
3. **Step 1: Upload key**. Complete the key identity and rotation fields:
   * **Key name**: Enter a unique handle for the key (e.g., prod-build). Choose a name representing the build environment; this name is permanent and cannot be modified later
   * **Upload public key**: Drag and drop or browse to upload your .pub file
   * **Rotation**: Select how long the key remains valid before rotation is due (preset options of 30, 60, or 90 days, or choose Custom to set an explicit date)
4. **Advance to Step 2: Predicates**.\
   Predicates are the payload of an attestation — the domain-specific metadata that describes the artifact. SLSA provenance records how the artifact was built and signed, and is always enabled. You cannot disable SLSA provenance.
5. Click **Submit**.

**Result:** Cortex Cloud confirms with Key created successfully and the new key appears in the Public key registry. Verify that the key status is Active.

**Note**: The private key is never uploaded to Cortex Cloud. Keep the private key on your CI/CD runner and protect it with the same controls you apply to any other build secret.

#### Confirm registration works end to end

A row in the registry proves that a record was stored. It does not prove that the key you uploaded is the public half of the key pair your pipeline signs with. For example, a stale key from an earlier rotation, or the public half of a different pair, produces the same success message and the same registry row as a correct upload.

## Understand the public key registry

The Public key registry table lists every registered key with its rotation state. Use the registry to identify keys approaching or past their rotation date before verification failures appear in your pipelines.

* Navigate to **Settings > Configurations > Attestations**.

Each row reports the key name, its rotation policy, when the next rotation is due, when the key was created and by whom, the expiration date, and the current status.

## Rotate a key

Rotate a key to swap out the underlying public key material while keeping the registered key name identical, preventing any breaks in pipelines referencing that key.

1. Navigate to **Settings > Configurations > Supply Chain Security > Attestation**.
2. Right-click and select **Edit**.
3. Remove the current key file.\
   **Note**: The rotation setting remains locked and cannot be edited until you remove the old file.
4. Upload the new public key file.
5. Set the rotation period.\
   **Note**: Ensure you upload the file before setting the period, as setting it beforehand will discard your selection.
6. Click **Submit**.
7. **Deploy the private key**: Update the corresponding private key on your CI/CD runner during the same change window to ensure continuous verification.

## Delete a public key

Deleting a key permanently withdraws trust from every artifact signed by that key. Identify all affected container images from your build records and plan to re-sign them if they must remain trusted.

1. Navigate to **Settings > Configurations > Attestations**.
2. Right-click and select **Delete** .
3. Read the warning details in the dialog explaining that historical audit logs are retained but future verification will fail.
4. Click to confirm the deletion.


---

# 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/supply-chain-security-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.
