Attach a signed SBOM as a cosign attestation to an OCI image and verify the attestation in a downstream deployment step

domain: security/compliance · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Generate an SBOM for the image using Syft or Trivy and save it to a file (e.g., sbom.cdx.json).
  2. Run cosign attest --predicate sbom.cdx.json --type cyclonedx <image-digest-reference> using the image's digest (not tag) reference; if using keyless signing, the command will use the ambient OIDC token from the CI environment.
  3. Verify the attestation was stored by running cosign verify-attestation --type cyclonedx <image-digest-reference> and inspecting the returned predicate JSON.
  4. In a downstream deployment gate, run cosign verify-attestation with --certificate-identity and --certificate-oidc-issuer flags to enforce that the attestation was created by the expected CI workflow identity.
  5. Optionally pipe the verified predicate to a policy check (e.g., cosign verify-attestation ... | jq ... | opa eval) to enforce that the SBOM meets component or license policies.

Known gotchas

Related routes

Attach a signed SBOM attestation to an OCI image using cosign attest
docs.sigstore.dev · 6 steps · unrated
Attach and verify a cosign attestation for an SBOM linked to a container image
docs.sigstore.dev · 5 steps · unrated
Verify a cosign attestation on a container image with cosign verify-attestation
slsa.dev · 6 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans