HashiCorp Vault Reviews

My primary use case for HashiCorp Vault is secret management. I keep my secrets away from the cluster in Vault, which acts as my secret manager. I remotely ingest with the help of Vaulting into the cluster.

The most valuable feature of HashiCorp Vault is version control. Whenever I change any secret, I am unable to edit it; I have to create a new version, which maintains a history. Additionally, Vault keeps my secrets safe and encrypted. The integration capabilities with Kubernetes are efficient, making it easy to detect.

We use it for password management.

For me, the most valuable features include that it's easy to manage and maintain the password API for retrieving passwords and other things.

The solution's typical use case is machine-to-machine communication, particularly in environments where development teams use various tools throughout the software development lifecycle. This includes scenarios where continuous integration is crucial. For instance, developers might manage various microservices or DNS services that frequently change. The solution facilitates secure and seamless authentication and integration of services, making it easier to manage service accounts and passwords. 

The feature I find most beneficial in HashiCorp Vault is the secret engine. It integrates smoothly with many applications, making it easy to set up and implement quickly. This allows you to test it easily and see good results rapidly. When you integrate an internal API or application, it quickly manages that application's secrets. 

The access management feature in HashiCorp is great, especially if you are considering situations where users are getting onboarded. They can manage their passwords themselves, and it integrates well with Active Directory or any other directory services. This is particularly useful for user management and applications that communicate with each other without human intervention.

I currently push secret data to our target namespaces. Before joining the company, I managed everything in HashiCorp Vault, but now I'm just a consumer.

We use it to store service principal credentials for Azure provisioning. 

Before provisioning things in Azure, we use HashiCorp Vault to store service principal credentials—passwords and such. Then, we can identify if a user is authorized to provision resources. 

If not, the blueprint will throw an error saying the user isn't authorized to provision or spin up resources in Azure. Same thing with other components, except for the applications themselves. We don't store credentials for those.

On the replication side, in a high-availability setup in multiple Vault instances, secret data is accessible by other resources. Each user or technical user has their own token, and there are different tokens for dev, test, QA, and product environments. It meets all three-point authentication, authorization, and access control requirements.

We use the solution for secret management. 

The product needs to improve its customization. It should be also more like easy to plug and play. 

The product is free and easy to use. It is well documented with an easy implementation process.

There could be a plugin for the database to change the secret automatically. It would be an efficient feature for password security.

We're a VoIP service provider, and we have a lot of particular requirements. Whatever we use must have a RESTful API. We also have very particular requirements around our backup, logging, and key lifecycle. That's because we have an American parent, who applies a lot of niche standards. My parent company is a big client of theirs. So, the overall group engages HashiCorp. It has gotten to the point where they actually reference HashiCorp as the tool of choice.

I ran a really detailed proof of concept for our business for six months. I got from HashiCorp one of their premium licenses, and we ran a test of it for six months,  but it is not in use at the moment.

We were using it for an on-prem implementation. I personally tested the HashiCorp cloud (HCP) on my personal laptop. I tested the premium version, which is the binary download, but it doesn't allow you to do clusters. It was a very limited use case, but we needed something on-prem. We are all on-prem. We don't operate in the cloud. So, we needed something to work with our on-prem setup. So, we weren't not doing a trial of the cloud version.

It was very easy to use. They've got multiple authentication methods, and because everything has a RESTful API, and my whole system is built on API, it would've worked fabulously for us.

One of our primary use cases of HashiCorp Vault is security, to keep things secret. Instead of going for any particular cloud-based solution, this is cloud agnostic. We can go for any cloud solution when we have a hybrid solution in place, so Vault is always recommended for it. 

This solution is cloud-based. 

The most valuable feature of HashiCorp Vault is that it's an open source solution. Second, it's cloud agnostic, so it's very easy to maintain and control, which is why we prefer HashiCorp.