SPIFFE and SPIRE: Architecture Deep Dive
Talkat Production Identity Day: SPIFFE + SPIRE 2020 · on Tuesday, 2020-11-17· at 12:40· Virtual, Virtual·
summary
SPIRE implements the SPIFFE Workload API with an agent/server model: agents cache SVIDs and bundles, servers hold X.509 and JWT authorities and offload private keys to key manager plugins (memory, disk, TPM coming, KMS). Node attestation uses cloud metadata or TPM-challenges to bind nodes; workload attestation uses kernel/docker/Kubernetes selectors to mint SVIDs. Authority rotation prepares keys at half-life and activates at one-sixth to avoid validation gaps. Deployments scale horizontally, use nested SPIRE or federation for cross-domain resilience.
AI-written summary · about
chapters (13)
- 0:00Andrew Harding
- 1:30Agenda
- 3:34Spiffing Verifiable Identity Document
- 4:41Spiffy Workload Api
- 5:27The Federation Api
- 7:30The Spire Agent
- 14:51Workload Attestation
- 18:05Key Manager Plug-In
- 21:09Upstream Ca
- 28:25Deployment Strategies
- 30:00Nested Spire
- 31:02Federation
- 31:36Summary
related talks
33mUniform Workload Identity Everywhere: SPIRE Integrations and Extensibility
37mSPIFFE Deep Dive
41mSPIFFE Project Intro
30mIntro: SPIFFE
34mSecuring Multi-Cloud Cross-Cluster Communication with SPIFFE and SPIRE
32mProduction Workload Identity with SPIRE
34mScaling SPIRE for Performance and Availability
49mReal World SPIFFE Scenarios and Outcomes
