Federating Trust in Healthcare with SPIFFE
summary
Claims a workable federated zero trust for healthcare that uses mTLS via SPIFFE/SPIRE and Envoy proxy for cross-cluster auth to let partner workloads access PHI/PII on HealthOS. Architecture deploys Spire servers and agents on each Kubernetes cluster (EKS/AKS style), exchanges trust bundles, enforces endpoint verification, uses JWTs and policy agents for authorization, and relies on PVC-backed workloads. Prototype boots, trusts are exchanged, and partner services authenticate to the HealthOS gateway to fetch member insights.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:37Abstract
- 1:14NIST Definition
- 2:33Anthem's Health OS
- 3:07Health OS Federation Introduction
- 3:49Tech stack
- 7:41Questions?
related talks
34mSecuring Multi-Cloud Cross-Cluster Communication with SPIFFE and SPIRE
32mA Platform-Agnostic Approach to Securing Workloads
36mFederated Identity for Distributed Systems: Understanding SPIFFE
36mSecuring Agentic Platforms with Zero-Trust Workload Identities
29mBridging the Great Divide: SPIFFE/SPIRE for Cross-Cluster Authentication
27mBridging Trust Between Multi-Cluster Meshes
19mFederate, Scale, and Secure: Practical SPIFFE/SPIRE for Containers...
30mIntro: SPIFFE