> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/set-up-insights/set-up-insights-image-scanning.md).

# Set up Insights: image scanning

To determine the risk factors and prioritize your Code, Open Source, and Container issues, you must scan your container images using [Snyk Container](/scan-fix-and-prevent/scan-with-snyk/snyk-container.md).

The container image is at the center of the application model that powers Snyk Enterprise. A container image includes your source code and dependencies, and it is deployed to your running environment, enabling Snyk to use the container image to bridge the development and deployment states.\
\
Snyk will identify any deployed container images using the [Kubernetes Connector](/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/set-up-insights/set-up-insights-kubernetes-connector.md) and compare the deployed container images to the list of scanned images you have scanned using [Snyk Container](/scan-fix-and-prevent/scan-with-snyk/snyk-container.md).

{% hint style="info" %}
Snyk recommends that you scan each image using at least one of the Snyk Container integrations.
{% endhint %}

## Snyk Container scanning with the CLI

To ensure the image names match, specify the full name of the image as referenced in your Kubernetes deployment.

Example:

`snyk container monitor gcr.io/my-company/my-image:latest`

For details, see [Snyk CLI for container security](/developer-tools/snyk-cli/snyk-cli/scan-and-maintain-projects-using-the-cli/snyk-cli-for-snyk-container.md).

## Snyk Container registry scanning

The names will match if you are importing images to Snyk from the same container registry that you are referencing in your Kubernetes deployments.

For details, see [Snyk Container - Integrations](/scan-fix-and-prevent/scan-with-snyk/snyk-container/container-registry-integrations.md).

## Snyk Container scanning with Kubernetes integration

The names of the container images will match because the deployed image is scanned by Snyk and created as a Project.

{% hint style="info" %}
To ensure you have set up your Kubernetes Connector properly, navigate to the **Set up Insights** tab on the **Issues** page and check the **Image coverage** section to view the data Insights has access to.
{% endhint %}

For details, see [Kubernetes integration](/scan-fix-and-prevent/scan-with-snyk/snyk-container/kubernetes-integration.md).


---

# 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.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/set-up-insights/set-up-insights-image-scanning.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.