tigergate scan --type image --image <ref> step to your pipeline so no tag reaches the registry unscanned. Image scanning is the same scan command used for code, with --type image. The CLI ships only as the tigergate/tigergate-cli image (entrypoint tigergate).
Prerequisites
- A connected registry — TigerGate needs read access to pull the image.
- A
ci-cd-quality-gateAPI key in your CI’s secret store (the same key used for code scans — see API keys).
CI snippets
- GitHub Actions
- GitLab CI
- Bitbucket Pipelines
- Jenkins
--type image pulls the image from the registry directly, so no -v repo mount is needed (unlike code scans). The gate runs by default; add --quality-gate=false for report-only. A non-zero exit fails the step.Quality gate
The image scan runs through the same CI quality gate as code scans. By default the build fails oncritical or high findings (--fail-on critical,high); add --quality-gate=false to upload results without failing the build.
Override the failing severities per run:
Scanning local images (without push)
You don’t have to push to a registry first —--image scans a locally built image by reference. Share the Docker socket so the CLI container can see it:
SBOM
Image SBOMs are produced by TigerGate’s container scans of a connected registry, not by the CI CLI image scan. Each scanned image gets a CycloneDX bill of materials, viewable and downloadable (CycloneDX JSON) under Container Security → the image → SBOM tab.