CyberKit

Image Provenance and Signing

Also called Image signing, Software provenance.

Cryptographically proving where a container image came from and that it is unaltered.

What it is

The practice of attaching verifiable metadata and cryptographic signatures to container images so consumers can confirm the image's origin and that it has not been tampered with. Verification can be enforced as an admission gate before deployment.

Why it matters

Provenance defends against supply-chain tampering and substituted images, and during an incident a signature mismatch is strong evidence that a malicious image slipped into the pipeline.

In practice

An investigator finds the running image had no valid signature, indicating it bypassed the build pipeline and was pushed directly by the attacker.

What to look for

  • Images deployed without a valid signature or attestation.
  • Digests that do not match what the build system produced.
  • Tags reused to point at different images.

Common mistake

Trusting tags. A tag can be moved; pin and verify digests and signatures.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Trivy Open source

    Scans images, file systems and code for known vulnerabilities and secrets.

  • Falco Open source

    Detects suspicious behavior inside running containers and Kubernetes.

  • Sigstore Open source

    Signs and verifies software artifacts so you can prove where a build came from.

  • CrowdStrike Falcon Cloud Security Commercial

    Protects cloud workloads and containers, from build to runtime.

Read next

Sources