HashiCorp Vault is a secrets management and data protection system for securely storing, accessing, and distributing credentials, API keys, certificates, and encryption keys. It centralizes secret lifecycle management, enforces fine-grained access policies, and provides audit logging and dynamic secrets to reduce credential sprawl across infrastructure and a…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
HashiCorp Vault centrally manages sensitive information such as passwords, tokens, and certificates and controls access to it.
Vault emerged at HashiCorp from the problem of applications keeping secrets scattered in configuration files and environment variables. The project was developed as open source and first released in 2015 to centralize secret management and short-lived credentials.
A client authenticates through a configured authentication method. Policies allow paths and operations; secrets engines store or generate values, while leases, rotation, and audit logs govern their lifecycle.
Workloads and people prove identity through suitable auth methods.
Policies limit which identity can access which secret paths.
Leases, rotation, and revocation limit credential validity.
Vault reduces scattered secrets and makes access traceable. High availability, unsealing, backup, key management, and careful policies are part of secure operation.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.