Security & Trust in a Microservices World
summary
Microservices let teams enforce data flow by classification instead of ad hoc endpoints: services get classification labels in service registry and responses are filtered at runtime, so changing a label (no code or redeploy) returns more or less user data — demonstrated with Kubernetes labels. Identity uses JWT-based transitive trust plus per-instance tokens, aggressive logging and alerts provide audit trails and forensics, and policy-driven revocation and caching keep performance acceptable.
AI-written summary · about
chapters (5)
related talks
01h 06mMicroservice Authentication and Authorization
46mSecure your Microservices with ZeroTrust approach
23mMicroservice Security at the API Level
23mAuthentication and Authorization in Micro Services
45mSecurity in a Microservices Architecture?
19mOAuth and OpenID Connect for Microservices
53mSecurity And Microservices
57mSecuring Microservices with Auth0 and MicroProfile in Kubernetes without a hassle
