The solution's access policy is important. You can directly provide the kind of access you want to grant to any particular user or batch of users rather than monitor which particular user should assign which particular task and what things can be seen by which particular user. Those kinds of restrictions can be added directly using the access policy. You need to maintain the solution. If the credentials are getting expired, you have to provide an update on that. One person is more than enough to maintain the solution. Overall, I rate the solution a seven out of ten.
Azure Key Vault provides a very good interface wherein we can continuously change or recycle the keys seamlessly. This automatic mechanism is much better than the typical process of changing keys or certificates. The solution takes backups before the keys expire and informs us in advance when the keys will expire. There is something called rainbow keys. I can generate certain read-only keys that even the administrator cannot delete. The access control is very granular. I can provide access control on certain keys so that only a specific person can access them. We have deployed Azure Key Vault on the cloud in our organization. Azure Key Vault is the best solution for Microsoft users. If you use another cloud provider, you will have to find a solution that works across all of them. Overall, I rate the solution a seven out of ten.
I use the tool to manage application secrets by storing digital assets separately. My company puts the digital assets directly in the tool using the credentials. Azure Key Vault plays a key role in encryption in certain projects or scenarios in our company. In our company, if we want to apply some algorithms to encrypt our data, we store such data in Azure Key Vault and pull it manually from the solution later to encrypt our organization's data. My company doesn't exactly use the access policies in Azure Key Vault for managing permissions, but we do use it for the storage of our secret information. For managing our company's secrets, we use Azure Key Vault, but we don't use it for managing permissions as we use IdentityServer and other tools for such purposes. Azure Key Vault can integrate very well with other Azure services. Azure Key Vault is a good option since it is a secure and useful tool. I rate the solution a nine out of ten.
Dev Ops Engineer at a wellness & fitness company with 201-500 employees
Real User
Top 5
2024-03-05T07:22:00Z
Mar 5, 2024
The most beneficial component related to cryptographic graphic key management stems from the auto-rotation functionality. The product comes with two types of access policies. The tool provides a conventional policy and Azure RBAC. My company mostly, you say, the conventional access policy and it has been working great so far. The product plays a crucial role in our company's security strategy. The product is easy to maintain. The product helps ensure compliance with our industry regulations since it meets most of the auditing and compliance rules. It is a secure solution that needs to have most of the policies and compliance rules. I would say that Azure Key Vault is a good solution, considering the security part. I rate the overall tool a nine out of ten.
The platform provides straightforward integration with most of the other Azure services. It has improved the compliance and auditing processes. Earlier, we had to either store secret information inside the application or develop a custom solution to comply with it. There was a high chance of the data getting corrupted as different people had access to it. I rate Azure Key Vault an eight out of ten.
I am satisfied with the product overall. I would definitely recommend the solution to small companies planning to use it since it is quite straightforward. Overall, I rate the solution a nine out of ten.
We are a partner of Microsoft. We haven't exported or imported information in Key Vault. This solution is worth the cost and is useful to use. It's a service that can be used in multiple regions in Azure. They are mostly deployed in UK South and UK West. It can be deployed and used in other regions as well; however, we have data constraints. I'd rate her solution eight out of ten overall. Potential new users should consider the types of sensitive information they want to store and how they want to retrieve the information, and from where. These are critical to understanding as they will govern the configuration of Key Vault. You can deploy Key Vault both publicly and privately. For example, if you do it privately, you can ensure you will ensure it can only be accessed from within your environment, and that ensures a very high level of security.
I advise others to use the solution if they already work with Microsoft Azure environment. In such cases, they should not prefer integration with a third-party tool. They should consider other products if the databases are distributed to on-cloud and on-premises infrastructures. I rate the solution as an eight.
I would rate Azure Key Vault a nine out of ten. I recommend it as a good solution for those using Azure Cloud to host their services. The solution does not require any maintenance.
Senior Data Engineer at a tech company with 201-500 employees
Real User
Top 5
2023-02-12T12:22:05Z
Feb 12, 2023
I give the solution a ten out of ten. The solution is self-maintaining. We have implemented EIS, and infra as a code, and incorporated a CI/CD process to automate the maintenance in our environment. I always recommend going to Microsoft Learn for its rich knowledge base. Azure Key Vault is an excellent solution for improving organizational security, and it offers great value for money.
CyberSecurity Director of Intelligence at a tech services company with 1-10 employees
Real User
2022-06-01T21:05:00Z
Jun 1, 2022
Other service providers try to lower the prices, but it all depends on your development environment and your core skills. You are a bit more stuck if you are coding in .NET. If you go down that route, you can't easily move out to another service provider. Maybe you can go the route of adding a new team with a different service provider, but then you will need to mash it together. You would need to evaluate if that is a good option. We have about 70 developers and they are in different teams. They interact with third parties and they have different roles, including front-end and back-end developers. Each one creates services for different websites for different regions, to sell e-vape cigarettes. And we have team leaders who use it as well. There's a security team of five people responsible for the infrastructure of Azure, including creating new resources or whatever is necessary for the dev teams. There are also operations management and product owners who make decisions on schedules, what will be built, and priorities. Deployment and maintenance are part of the security engineers' work, to manage any issues. Sometimes the dev teams get involved with root cause analysis if something is going wrong with a web application. We have a team for certain maintenance tasks and requests. The biggest lesson I've learned from using this solution is: "Stay secure."
Senior Software Engineer at a tech services company with 10,001+ employees
Real User
2022-04-12T16:49:10Z
Apr 12, 2022
The solution is simple to use, but there are now many more wallets that are available in the market. I haven't explored other solutions. I would advise others to look at other solutions to have an overview of what features the others are providing before choosing. I rate Microsoft Azure Key Vault a six out of ten.
Cloud Architect at a marketing services firm with 11-50 employees
Real User
2021-08-17T13:05:00Z
Aug 17, 2021
I'm a cloud architect. If I don't see that Key Vault has been included in a proposed architecture, I don't approve it. It's a main ingredient in any cloud enterprise infrastructure and architecture. When you're using Azure, you have to have this or a third-party solution. If someone shows me a third-party solution, I have to ask, "What's the cost of owning this component that you're adding to the architecture? Is it included, like Key Vault, or do you have to pay for it like with HashiCorp Vault?" With Azure Key Vault you have something that is free, enterprise-level, global, and it just works. I don't know if we could survive without Key Vault in a cloud implementation and still call it a secure platform. These days, you have to have Azure Key Vault or some third-party mechanism such as HashiCorp Vault. You need something that addresses key management in your cloud environment. But why should you pay for extra resources, costs, and management overhead, if everything is managed by Azure itself?
Senior Lead Software Engineer Individual Contributor at a hospitality company with 10,001+ employees
Real User
2021-07-08T07:19:00Z
Jul 8, 2021
Follow the Microsoft official documentation for this solution. It is pretty straightforward and very well documented. I would rate Azure Key Vault as nine out of 10.
We are just a customer and an end-users. We tend to use the solution for our clients. For those companies that want to work with the solution, I'd advise that they consider the use of and integration with Azure's pipeline. Overall, I'd rate the solution at an eight out of ten. We've largely been quite happy with its capabilities.
Founder & Principal Architect at NCompas Business Solutions Inc.
Real User
2021-04-01T08:59:00Z
Apr 1, 2021
Overall, I would rate this solution at nine, on a scale from one to ten. However, if you're not looking to have your application tied to one cloud provider, then you should stay away from this solution. Once you are tied to a particular cloud provider, coming out of it will be very difficult.
Microsoft Azure Key Vault is a cloud-based data security and storage service that allows users to keep their secrets safe from bad actors.
Benefits of Microsoft Azure Key Vault
Some of the benefits of using Microsoft Azure Key Vault include:
Secure your secrets in a single central location, enabling you to control how your information is disseminated.
Keep your data away from bad actors. Application administrators can store their application’s security information away from the actual...
The solution's access policy is important. You can directly provide the kind of access you want to grant to any particular user or batch of users rather than monitor which particular user should assign which particular task and what things can be seen by which particular user. Those kinds of restrictions can be added directly using the access policy. You need to maintain the solution. If the credentials are getting expired, you have to provide an update on that. One person is more than enough to maintain the solution. Overall, I rate the solution a seven out of ten.
Azure Key Vault provides a very good interface wherein we can continuously change or recycle the keys seamlessly. This automatic mechanism is much better than the typical process of changing keys or certificates. The solution takes backups before the keys expire and informs us in advance when the keys will expire. There is something called rainbow keys. I can generate certain read-only keys that even the administrator cannot delete. The access control is very granular. I can provide access control on certain keys so that only a specific person can access them. We have deployed Azure Key Vault on the cloud in our organization. Azure Key Vault is the best solution for Microsoft users. If you use another cloud provider, you will have to find a solution that works across all of them. Overall, I rate the solution a seven out of ten.
I use the tool to manage application secrets by storing digital assets separately. My company puts the digital assets directly in the tool using the credentials. Azure Key Vault plays a key role in encryption in certain projects or scenarios in our company. In our company, if we want to apply some algorithms to encrypt our data, we store such data in Azure Key Vault and pull it manually from the solution later to encrypt our organization's data. My company doesn't exactly use the access policies in Azure Key Vault for managing permissions, but we do use it for the storage of our secret information. For managing our company's secrets, we use Azure Key Vault, but we don't use it for managing permissions as we use IdentityServer and other tools for such purposes. Azure Key Vault can integrate very well with other Azure services. Azure Key Vault is a good option since it is a secure and useful tool. I rate the solution a nine out of ten.
I would rate the overall solution an eight out of ten.
The most beneficial component related to cryptographic graphic key management stems from the auto-rotation functionality. The product comes with two types of access policies. The tool provides a conventional policy and Azure RBAC. My company mostly, you say, the conventional access policy and it has been working great so far. The product plays a crucial role in our company's security strategy. The product is easy to maintain. The product helps ensure compliance with our industry regulations since it meets most of the auditing and compliance rules. It is a secure solution that needs to have most of the policies and compliance rules. I would say that Azure Key Vault is a good solution, considering the security part. I rate the overall tool a nine out of ten.
The platform provides straightforward integration with most of the other Azure services. It has improved the compliance and auditing processes. Earlier, we had to either store secret information inside the application or develop a custom solution to comply with it. There was a high chance of the data getting corrupted as different people had access to it. I rate Azure Key Vault an eight out of ten.
Azure Key Vault is a cloud-based solution. Overall, I rate Azure Key Vault a nine out of ten.
Azure Key Vault is easy to use. It is a best practice and must be used within architecture implementation for security. I rate it an eight out of ten.
I rate Azure Key Vault an eight out of ten.
I would definitely recommend Azure Key Vault. It is very easy to use, especially for retrieving keys and creating secrets.
I rate Azure Key Vault an eight out of ten.
I would advise to construct the global scenario in alignment with their specific requirements. Overall, I would rate it ten out of ten.
I rate the tool a ten out of ten.
I am satisfied with the product overall. I would definitely recommend the solution to small companies planning to use it since it is quite straightforward. Overall, I rate the solution a nine out of ten.
We are a partner of Microsoft. We haven't exported or imported information in Key Vault. This solution is worth the cost and is useful to use. It's a service that can be used in multiple regions in Azure. They are mostly deployed in UK South and UK West. It can be deployed and used in other regions as well; however, we have data constraints. I'd rate her solution eight out of ten overall. Potential new users should consider the types of sensitive information they want to store and how they want to retrieve the information, and from where. These are critical to understanding as they will govern the configuration of Key Vault. You can deploy Key Vault both publicly and privately. For example, if you do it privately, you can ensure you will ensure it can only be accessed from within your environment, and that ensures a very high level of security.
I advise others to use the solution if they already work with Microsoft Azure environment. In such cases, they should not prefer integration with a third-party tool. They should consider other products if the databases are distributed to on-cloud and on-premises infrastructures. I rate the solution as an eight.
I would rate Azure Key Vault a nine out of ten. I recommend it as a good solution for those using Azure Cloud to host their services. The solution does not require any maintenance.
I give the solution a ten out of ten. The solution is self-maintaining. We have implemented EIS, and infra as a code, and incorporated a CI/CD process to automate the maintenance in our environment. I always recommend going to Microsoft Learn for its rich knowledge base. Azure Key Vault is an excellent solution for improving organizational security, and it offers great value for money.
Other service providers try to lower the prices, but it all depends on your development environment and your core skills. You are a bit more stuck if you are coding in .NET. If you go down that route, you can't easily move out to another service provider. Maybe you can go the route of adding a new team with a different service provider, but then you will need to mash it together. You would need to evaluate if that is a good option. We have about 70 developers and they are in different teams. They interact with third parties and they have different roles, including front-end and back-end developers. Each one creates services for different websites for different regions, to sell e-vape cigarettes. And we have team leaders who use it as well. There's a security team of five people responsible for the infrastructure of Azure, including creating new resources or whatever is necessary for the dev teams. There are also operations management and product owners who make decisions on schedules, what will be built, and priorities. Deployment and maintenance are part of the security engineers' work, to manage any issues. Sometimes the dev teams get involved with root cause analysis if something is going wrong with a web application. We have a team for certain maintenance tasks and requests. The biggest lesson I've learned from using this solution is: "Stay secure."
The solution is simple to use, but there are now many more wallets that are available in the market. I haven't explored other solutions. I would advise others to look at other solutions to have an overview of what features the others are providing before choosing. I rate Microsoft Azure Key Vault a six out of ten.
Other people's opinions of Microsoft Azure Key Vault seem to be quite good. I rate Microsoft Azure Key Vault an eight out of ten.
I'm a cloud architect. If I don't see that Key Vault has been included in a proposed architecture, I don't approve it. It's a main ingredient in any cloud enterprise infrastructure and architecture. When you're using Azure, you have to have this or a third-party solution. If someone shows me a third-party solution, I have to ask, "What's the cost of owning this component that you're adding to the architecture? Is it included, like Key Vault, or do you have to pay for it like with HashiCorp Vault?" With Azure Key Vault you have something that is free, enterprise-level, global, and it just works. I don't know if we could survive without Key Vault in a cloud implementation and still call it a secure platform. These days, you have to have Azure Key Vault or some third-party mechanism such as HashiCorp Vault. You need something that addresses key management in your cloud environment. But why should you pay for extra resources, costs, and management overhead, if everything is managed by Azure itself?
Follow the Microsoft official documentation for this solution. It is pretty straightforward and very well documented. I would rate Azure Key Vault as nine out of 10.
We are just a customer and an end-users. We tend to use the solution for our clients. For those companies that want to work with the solution, I'd advise that they consider the use of and integration with Azure's pipeline. Overall, I'd rate the solution at an eight out of ten. We've largely been quite happy with its capabilities.
Overall, I would rate this solution at nine, on a scale from one to ten. However, if you're not looking to have your application tied to one cloud provider, then you should stay away from this solution. Once you are tied to a particular cloud provider, coming out of it will be very difficult.
I would rate this solution a ten out of ten.
In summary, this is a good product and one that I recommend. I would rate this solution an eight out of ten.
I recommend this solution and would rate it an eight out of 10.