Devolutions Server vs. HashiCorp Vault

We love using Devolutions Server as our Privileged Access Management solution! We were able to use it initially for our Information Technology team and after that, we expanded the use to other teams outside of IT, like our Database Admins, etc. Integrating Devolutions Server with Remote Desktop Manager allows our Systems Admins & Engineers to support our environment without having to keep passwords in an Excel file or on Post-It notes! :)

Vault is a reliable and resilient as the Key Management System. It is not for the novice user that does not have a background in information security. It requires a significant time investment into the different key engines that the solution offers to get started. It works very well once implemented and is very flexible in general.

Incentivized

• Multiple way to access your data
• Easy server management
• Of course easy and secure access/storage of your data

• 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

• We would like to see some additional reporting options.

• Documentation for the API moves slower than changes in the API itself
• The database secret engine's API design isn't as elegant as it could be
• No support for revocation of all secrets under one path

Incentivized

I think that we will stick with this service for as long as possible.

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

They don't have the same "Server" option as Devolutions, so you can only access data from the computer program.

HashiCorp Vault integrates with a lot of tools and systems, and the documentation was pretty robust with a lot of community help. Because HashiCorp Vault is also older than other solutions, it is already well developed with a lot of features you need for storing secrets and configuration. HashiCorp Vault is also friendlier towards application build and is focused in providing security and a lot of customization for almost any use case scenario. Bitwarden is more limited to password management of enterprise accounts, but for application usage is not that great or easy to integrate. It does not scale well also. AWS Secrets Manager on the other hand is really good but more limited to AWS applications and vendor lock is problematic as well for such a critical piece of infrastructure.

• ROI was higher when I used the password server
• The time to set up took a while since the importing from out password vault would not work properly
• The server worked quickly reducing our response time

Incentivized

• Allowed better access control for credentials, passwords, and important keys.
• After we started using HashiCorp Vault, we were able to base our environment 100% as code.
• SSH access control that is possible using HashiCorp Vault adds an extra level of security in environments where external remote access is required.

Incentivized