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.
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.
Project Manager at a comms service provider with 201-500 employees
Real User
2022-03-30T11:55:40Z
Mar 30, 2022
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.
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.
Founder & Principal Architect at NCompas Business Solutions Inc.
Real User
2021-03-16T23:00:21Z
Mar 16, 2021
Primarily, we use this solution for the secret management side of things. Initially, we were using Azure Key Vault, but we kind of shifted to HashiCorp Vault because we are using Terraform scripts, etc. We needed a common storage mechanism.
We are currently conducting a PoC with HashiCorp vault to see if it meets our requirements. I have ten different use cases for the evaluation. We are integrating it into our Key Management Service. In my previous company, we were using it to store all of our keys and secret certificates.
TechOps Engineer - Middleware & Containers specialist at EBRC -European Business Reliance Centre
Real User
2019-05-23T17:02:00Z
May 23, 2019
This is a Secrets Management framework to manage a keystore, certificates, and passwords dynamically in a Platform as a Service context, such as Vanilla Kubernetes Platforms, Rancher, Meso, Tectonic, and Origin/OpenShift Enterprise Platforms. Whatever the platform, this product can help provide good security and be PCI Compliant.
HashiCorp Vault is a cloud-agnostic solution used for security and secret management. Its valuable features include integration with other HashiCorp tools, token sharing, open source nature, cloud agnosticism, and on-the-fly encryption management.
The solution provides encryption of data at rest, in use, in transit, on the fly, and linked with applications. It is free to use, and the interface is simple to navigate. HashiCorp Vault has helped organizations with its multiple...
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.
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.
We use HashiCorp Vault to manage and keep all secrets and configurations in SQL. It works as central storage, securing different environments.
We use it for password management.
We use the solution to store and encrypt the passwords.
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.
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.
Primarily, we use this solution for the secret management side of things. Initially, we were using Azure Key Vault, but we kind of shifted to HashiCorp Vault because we are using Terraform scripts, etc. We needed a common storage mechanism.
We are currently conducting a PoC with HashiCorp vault to see if it meets our requirements. I have ten different use cases for the evaluation. We are integrating it into our Key Management Service. In my previous company, we were using it to store all of our keys and secret certificates.
This is a Secrets Management framework to manage a keystore, certificates, and passwords dynamically in a Platform as a Service context, such as Vanilla Kubernetes Platforms, Rancher, Meso, Tectonic, and Origin/OpenShift Enterprise Platforms. Whatever the platform, this product can help provide good security and be PCI Compliant.