SPIFFE
A CNCF standard for issuing short-lived, verifiable identities to workloads, as X.509 or JWT SVIDs, without static secrets.
SPIFFE defines an identity format (spiffe://trust-domain/path), a document that carries it (an SVID, either an X.509 certificate or a JWT) and a Workload API from which a process fetches its SVID. SPIRE is the reference implementation: agents attest workloads by kernel and orchestrator facts (Kubernetes service account, node identity) before issuing them an SVID.
It removes the bootstrap problem of how a service gets its first secret. The platform vouches for the workload, certificates live for minutes or hours, and rotation is automatic, making mTLS between services routine. Istio and other meshes issue SPIFFE-format identities.
Pitfalls: authorising on overly broad ID prefixes, weak node attestation that lets any pod claim any identity, and federation between trust domains configured without thinking about what each side may assert.
spiffe://prod.example.com/ns/payments/sa/ledger-writerLearn it properly
Also used in
- Identity: authentication, authorisation and tokensSecEng · Foundations of Security EngineeringFree
- TLS and PKI in practiceSecEng · Network & Infrastructure SecurityFree
- The round, the framework, the numbersHLD · The security HLD roundFree
- Design a zero-trust access gatewayHLD · Design problems: Access & identityFree
- Secrets management and rotationSecEng · Identity & Access EngineeringPro
- Zero trust reference architectureSecEng · Advanced: Security Architecture at ScalePro