Compliance and Identity Management in Kubernetes
summary
Claims that automating identity workflows removes admins from access requests and produces auditable proof for frameworks like FISMA/NIST, demonstrated working end-to-end: kube 1.8 cluster + API server, AD FS via SAML for auth, short‑lived tokens (seconds to a minute) via OpenID Connect, role/rolebinding model for authorization, a relational audit store, and a workflow engine that creates namespaces, grants and revokes access. Demo uses OpenUnison with U2F YubiKey MFA, shows live namespace creation, approvals, audit logs and successful immediate revocation.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:54Who Am I?
- 1:39Why Is Compliance Important?
- 2:51What Is Compliance?
- 3:47Where Does IDM Fit?
- 4:29IDM Compliance without DevOps
- 6:47How This Applies to k8s?
- 12:24Demo Environment
- 26:27Useful Resources
- 27:32Shameless Self Promotion
related talks
01h 59mBuilding Secure Kubernetes Clusters with Identity Management
09mData-Driven Identity Governance for Modern Infrastructure
33mIdentity and Access Management in Kubernetes
23mKeynote: Cloud & Cloud Native Identity and Access Management: Challenges & Opportunities
34mWho Are You? I Really Want to Know… the Magic Behind OIDC
59mKubernetes access control in the enterprise
41mKubernetes Auth and Access Control
40mArchitecting Secure Agentic Workflows on Kubernetes: A Financial Sector...