InfrastructureLiveFrom Pro ($199/mo)

Container Security

Crate (Container) checks a container image for known CVEs in its OS and language packages. Give it an image reference, add a registry credential if the image is private, and the findings land in the same dashboard as your code and application findings.

Detection Coverage

What Container Security scans

OS Package CVEs

Known vulnerabilities in the operating system packages inside the image.

Language Package CVEs

Known vulnerabilities in the application libraries bundled in the image.

Base Image Vulnerabilities

CVEs that come from the base image, whatever your application layer contains.

Fix Versions

Each CVE shows the affected package and the fixed version when one exists.

Private Registries

Saved credentials for Docker Hub, AWS ECR, Google GCR, Azure ACR or another registry.

Honest Coverage

If the layer scanner is unavailable, the result is marked Partial instead of reported as clean.

How it works

Image reference to findings

  1. 1

    Enter an image reference

    For example nginx:1.27 or ghcr.io/org/app:v1.2. Public images need no credentials.

  2. 2

    Add a registry credential

    For private images, save a registry credential in Settings and select it for the scan.

  3. 3

    Package analysis

    The OS and language packages in the image are checked for known CVEs. No agent or Docker daemon is needed on your side.

  4. 4

    Findings in one place

    Each CVE is recorded with its severity, affected package and fix version, next to the findings from your other engines.

container-scan-result.jsonJSON
{
  "image": "myapp:v2.1.0",
  "cves": [
    {
      "id": "CVE-2022-3602",
      "severity": "high",
      "package": "openssl",
      "installed": "3.0.2",
      "fixed": "3.0.7"
    }
  ]
}
FindingIllustrative result: each CVE names the affected package and the version that fixes it.

Spoorder Container Security vs running a scanner yourself

CriterionSpoorderrunning a scanner yourself
SetupNo agent or Docker daemon to installLocal tooling to install and maintain
Private registriesSaved credentials for Docker Hub, ECR, GCR and ACRLogin on each machine
FindingsTracked with your code and application findingsA separate report
Compliance mappingFindings mapped to framework controlsSeparate manual step
Do I need to install an agent to scan images?

No. You give Spoorder an image reference and, for a private image, a saved registry credential. The scan runs on Spoorder's side.

Can Container Security scan private registries?

Yes. Save a credential for Docker Hub, AWS ECR, Google GCR, Azure ACR or another registry under Settings, then select it when you scan.

What is the EPSS score and why does it matter?

EPSS (Exploit Prediction Scoring System), published by FIRST.org, is a probability from 0 to 1 that a CVE will be exploited in the wild within the next 30 days. Spoorder adds EPSS to findings that carry a CVE ID, so you can patch what is most likely to be exploited first.

Does this cover Helm charts and Kubernetes manifests?

Container scanning covers the contents of an image. Kubernetes manifests are checked by the IaC engine, and both sets of findings appear in the same dashboard.

What plan and credits does it need?

Container scanning is included from the Pro plan ($199/mo). A scan costs 6 credits.

Start scanning

Start with a free health check. Container Security is included from Pro ($199/mo).