> 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/references/reference-a-artifact-attestation-security-model.md).

# Reference A: Artifact attestation security model

This technical reference details the trust, signing, and detection models governing Cortex Cloud artifact attestation.

## Trust model

Attestation separates validation into three distinct verification checks to avoid overstating what a signature proves.

<br>

| Verification type        | Question answered                                                 |
| ------------------------ | ----------------------------------------------------------------- |
| Signature Verification   | Is this artifact signed by a key the organization trusts?         |
| Provenance Verification  | Was this artifact built by the official pipeline?                 |
| Attestation Verification | Does the internal payload meet organizational security standards? |

#### Key management and trust anchors

* Public key registry: Your public Cosign keys serve as the trust anchor. Private keys remain exclusively on your CI/CD runners
* Registration scope: Registering a key declares trust within Cortex Cloud; it does not automatically sign artifacts. The pipeline must sign with the matching private key for any artifact to verify against it

#### Rotation operational trade-offs

* Blast radius reduction: Keys carry a configurable rotation interval (set per key, not per tenant) to limit exposure over time
* Coordinated windows: Key updates must occur in the console and CI/CD pipelines simultaneously. Artifacts signed with old keys stop verifying upon rotation
* Operational scale: Maintenance scales directly with key count (such as 20 keys with 90-day intervals require 80 coordinated change windows annually)
* Setting lock-in: Updating a key's interval requires removing the existing key file and deploying new key material
* Monitoring cadence: Treat the registry as pull-only and assign internal owners to review derived rotation statuses

## Signing model

#### Pipeline sequence constraints

The Cortex CLI signs images strictly by digest, requiring the image to exist in the registry prior to signing. Pipelines must execute in this exact sequence:

1. Build the container image.
2. Push the image to the registry.
3. Capture the image digest.
4. Scan the image with cortexcli image scan.
5. Sign the digest reference with cortex-cli attest sign.\
   Note: A pipeline that signs without the scan step raises APPSEC-ATTEST-2. A pipeline with no signing step raises APPSEC-ATTEST-5.

#### Registry outputs

A completed signing process creates three co-located registry entries tagged with the same image digest:

* Container Image
* Signature Entry
* Attestation Predicate

## Detection model

Cortex Cloud evaluates compliance using two independent, unsynchronized scans running twice daily.

<br>

| Scan type                | Insight type | Mechanism                     | Question answered                                                                                                      |
| ------------------------ | ------------ | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Periodic Scan (CI-Match) | Static       | Analyzes pipeline definitions | Does the pipeline sign, and does it scan the image before signing?                                                     |
| Attestation Worker Scan  | Dynamic      | Analyzes runtime build logs   | Did the signing operation succeed during execution, or was it refused because of a key problem or a failed scan check? |

#### Attestation detection rules

11 attestation rules are built-in and read-only. At this release, three produce findings; the remaining eight are listed but no scan produces findings for them.

| Rule ID          | Severity | Rule name                                                                   | Produces findings | Insight type                      |
| ---------------- | -------- | --------------------------------------------------------------------------- | ----------------- | --------------------------------- |
| APPSEC-ATTEST-1  | Critical | Artifact signing operation failure detected in pipeline                     | Yes               | Dynamic — attestation worker scan |
| APPSEC-ATTEST-2  | High     | Pipeline signs an image without scanning it                                 | Yes               | Static — periodic scan (CI-match) |
| APPSEC-ATTEST-5  | High     | Pipeline is pushing unsigned artifact to registry                           | Yes               | Static — periodic scan (CI-match) |
| APPSEC-ATTEST-3  | High     | Image signature verification failed due to untrusted public key in pipeline | No                | —                                 |
| APPSEC-ATTEST-4  | Critical | Image signature verification failed due to invalid signature in pipeline    | No                | —                                 |
| APPSEC-ATTEST-6  | Critical | Invalid artifact signature detected in registry                             | No                | —                                 |
| APPSEC-ATTEST-7  | Medium   | Unsigned image detected in registry                                         | No                | —                                 |
| APPSEC-ATTEST-8  | High     | Image signed by an untrusted public key found                               | No                | —                                 |
| APPSEC-ATTEST-9  | Critical | Image signed by a recently removed trusted public key found                 | No                | —                                 |
| APPSEC-ATTEST-10 | Medium   | Expired signing key found                                                   | No                | —                                 |
| APPSEC-ATTEST-11 | Low      | Key has not been rotated within the required period                         | No                | —                                 |

APPSEC-ATTEST-2 and APPSEC-ATTEST-5 are mutually exclusive on a pipeline: a pipeline with no signing step raises APPSEC-ATTEST-5; a pipeline that signs but has no image-scan step raises APPSEC-ATTEST-2; a pipeline that scans and signs raises neither.

#### Enforcement scope

* Report-only visibility: Cortex Cloud identifies and surfaces non-compliant pipelines across the tenant, but does not block builds or deployments
* Pipeline gates: Active enforcement requires configuring individual CI/CD pipelines to fail the build step upon a signing error
* Governance limits: Cortex Cloud detects whether a pipeline has a signing step and a scan step. It cannot detect whether either step fails the build when it fails. Track gate adoption externally through pipeline templates or change records


---

# 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/references/reference-a-artifact-attestation-security-model.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.
