Skip to content
_CORE
AI & Agentic Systems Core Information Systems Cloud & Platform Engineering Data Platform & Integration Security & Compliance QA, Testing & Observability IoT, Automation & Robotics Mobile & Digital Banking & Finance Insurance Public Administration Defense & Security Healthcare Energy & Utilities Telco & Media Manufacturing Logistics & E-commerce Retail & Loyalty
References Technologies Blog Know-how Tools
About Collaboration Careers
CS EN DE
Let's talk

Image Signing — Cosign and Sigstore

19. 11. 2025 Updated: 27. 03. 2026 1 min read intermediate

A signed image guarantees it comes from your build and has not been modified. Cosign + Sigstore solve this elegantly.

Cosign — signing and verification

Signing (keyless — OIDC identity)

cosign sign –yes ghcr.io/myorg/myapp:v1.0

Verification

cosign verify ghcr.io/myorg/myapp:v1.0

With a key

cosign generate-key-pair cosign sign –key cosign.key ghcr.io/myorg/myapp:v1.0 cosign verify –key cosign.pub ghcr.io/myorg/myapp:v1.0

Kubernetes admission — Kyverno

apiVersion: kyverno.io/v1 kind: ClusterPolicy metadata: name: verify-images spec: rules: - name: verify-cosign match: resources: kinds: [Pod] verifyImages: - imageReferences: [“ghcr.io/myorg/*“] attestors: - entries: - keyless: subject: “*@myorg.com” issuer: “https://accounts.google.com”

Key Takeaway

Sign images in CI/CD, verify in Kubernetes (Kyverno/OPA). Keyless signing with Sigstore.

securitycosignsigstorecontainers
Share:

CORE SYSTEMS team

We build core systems and AI agents that keep operations running. 15 years of experience with enterprise IT.