Zero Trust: From Airports to Identity-Aware Proxies
summary
Shows how an identity-aware proxy (IAP) running at layer 7 — e.g., as an edge service or Kubernetes ingress — enforces continuous verification, device posture and context rules, and pushes fine-grained micro-segmentation down to individual routes. Describes a practical migration: pilot one app, add MFA and device checks, then expand; legacy apps sit behind the IAP immediately. Claims VPNs can coexist but cites 2.8 million IPs currently attacking VPN infrastructure as a reason to move away from perimeter trust.
AI-written summary · about
chapters (12)
- 0:00Introduction to Zero Trust and Airport Security Analogy
- 1:36Why Zero Trust Matters
- 2:28Problems with Perimeter-Based Security
- 4:56Airport Security as a Zero Trust Model
- 7:32Core Zero Trust Components
- 8:14Identity Aware Proxy
- 9:38Context-Defined Access
- 10:25Policy Engine
- 12:26Microsegmentation
- 13:56Zero Trust for Legacy Systems
- 16:46Zero Trust with Kubernetes
- 17:33Conclusion and Key Takeaways
related talks
23mZero Trust: From Airports to Identity-Aware Proxies
35mIdentity Aware Proxy — Taking a Meaningful Step Toward Zero Trust
29mZero Trust for APIs: From Edge to Mesh with Istio
45mZero Trust: Getting to Step One..and What to Do When You Get There
40mZero Trust, Zero Pain: A Practical Implementation with Intrinsic Security
27mLeveraging Infrastructure as Code to Create Zero Trust Access to Your Apps and Infrastructure
38mIdentity Based Segmentation for a ZTA
20mTrust by verify - how to provide secure access to your team