HashiCorp Vault vs KeePass

• 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.

Read full review

• KeePass offers us a simple to use interface to store our passwords in a centralized location.
• I particularly like the fact that it allows you to obfuscate the username/password.
• The feature for copy/paste the credentials is also a very handy ability that helps to save us time.
• The ability to include URL and expiration dates is also great to have.
• It also has an option to randomly-generate passwords for you.

Read full review

• Documentation could be better.
• The multiple key unseal process can be a problem if the need arises.
• It would make more sense if HashiCorp Vault combined with HashiCorp Consul to create a unique product.

Read full review

• Keepass is kept locally on your computer. It takes a cloud service in order to keep it current on multiple computers.
• Some websites do not work with the autofill feature in KeePass. Instead, you will find yourself on the reset password page. KeePass doesn't try to read the website before it pushes the autofill data.
• The file on your computer is encrypted, but it is local and fairly easy to find on your computer.

Read full review

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

Read full review

• Positive. All of our usernames and passwords for service accounts are in one convenient location.
• Positive. The ability to organize everything into separate locations/folders is great.
• Positive. Password generator makes it easy for us to generate a secure password for our accounts.

Read full review