Trust by verify - how to provide secure access to your team
summary
Argues that traditional VPNs fail at continuous, least-privilege access and cites over 560 known VPN vulnerabilities; recommends zero trust patterns: continuous authentication, short-lived certificates and just-in-time access to limit lateral movement and credential exposure. Recommends routing access through a proxy/gateway for identity-aware authorization and audit, notes Google’s BeyondCorp (2014) as a model, and points to Teleport as an open source implementation that issues short-lived certs and provides authentication, authorization and auditing across cloud resources.
AI-written summary · about
chapters (13)
- 0:00Zero trust access intro
- 1:28Zero trust necessity
- 2:51VPN perimeter limits
- 4:59Zero trust principles
- 6:24Continuous auth & least privilege
- 8:50Shared secrets risks
- 11:37Just-in-time access
- 12:42Certificates replace secrets
- 14:27Restrictions vs usability
- 16:12Unified access & accountability
- 17:36BeyondCorp & identity proxy
- 18:19Teleport cloud tools
- 19:20Zero trust benefits
related talks
23mZero Trust: From Airports to Identity-Aware Proxies
23mEstablishing trust with verifiable creds and zero trust
49mZero Trust Security
27mLeveraging Infrastructure as Code to Create Zero Trust Access to Your Apps and Infrastructure
19mZero Trust: From Airports to Identity-Aware Proxies
26mZero Trust: Continuous Verification in the Modern Enterprise
40mClarifying Zero Trust: The Model, the Philosophy, the Ethos
48mBeyondCorp: A DevOps Security Model Without Sign‑On and VPN