cosign
An open-source tool under the Sigstore project, designed for signing, verifying, and attesting OCI container images and artifacts. It supports attaching structured metadata such as scan reports and SBOMs to artifacts in cryptographically signed form, conforming to the in-toto Attestation Framework.
Timeline (last 90 days)
cosign's Attestation feature allows arbitrary structured metadata (such as scan reports, SBOMs, and build logs) to be attached to an artifact in signed form, following the in-toto Attestation Framework format.
cosign is an open-source tool under the Sigstore project, designed specifically for signing, verifying, and attesting OCI container images and artifacts.
cosign stores signature information in the same OCI repository as the artifact, cryptographically binding it via the artifact's content digest (SHA256 digest); whenever the artifact's content changes, the digest changes accordingly and the existing signature is automatically invalidated.
When re-scanning after a scanner upgrade, appending a new attestation with the scanner version and timestamp recorded is more reasonable than an overwrite-style update and facilitates audit traceability.
cosign attestations can be automatically intercepted and verified at deployment time by Kubernetes policy engines such as Kyverno and OPA Gatekeeper.
Attaching each scan result as a cosign attestation to an OCI artifact and having the cluster perform policy validation at startup—rejecting artifacts that lack the required attestations—is a viable ML supply chain security approach.
GitHub introduced official signing support for Actions release artifacts (based on the Sigstore/cosign system) in 2022.
All Facts (7)
cosign's Attestation feature allows arbitrary structured metadata (such as scan reports, SBOMs, and build logs) to be attached to an artifact in signed form, following the in-toto Attestation Framework format.
50%Unverifiedcosign is an open-source tool under the Sigstore project, designed specifically for signing, verifying, and attesting OCI container images and artifacts.
50%Unverifiedcosign stores signature information in the same OCI repository as the artifact, cryptographically binding it via the artifact's content digest (SHA256 digest); whenever the artifact's content changes, the digest changes accordingly and the existing signature is automatically invalidated.
50%UnverifiedWhen re-scanning after a scanner upgrade, appending a new attestation with the scanner version and timestamp recorded is more reasonable than an overwrite-style update and facilitates audit traceability.
50%Unverifiedcosign attestations can be automatically intercepted and verified at deployment time by Kubernetes policy engines such as Kyverno and OPA Gatekeeper.
50%UnverifiedAttaching each scan result as a cosign attestation to an OCI artifact and having the cluster perform policy validation at startup—rejecting artifacts that lack the required attestations—is a viable ML supply chain security approach.
50%UnverifiedGitHub introduced official signing support for Actions release artifacts (based on the Sigstore/cosign system) in 2022.
50%