AWS CloudHSM vs. Google Cloud Key Management vs. IBM Vault

Use for most types of cloud SQL services. Excellent modern-day encryption technologies. If a customer wants to manage their keys then Google Cloud Platform is well suited for those people if it matters. Able to divide workloads and pipelines. Customer managed encryption keys support for Data fusion, Data Proc, Cloud SQL, and GKE. We use Cloud EKM: key use operations $0.03 per 10,000 operations for our day to day operations.

Incentivized

HashiCorp Vault, in my opinion, is a defacto standard for any cloud or automation implementation. They're the best of the best as far as products for secrets management and the ability to use it against relatively any service you have is unheard of for other products. HashiCorp has really taken out all the stops when it comes to creating a nice, extensible tool that people can use to suit their needs.

Incentivized

• Option for Customer-Managed Encryption keys for Cloud which very [few] providers do.
• Option to enhance security via Hardware Security Modules.
• Easy control panel and CLI.
• Unified commands to approve or deny key requests.

Incentivized

• The HTTP API you use to write and read secrets is open and can be used by any application.
• It keeps our sensitive data/credentials out of our GitLab repositories.
• Sealing and unsealing the Vault on demand adds an additional layer of security.

Incentivized

• They removed the option for RSA128 bit security so yeah if it matters it a bummer.
• Pipelines are limited and very [few] for the amount you pay.
• General usability and Rapid CI/CD.

Incentivized

• Session Management is terrible to manage
• Monitoring is hard and not enough information
• User management
• Configuration is too complex
• More user friendly UI

HashiCorp Vault is the best there is out there, and it has become critical to our secret management use cases. It would be difficult to find anything that would suit our needs better and that would be beneficial for us to switch over to.

Incentivized

We spent a little more time than we imagined to conceptually understand how HashiCorp Vault operates, as well as how it is configured. This is not trivial, and keep in mind that you will need to take some time to get a thorough understanding of the tool. The documentation could be more helpful in this regard.

Incentivized

Hashicorp has been very responsive to our questions and inquiries up to this point. We are currently working on them to develop a more granular permissions model within Vault. We are very close to achieving our objectives with the help of their support team. We do not seem to be in the same time zone which makes it hard for escalated issues.

Incentivized

The UI / UX, first of all, is night and day difference. The main attraction after the services were this: It's user friendly. It welcomes new users and properly guides them on what to do and what you can expect. Honestly, I had a very bad experience with Microsoft Azure in 2018, so I think the Google Cloud Key Management service is best for me for now and I may give the new Azure a try later.

Incentivized

HashiCorp Vault is way better than Azure Key Vault; it has more features and it goes beyond a key-value secret store.

Incentivized

• There is no Return of investment in our operations as we use it for KMS.
• The only ROI is that we have a piece of mind while our data is handled by Google.
• Our main objective is being fulfilled and the staff as well as customer are happy.
• Value for money.

Incentivized

• Helped us reach our security compliance goals.
• Helped us strengthen our security position in our infrastructure by improving on poor secret management practices.

Incentivized