> 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/cortex-xsiam/cloud-security/container-registry-scanning/how-container-registry-scanning-works/scan-re-evaluation-process.md).

# Scan re-evaluation process

Understand how Cortex XSIAM re-evaluates container registry scan results.

After the initial scan completes, scan re-evaluation keeps container image findings up to date without requiring the image to be re-pulled or re-scanned.

Because container images are immutable, the software inventory and scan results from the initial scan are retained and reassessed as new information becomes available.

Scan re-evaluation occurs in the following scenarios:

* **New vulnerability intelligence:** When updated vulnerability intelligence becomes available, the stored software inventory of previously scanned images is matched against the updated data, and associated findings and risk scores are updated.
* **Base image changes:** When the base image used to build an image changes, affected images are reassessed to reflect the updated layer information.
* **Updated malware verdicts:** File verdicts for previously scanned images are periodically rechecked. If a file is later classified as malicious, a new finding is generated.

Scan re-evaluation applies to **vulnerability and malware findings**. Secrets and compliance findings are determined during the image scan and are updated only when the image is rescanned, such as after a scanner engine update.

Scan re-evaluation reduces resource-intensive rescans while keeping security assessments current and helping you identify and mitigate emerging risks in images stored in your registries.


---

# 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/cortex-xsiam/cloud-security/container-registry-scanning/how-container-registry-scanning-works/scan-re-evaluation-process.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.