Cosign and Sigstore for Image Signing
What you'll learn: How Cosign and Sigstore enable modern, keyless container image signing using transparency logs instead of traditional key management.
The Modern Approach to Image Signing
You've learned that signing container images proves their authenticity and integrity. Traditionally, this required managing private keys securely—a significant operational burden. Cosign (part of the Sigstore project) revolutionizes this by offering "keyless" signing that leverages your existing identity providers (like GitHub, Google, Microsoft) combined with a transparency log.
How Sigstore and Cosign Work
Think of Sigstore as a "notary public" for software artifacts. When you sign an image with Cosign in keyless mode:
- You authenticate using OpenID Connect (OIDC) with your existing identity
- Sigstore issues a short-lived certificate tied to your identity
- The signature is recorded in a public, immutable transparency log called Rekor
- Your signature is stored alongside the container image in the registry
The transparency log acts like a tamper-proof ledger—anyone can verify that your signature was created at a specific time by a specific identity, without you needing to distribute public keys.
Verification Benefits
When verifying an image, Cosign checks:
- The cryptographic signature matches the image digest
- The signature exists in Rekor's transparency log (proving it was created, not backdated)
- The identity claimed in the certificate matches your policy (e.g., "signed by our CI system's identity")
This approach eliminates key rotation, key storage risks, and key distribution challenges while maintaining cryptographic proof of authenticity.
Key Takeaway: Cosign and Sigstore provide keyless image signing by combining OIDC identity, short-lived certificates, and a public transparency log—offering security without the operational overhead of traditional key management.