Skip to main content
Check the built container image you release for known vulnerabilities in operating system packages and bundled dependencies. You can also check images declared by a repository during a full scan where discovery is enabled. Find results on the Containers page, marked Early access.

Choose what to scan

Scan a built image

  1. Open Containers and select Scan image. If the page prompts you to configure scan types, enable Container Scanning under Full scans → Full Scan Issue Types.
  2. Choose how to provide the image.
  3. Optionally link the image to a repository, then select Scan image. The image page opens and shows the scan status. Once the scan succeeds, review its Vulnerabilities tab.
Use a digest to scan a specific published image. A tag is resolved when the scanner pulls it, so the same tag can refer to a different build on a later scan.

Scan images from a repository

Enable Container Scanning in the repository’s full-scan settings. Where repository image discovery is enabled for your deployment, run a full scan on the branch you want to check.
  1. Open the repository’s Scans → Full Scans. Select the container summary on the scan to open Container coverage.
  2. Check the branch and commit. Expand Image sources to see the files that declare an image, and select View container vulnerabilities to open a completed image check.
  3. Resolve access or coverage gaps before using the scan to verify a fix. A source scan can finish while its image checks are still running.

Which references are discovered

Discovery uses the scanned commit and the repository’s partition scope. A full scan checks up to 20 distinct image and platform pairs. It uses linux/amd64 by default and can use a resolved platform declared in a Dockerfile or Compose file. A scan can report coverage gaps for unreadable files, unresolved build or deployment inputs, or templates that need a renderer such as Helm. A base-image check covers the declared base. Scan the built application image to check packages added during your build.

When to retry

Retry container checks requires permission to start repository scans. It reuses the committed image references from the saved source scan and leaves source scan results and triage decisions intact. It can resolve a mutable tag to a different digest.

Review findings and coverage

Overview

Containers → Overview shows tracked image status and known open package findings across images you can access. A failed rescan leaves previously confirmed risk visible.

Images list

Containers → Images groups tracked images by repository, with a separate group for standalone images. Use the search and filters to open the image you want to review.

Image detail

  • Overview shows scan status, severity, digest, layers when available, and any recommended base-image upgrade. If an attempt failed, use View successful results when a previous successful scan is available.
  • Vulnerabilities groups findings by package. Search by package name or CVE, use Fixable to find upgrades, or open a finding to review its evidence and status. For a cross-image view, select the Containers tab on Issues.
  • Settings lets you manage monitoring and the image’s repository link.
To share vulnerability findings, open Issues → Containers, set your scope, and select Export. The file contains finding records from Issues. Keep the image’s digest and scan status from its detail page when you need to identify the image you reviewed.

What the scanner checks

ZeroPath inventories packages detected in the pulled or uploaded image and matches them against known vulnerabilities. Layer details, when available, help you identify whether a package came from the base image or was added later. For supported base distributions and versions, the scanner can suggest a newer base. When a comparison is available, the reduction count compares OS-package CVEs against that candidate. Rebuild and scan your application image to verify its results.

Monitor and manage images

For a registry image, open its Settings, enter a UTC cron schedule under Monitoring, and select Enable. Use Update to change it or Turn off to stop it. Resubmitting with the schedule field empty leaves any existing monitoring schedule in place.
  • Re-scan now pulls a registry image again. Scheduled runs also pull the image and check it against the available vulnerability data.
  • An uploaded archive is a one-time scan. Upload a new archive to scan a newer build.
  • Delete removes the tracked image and its scan history.

Repository deletion

Deleting a repository stops monitoring for its linked images and clears their saved registry connection links. Their history is removed when the repository is permanently deleted.

Connect a registry

Open Integrations → Registries → Container registries, choose a provider, and save credentials with pull access to the images you need. Saving a connection requires Create Integrations. The same integration also manages private package registries for dependency scans.
Use your Docker Hub username and a read-only access token. Set the namespace for browsing if it differs from your username.
Use a GitHub username, a classic personal access token with read:packages, and the organization or user that owns the packages.
Enter the AWS account ID, region, access key ID, and secret access key. Use an identity with permissions to list and pull the images.
Enter the registry host, GCP project ID, and a service account JSON key with Artifact Registry Reader access.
Enter the login server and pull credentials. You can use a repository-scoped token or a service principal.
Enter the base host, username, and identity token. Repository browsing in the scan dialog requires Artifactory Pro.
Enter the host, username, and token. If the registry does not support repository browsing through /v2/_catalog, enter an image reference manually.
For ZeroPath Cloud, make the registry reachable over the public internet. For self-hosted ZeroPath, the workers can reach permitted private registries on your network. Install local Trivy and Grype database snapshots or configure reachable mirrors if the workers lack internet access.

Scan with a connection

For a built image, choose the connection in Scan image → Connected registry. For a repository image check, select a connection for the image in Container coverage. If several connections match a discovered image, select the one with pull access and retry. For API or CLI submissions, use the connection ID instead of inline registry credentials. The connection must match the image’s registry host.

Registry connection in API responses

A saved connection appears as registryConnection with an id and displayName. The hasRegistryAuth flag also covers inline credentials. The API does not return registry secrets.

Use the CLI or API

See the CLI guide for flags and the API reference for image submission and chunked archive upload. When polling a repository scan through the API, wait for containerCoverage.status to leave DISCOVERING or CHECKING if that field is present. INCOMPLETE means the image checks finished with gaps. The CLI also waits for pending container coverage when running a repository scan.

First scan checklist

  1. Submit the exact image you release, or run a full scan to check its declared images.
  2. Confirm the relevant image scan succeeded and review the open findings.
  3. Set a monitoring schedule for images you want ZeroPath to check again.