Insights setup: 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.

The container image is at the center of the application model powering Insights. A container image includes your source code and dependencies, and it is deployed to your running environment, enabling Insights to use the container image to bridge the development and deployment states together. Insights will identify any deployed container images using the Kubernetes Connector in the previous setup step and compare them to the list of scanned images you have scanned using Snyk Container.

We recommend that you scan each image using at least one of the Snyk Container integrations.

Snyk Container Scanning

CLI

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

For example: $ snyk container monitor gcr.io/my-company/my-image:latest

Container Registry

If you are importing images to Snyk from the same container registry that you are referencing in your kubernetes deployments, the names will match.

Kubernetes Integration

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

To make sure you have set up your Kubernetes connector properly, navigate to the Data tab on the Insights page and check the Image coverage section to view the data that Insights has access to.