DataTerminology.comNEW
Also known as: HashiCorp Vault
A tool for securely storing, accessing, and managing secrets and cryptographic material with fine-grained policy controls.
DESCRIPTION
HashiCorp Vault centralizes secret storage, access, and rotation. It supports static and dynamic secrets, encryption-as-a-service, PKI, and identity-based policies. Vault integrates with cloud providers, databases, and platforms. Audit devices record usage for compliance. It is widely used to secure credentials in CI/CD, microservices, and data platforms.
ALTERNATIVE DEFINITIONS
HashiCorp
Vault is a tool for securely storing and accessing secrets.
Concise vendor definition focusing on secure secret storage.
Red Hat
HashiCorp Vault is an identity-based secrets and encryption management system.
Highlights identity-based access and encryption management.
CNCF
Vault provides a unified interface to manage secrets and protect sensitive data in dynamic infrastructure.
Stresses dynamic infrastructure and unified secrets interface.
RELATED TERMS
Secrets Management Key Management Service Data Encryption Tokenization Public Key Infrastructure IAM Hardware Security Module Secret Rotation Service Identity Policy-Based Access Control
COMPETING TERMS
AWS Secrets Manager Azure Key Vault Google Secret Manager
RELATIONS
- Narrower: Azure Key Vault Data Vault
KNOWLEDGE AREAS
Data Security Infrastructure Platform & Tooling MLOps
TARGET AUDIENCE
DevOps Engineer Security Architect Cloud Architect Software Developer MLOps Engineer
EXTERNAL SOURCES
- Wikipedia - HashiCorp Vault
- HashiCorp - Official Vault documentation
- HashiCorp - Open source Vault repository
- Red Hat - Vendor overview of Vault
TOP QUESTIONS
Why use Vault for secrets management?
Vault centralizes secret storage, enforces policy-based access, supports dynamic credentials, and provides auditing for compliance.
Category: Relevancy
How does Vault handle dynamic secrets?
It generates time-bound credentials on-demand for services like databases, automatically revoking them after TTL.
Category: Example
What are common mistakes when using Vault?
Overly permissive policies, unsealed clusters, missing audit devices, and storing secrets in config files undermine security.
Category: Mistakes
How is Vault integrated in CI/CD pipelines?
Use short-lived tokens, inject secrets at runtime, and avoid persisting them in artifacts or environment variables.
Category: Best practices
What risks exist if Vault is misconfigured?
Leaked root tokens, unencrypted backends, or weak authentication could expose sensitive credentials.
Category: Risks
What are alternatives to Vault?
AWS Secrets Manager, Azure Key Vault, and Google Secret Manager provide managed secrets services.
Category: Alternatives
How does Vault support encryption services?
Vault’s transit engine offers encryption, decryption, and signing without storing data, enabling cryptography-as-a-service.
Category: Overview
How is Vault secured and managed?
Use secure storage backends, enable audit logging, enforce HSM-backed auto-unseal, and implement strong auth methods.
Category: Management
What is a striking analogy for Vault?
Think of Vault as a bank vault with controlled compartments, issuing time-limited keys and recording every access.
Category: Example