Security lifecycle management in a multicloud world
summary
Customer survey shows leaked credentials top cloud security worry and Verizon data says 9 of 10 web app breaches stem from stolen creds; HashiCorp Cloud Platform uses Vault and Boundary plus a new scanner Vault Radar that scans 18 data sources and finds exposed items (demo surfaces an SSH key in a repo). Exposed secrets get ticketed via Slack, moved into Vault KV, converted to dynamic SSH credentials that Boundary injects for access, and sessions are captured with Boundary session recordings for post‑incident forensics.
AI-written summary · about
chapters (11)
- 0:00Introduction to security lifecycle
- 1:26HashiCorp Cloud Platform overview
- 2:28Protecting credentials with Vault
- 4:17Secure access with Boundary
- 5:42Finding secrets with Vault Radar
- 8:32Moving secrets to Vault
- 9:58Dynamic secrets in Vault
- 10:39Boundary for least privilege
- 11:43Vault and Boundary integration
- 12:47Session recordings in Boundary
- 14:13Closing and Q&A
related talks
29mBuilding blocks of security lifecycle management
29mBe nice, help the person who hacks your servers to get your data
24mDeveloper-First Application Security and DevSecOps
26mCloud Security Lessons
27mWho's managing the credential for your data infrastructure?
45mProtecting you from you: Misconfiguration-caused breaches
38mAdventures in Cloud Security: What DevOps Can Learn from a Security Engineer
39mPerils of the cloud