From 0 to hero: platform engineers are Zero Trust rainmakers
summary
Claims that platform engineers become the ones who implement Zero Trust inside Kubernetes by automating identities policies and enforcement using concrete tools and primitives: cert-manager for x509 lifecycle, Kubernetes RBAC and CNI/networkpolicies, Istio and Linkerd for mTLS and traffic controls, and kyverno and gatekeeper for admission policy enforcement. The concrete result is automated certificate issuance and per‑request identity checks wired into CI/CD and cluster admission, requiring security to define policies and platform to build and operate them.
AI-written summary · about
chapters (7)
- 0:00Zero Trust in Kubernetes intro
- 1:40Zero Trust core principles
- 3:08Zero Trust challenges in Kubernetes
- 8:08Kubernetes native Zero Trust
- 9:38Zero Trust add-on tools
- 11:04Platform engineers' Zero Trust role
- 12:48Security and platform teamwork
related talks
15mPlatform Engineering Security
35mDemystifying Zero-Trust for Cloud Native Technologies
06mSponsored Keynote: Kubernetes is the Perfect Platform for Enforcing Zero Trust Security
45mZero Trusting as a True Cloud Native Dev
27mPlatform-led Zero Trust service networking for Fintech
39mOn Establish a Production Zero Trust Architecture
22mBuilding Secure AI Platform Infrastructure: A Zero Trust Framework
18mImplementing Zero Trust at Enterprise Scale