> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/technical-guides/working-with-containers/container-scanning-policy.md).

# Container scanning policy

We perform internal container scans for all of our officially supported images. Please read [the dedicated section in our versioning policy](/versioning-policy.md#support) to find out which images receive official support.

More specifically we schedule a daily job that searches for vulnerabilities using a [Trivy](https://trivy.dev/) scan with standard configuration. We process the resulting findings as follows:

1. We filter out findings that do not have a severity of 'critical', 'high' or 'medium'.
2. We also filter out findings that do not have a status of 'fixed'.
3. For the remaining findings, we look at the finding's severity as dictated by the Trivy scan to determine how urgently we need to fix it. For 'critical' vulnerabilities we publish a patch release within 3 business days. Findings with a severity of 'high' or 'medium' get a fix within 9 and 27 business days respectively.

On top of this we only publish a release if at that point in time our Trivy scan finds no 'critical', 'high' or 'medium' vulnerability that has a 'fixed' status.


---

# 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://docs.elimity.com/technical-guides/working-with-containers/container-scanning-policy.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.