Inspect and protect distributed environments with HCP Vault Radar
summary
HCP Vault Radar scans code and docs (GitHub, GitLab, Bitbucket, Confluence, Azure DevOps) via the SaaS console or agent pools/hybrid agents, indexes Vault to correlate leaked copies, and runs activeness checks (entropy, attempted logins) to escalate live credentials; found-audit stories range from hundreds to thousands of secrets (500 vs 5,000). Integrations open Jira/ServiceNow/Slack tickets for remediation, and prevention uses pre-commit hooks and PR checks; Radar is available in public beta.
AI-written summary · about
chapters (11)
- 0:00Introduction to Vault Radar
- 2:18Meet the speakers
- 3:20Why secret sprawl is a problem
- 5:27Secret sprawl pyramid explained
- 7:56Types of risks Radar detects
- 9:23How Vault Radar works
- 10:46Demo: Setting up data sources
- 13:36Demo: Prioritizing findings
- 18:09Prevention with PR checks
- 19:54Pre-commit hooks for security
- 21:02Call to action and resources
related talks
15mRemediate secret sprawl at scale
24mDeveloper-First Application Security and DevSecOps
39mSecurity in a DevOps World
14mSecurity lifecycle management in a multicloud world
12mCentralize and manage secrets with HashiCorp Cloud
50mDevOps: Shhhh! It's a secret! - HashiCorp Vault
28mEmbedding secrets governance into the enterprise through organizational change
38mKeeping Secrets - A Practical Approach to Managing Credentials
