Clarifying Zero Trust: The Model, the Philosophy, the Ethos
summary
PagerDuty documents building a cross‑region access control system that replaces VPN tunnels with a full opportunistic IPSec mesh so mutual auth and kernel‑level encryption apply to every flow. Policy lives in a Chef DSL → iptables pipeline checked into code and auto‑deployed, so the kernel drops non‑IPSec packets and all flows become authenticated, authorized and logged. Companies cited: Google BeyondCorp, Lyft (Envoy), Stripe; most deployments are DIY with partial vendor components.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:32What is PagerDuty
- 2:11Reliability
- 3:48Cross Cloud Cross Region
- 4:27DSL Example
- 5:45VPN
- 6:06Availability Concerns
- 7:19Transport Mode
- 9:00IP Tables
- 9:59No centralized firewall
- 10:35Beyond Corporate
- 13:05What is Zero Trust
- 15:52Every Flow is Expected
- 16:45IntentBased Policy
- 20:23Network Agent
- 23:13Automation Systems
- 24:45Side Benefits
- 26:14Starting Early
- 27:36Current State
- 29:26Client implementations
- 31:31Commercial vendors
- 32:45Conclusion
related talks
45mZero Trust: Getting to Step One..and What to Do When You Get There
40mZero Trust, Zero Pain: A Practical Implementation with Intrinsic Security
35mDefense Through Invisibility: Zero Trust Security for the Enterprise
35mDemystifying Zero-Trust for Cloud Native Technologies
32mImplementing Zero Trust
27mLeveraging Infrastructure as Code to Create Zero Trust Access to Your Apps and Infrastructure
01h 02mIntroduction to Zero Trust Security
31mEmbracing Zero Trust When You Aren't the World's Largest Internet Company