> For the complete documentation index, see [llms.txt](https://docs.aquilax.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquilax.ai/user-manual/scanners/container-scanning.md). # Container Scanning Container Scanning is the process of examining container images for security vulnerabilities, misconfigurations, or malware. As containers become more prevalent in modern software development, ensuring their security is paramount to protecting applications in production.\\ AquilaX AI’s Container Scanning uses cutting-edge ML algorithms to analyze both the base images and custom layers of your containers. This scanning ensures that only secure, compliant, and optimized images are deployed, reducing the attack surface of containerized applications. **Why Container Scanning Matters:** • Secure your containerized applications. • Detect vulnerabilities in container layers. • Ensure compliance and reduce production risks. --- # 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.aquilax.ai/user-manual/scanners/container-scanning.md?ask=&goal= ``` `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.