> 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/appsec-rules/ci-cd-security/artifact-integrity-validation/appsec-attest-2.md).

# Signed image without a prior build scan found

## Rule Details

|                        |                                                               |
| ---------------------- | ------------------------------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC-ATTEST-2                                               |
| Category - Subcategory | Artifact Integrity Validation - Attestation Lifecycle Failure |
| Severity               | HIGH                                                          |

## Impact

An image was signed via `cortex-cli attest sign` without a corresponding build-image asset in the Unified Asset Inventory (UAI). A build-image asset is created when a Cortex-CLI scan is performed on the image. Signing without a prior scan means the signature cannot be correlated to a build-image asset, breaking the scan-to-signature provenance chain and allowing an unscanned (and therefore unverified) artifact to carry a trusted signature.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/artifact-integrity-validation/appsec-attest-2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.