Securely Bridging Cloud-Native and Traditional Workloads...
summary
Not everyone can move to Kubernetes at once so SPIRE provides a single identity layer that issues X.509 or JWT identities to services across clouds, datacenters and clusters. A central SPIRE server verifies agents against cloud and Kubernetes APIs while agents perform workload attestation via OS and platform primitives and then mint identities according to policy. Once services hold those identities they establish mTLS and other secure connections uniformly, and examples show patterns for hybrid legacy and cloud native integrations.
AI-written summary · about
chapters (6)
related talks
34mSecuring Multi-Cloud Cross-Cluster Communication with SPIFFE and SPIRE
33mUniform Workload Identity Everywhere: SPIRE Integrations and Extensibility
32mA Platform-Agnostic Approach to Securing Workloads
34mScaling SPIRE for Performance and Availability
33mSPIFFE and SPIRE: Architecture Deep Dive
36mIntroducing SPIFFE: An Open Standard for Identity in Cloud Native Environments [I]
32mProduction Workload Identity with SPIRE
37mZero Trust Workload Identity in Kubernetes