> 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/software-supply-chain-security/artifact-attestation.md).

# Artifact attestation

Artifact attestation delivers continuous, observable supply chain security by cryptographically proving your container images were built by your pipeline and reached your registry unmodified. By enforcing signed build provenance, Cortex Cloud automatically identifies unverified or compromised artifacts, allowing you to instantly detect and remediate pipelines failing to meet integrity standards.

Currently, only container image artifacts are supported.

#### Core value and deliverables

* **End-to-end visibility**: Continuous tracking of build signatures and provenance across all pipelines, with automatic flagging of non-compliant artifacts
* **Regulatory compliance**: Satisfies mandatory supply chain frameworks, fulfilling requirements for **SLSA Level 2+**, **NIST SSDF (SP 800-218)**, and **US Executive Order 14028**

## Prerequisites

Artifact attestation requires both universal baseline prerequisites and specific requirements for your chosen deployment channel.

#### Universal prerequisites

| Prerequisite                               | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cortex Cloud license                       | An active Cortex Cloud license and an Application Security add-on                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| Cortex CLI                                 | Required to sign and verify. The pipeline downloads the Cortex CLI at build time. Refer to [Cortex CLI](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cli/cortex-cli.md) for download procedure and installation options                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| Cortex Cloud API API Key, ID, and Base URL | Required by the pipeline to download the Cortex CLI and to authenticate to the tenant. Generate and retrieve all required values from **Settings > Configurations > API Keys** in the Cortex Cloud console: a **Standard** API key, (with the CLI and AppSec Admin roles assigned) , the **API Key ID**, and copy the API Base URL, in the form <https://api-\\>\<TENANT\_FQDN>. See [https://github.com/PaloAltoNetworks/cortex-documentation/tree/gitbook-release/guides/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/manage-api-keys.md](https://github.com/PaloAltoNetworks/cortex-documentation/tree/gitbook-release/guides/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/manage-api-keys.md "mention") |
| RBAC: AppSec Admin                         | Required to register a public key in the tenant or through the API                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| Cosign                                     | Required to generate the key pair. Cosign is the open-source signing tool from the [Sigstore](https://www.sigstore.dev/) project. See the [Cosign installation instructions](https://docs.sigstore.dev/cosign/system_config/installation/). Generate the pair with `cosign generate-key-pair` — the command writes a private key and a public key file, and only the public key file is uploaded                                                                                                                                                                                                                                                                                                                                                                                        |
| A supported key type                       | Cortex Cloud accepts Cosign **ED25519** and **ECDSA** public keys. ECDSA keys must use the **P-256** curve                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| A conforming key file                      | When uploading in the tenant, the public key file must use the `.pub` extension and must be 4 KB or smaller. The cosign `generate-key-pair` command produces a conforming file by default                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| Your organizational rotation interval      | <p>Registration requires a rotation period, and the interval is a policy decision rather than a per-key preference. See <a data-mention href="https://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/artifact-attestation/references/reference-a-artifact-attestation-security-model.md">/pages/bSO0N9ienmTYndMapoVK</a></p><p><br></p>                                                                                                                                                                                                                                                                                                                                                                                                           |

#### Additional prerequisites for signing in a pipeline

| Prerequisite         | Description                                                                                                 |
| -------------------- | ----------------------------------------------------------------------------------------------------------- |
| A container registry | The pipeline must be able to push images and write signature artifacts alongside them                       |
| CI/CD onboarding     | The pipeline must be onboarded to Cortex Cloud for attestation detections to be raised against the pipeline |

#### Additional prerequisites for managing keys via the API

| Prerequisite      | Description                                                                                                              |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Read permissions  | Any one of `asset_management` or `ci_tool_view`, for validate, check-existence, list, get, and pipeline-query operations |
| Write permissions | Any one of `asset_management_action` or `ci_tool_edit`, for add, update, and delete operations                           |

**Note**: A 403 on any step in this manual is a permissions failure, not a malformed request.

## Core achievements

Artifact attestation is structured proactive-first — establishing signing precedes detecting its absence.

* **Provenance at build time (proactive)**: The pipeline signs each artifact by digest and publishes a SLSA provenance statement, producing tamper-evident build evidence at the earliest point the artifact exists
* **Trust anchoring (proactive)**: Registering the public key declares which signers the organization recognizes, so a valid signature from an unrecognized key is not mistaken for a trusted one
* **Signing-gap detection (reactive)**: Cortex Cloud identifies pipelines that push artifacts to a registry without signing them
* **Signing-failure detection (reactive)**: Cortex Cloud identifies pipelines where a signing operation was attempted and failed, a state that otherwise passes silently in a green build
* **Unscanned-signing detection (reactive)**: Cortex Cloud identifies pipelines that sign images without scanning them first, so the signature carries no scan evidence

## The trust model

Cortex Cloud artifact attestation provides supply chain security by cryptographically proving that container images were built by an authorized pipeline and reached the registry unmodified. It operates on two primary mechanisms:

* **Proactive signing and trust anchoring**: Pipelines sign container images by digest upon registry push, anchored by public keys registered in Cortex Cloud
* **Reactive detection**: Automated static and dynamic scans continuously monitor pipelines to flag unsigned image pushes, images signed without a prior scan, or runtime signing failures

For a detailed explanation of the underlying trust model, refer to [Reference A: Artifact attestation security model](https://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/artifact-attestation/references/reference-a-artifact-attestation-security-model.md).

## Attestation workflows

Deploy end-to-end artifact attestation by cryptographically proving container image integrity from build to deployment. Because feature support varies by task, executing a complete workflow requires a **multi-interface approach** using the Cortex tenant (UI), the Attestation API (programmatic), and CortexCLI/Cosign (CLI). See [Artifact attestation workflow](https://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/artifact-attestation/artifact-attestation-workflow.md).

## Monitoring and troubleshooting

To run regular health checks, troubleshoot pipeline signing issues, and monitor key expiration states, see [Reference C: Monitoring and troubleshooting guide](https://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/artifact-attestation/references/reference-c-monitoring-and-troubleshooting-guide.md).

## Where to go next

* [Artifact attestation workflow user guide](https://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/artifact-attestation/artifact-attestation-workflow.md): Generate a key pair, configure a pipeline to sign, sign and verify with the Cortex CLI, confirm the registry artifacts, and review the resulting detections
* [Register public keys](https://cortex-docs.paloaltonetworks.com/application-security/settings/supply-chain-security-settings.md): Register, rotate, and delete keys
* [Attestation settings](https://cortex-docs.paloaltonetworks.com/application-security/settings/supply-chain-security-settings.md): Manage attestation signing keys and audit signing adoption programmatically

For detailed artifact attestation information, see [References](https://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/artifact-attestation/references.md).


---

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