Embedding secrets governance into the enterprise through organizational change
summary
Nationwide and River Point describe hardening and centralizing HashiCorp Vault, migrating a deprecated secrets store into a hardened Vault cluster and automating certificate and secret workflows. They claim audits simplify because secrets move out of source and a rotate every 10 hours cadence is now feasible. Adoption needs executive sponsorship, roadshows and end-to-end automation to avoid operational outages; they cite 60–75% of breaches involving identities and show proof by resolving P0 incidents and improving availability for critical apps.
AI-written summary · about
chapters (14)
- 0:00Introduction and speakers
- 1:48Vault’s initial challenges
- 3:55Overcoming operational resistance
- 6:20Organizational change strategy
- 9:05Expanding Vault beyond secrets
- 11:13Legacy culture and legacy systems
- 13:22Organizational patterns for success
- 15:30Leveraging P0 incidents for ROI
- 17:19Third-party and infrastructure apps
- 18:41Compliance and audit benefits
- 20:49Reducing audit burden
- 21:50Future use cases and AI
- 24:41Advice for other organizations
- 27:27Closing and Q&A
related talks
28mHow to Store Secrets—and When Do You Need Them—in HashiCorp Vault
50mDevOps: Shhhh! It's a secret! - HashiCorp Vault
38mKeeping Secrets - A Practical Approach to Managing Credentials
41mHiding secrets in a Vault
29mHow to get dynamic with secrets management
29mBehind Closed Doors: Managing Passwords in a Dangerous World
40mA Better Way To Manage Secrets
43mSecret Management with Hashicorp's Vault