Zero Trust Security
summary
Zero trust means authenticating and authorizing every human and machine by identity rather than IP, using Vault for dynamic short-lived credentials (examples: 24‑hour tokens, customers down to 15 minutes), Consul for service discovery and catalog, and mTLS certificates for mutual TLS identity certificates so services authenticate to each other. Boundary replaces VPNs with identity-based access and fetches one‑time secrets from Vault; Terraform and integrations automate perimeter devices with Terraform-driven firewall updates to keep policies current.
AI-written summary · about
chapters (15)
- 0:00Introduction and setup
- 1:06HashiCorp’s mission and multi-cloud challenges
- 6:24Traditional security vs zero trust
- 10:34Why zero trust is necessary now
- 13:04Identity-based security fundamentals
- 15:33Human identity and authentication
- 17:17Machine identity and Vault’s role
- 22:50Dynamic secrets and credential rotation
- 24:56Data protection and encryption
- 28:09Machine-to-machine communication
- 31:36Consul’s identity-based networking
- 34:01Network infrastructure automation
- 36:07Human access with Boundary
- 41:16Zero trust architecture summary
- 43:46Q&A session
related talks
01h 02mIntroduction to Zero Trust Security
42mZero Trust security with HashiCorp Vault and AWS (PRT239)
02h 48mZero Trust: the new normal!
35mDemystifying Zero-Trust for Cloud Native Technologies
25mRisk-based authentication and zero trust architecture ZTA
40mZero Trust, Zero Pain: A Practical Implementation with Intrinsic Security
36mManaged Zero Trust Security With HashiCorp Cloud Platform
39mOn Establish a Production Zero Trust Architecture