Demystifying Zero-Trust for Cloud Native Technologies
summary
Zero trust means eliminating implicit network trust and enforcing identity and policy across ephemeral cloud native workloads; the panel describes using x509 certificates and JWTs for strong workload identity, Spire for cross‑cloud federation, Istio or a service mesh/overlay for microsegmentation, attestation plus a software bill of materials (SBOM) for host integrity, and CI/CD checks plus continuous monitoring to feed policy updates. It notes Kubernetes’ ephemeral IPs and dynamic pods as the core operational challenge.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:15What is zero trust
- 6:05Zero trust principles
- 9:16Cloud native security
- 12:49Zero trust building blocks
- 15:55Implementing zero trust
- 19:04Workload identity security
- 23:43Zero trust networking
- 27:59Golden path to zero trust
- 31:09Next steps for zero trust
related talks
23mThe Long and Windy Road that leads to Cloud Native Security
45mZero Trusting as a True Cloud Native Dev
41mZero-Trust Networks: Identity, AuthN, AuthZ, Audit
01h 02mIntroduction to Zero Trust Security
49mZero Trust Security
29mZero Trust for APIs: From Edge to Mesh with Istio
32mImplementing Zero Trust in a Kubernetes Cluster with Istio
45mZero Trust: Getting to Step One..and What to Do When You Get There