Workload Identity

The Secure Production Identity Framework for Everyone (SPIFFE) standardizes workload identity across heterogeneous systems. It defines a SPIFFE Verifiable Identity Document (SVID) , a short-lived X.509 certificate or JWT that proves the workload's identity. A SPIFFE ID is a URI, such as spiffe://example.com/ns/production/sa/web-server, that uniquely names the workload. The SPIFFE Workload API provides a secure, local endpoint for a process to retrieve its SVID without knowing any secrets, enabling identity bootstrapping.

The Secure Production Identity Framework for Everyone is an open-source standard that defines how services identify themselves in cloud-native environments. It provides a universal identity control plane where every workload receives a cryptographically verifiable identity document called a SPIFFE Verifiable Identity Document (SVID). Identities take the form of a URI, such as spiffe://trust-domain/workload, decoupling identity from network location. The SPIFFE Runtime Environment issues and rotates these short-lived certificates automatically, eliminating the need for manually managed secrets.

A cryptographic paradigm that binds a signature to a workload's OpenID Connect (OIDC) identity rather than a long-lived private key. The process works by:

• Authenticating the workload via an OIDC token from a trusted provider
• Requesting a short-lived certificate from a certificate authority like Fulcio
• Signing the artifact with the ephemeral key
• Recording the signature in a transparency log like Rekor This eliminates the operational burden of key rotation and storage while providing non-repudiation tied to the workload's identity.

A command-line utility within the Sigstore ecosystem that signs and verifies container images and other OCI artifacts using workload identity. Cosign supports multiple signing modes:

• Keyless signing: Uses ephemeral keys bound to an OIDC identity
• Key-based signing: For environments requiring explicit key management
• Hardware token integration: Supports HSMs and hardware tokens Signatures are stored directly in the container registry alongside the artifact, enabling seamless verification in CI/CD pipelines and admission controllers.

A cryptographically signed statement that asserts a verifiable fact about a software artifact or process. In the context of workload identity, attestations provide a tamper-proof record of:

• Provenance: Who built the artifact, from what source, using which build steps
• Vulnerability scans: Results of security scanning at build time
• Test results: Evidence that specific test suites passed
• Policy compliance: Confirmation that organizational policies were satisfied The in-toto framework standardizes how these attestations are collected and verified across the entire software supply chain.

A Kubernetes-native security mechanism that intercepts API requests before resources are persisted. In a workload identity context, admission controllers enforce binary authorization policies:

• Verify that every container image has a valid signature from an authorized workload identity
• Reject deployments where the signing identity does not match the expected SPIFFE ID
• Enforce that attestations exist and pass policy checks Tools like Open Policy Agent (OPA) and Kyverno implement these policies using the Rego language, ensuring only trusted, identity-verified workloads run in production.

An append-only, cryptographically verifiable ledger that records digital signatures and certificates in a publicly auditable manner. The Rekor service implements this for the Sigstore ecosystem. Key properties include:

• Immutability: Once recorded, entries cannot be modified or deleted
• Verifiability: Anyone can cryptographically verify the inclusion and consistency of entries
• Non-repudiation: Signers cannot later deny having signed an artifact This creates a permanent audit trail linking workload identities to their signed artifacts, critical for SLSA compliance and regulatory requirements.