AWS Secrets Manager vs. Google Cloud Key Management vs. Keeper

[AWS Secrets Manager] is really good at managing the secrets for each environment (stage, production, ...), and with a simple command, the users will get all the variables for running the project. Depending on the user role, they could just read and/or edit the variables on the Secrets Manager on AWS. This facilitates the management of the secrets.

Incentivized

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

I can only think of scenarios where Keeper is well-suited, in my experience. I work in small business (i.e., sole proprietor, 1 employee) environments and Keeper is well-suited to my needs. I imagine it would also be well-suited to multi-user environments, but would require a great deal more management and organization in such environments.

• Single source of truth for secrets
• Securely share secrets with colleagues
• Securely store secrets for services to access during runtime

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

• Ease of use. User find it simple and intuitive to use and I find they rapidly adjust to the software with minimal training.
• Single-sign-on. Super important and really makes things simple for the users and easy to manage for us in the IT team.
• Sharing features. We knew sharing was a key component of our password management solution. Keeper makes it easy for users and simple to administer.

Incentivized

• It could be good if a user can use a variable in the project but can't see them in the manager on AWS

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

• I find that Keeper could use some work with their desktop interface, a sleeker and friendlier user interface would definitely benefit them.
• Keeper doesn’t have a Security Dashboard, which makes it more complicated to evaluate the strengths and weaknesses of your passwords.
• The automatic web form filling is somewhat limited at the time, but im sure they will improve it soon.

Incentivized

It's just easy to use, plain and simple. It has the complexity and user-interface that gives you confidence in its build but the ease-of-use that keep things from getting too complicated. A huge plus when you have to onboard new members of the team or summer interns when you need them to step in and make orders on your behalf.

Incentivized

Because it is so good. It always works, has not crashed even in 3 years; I have a lot of data in it (never any problems).

Both AWS Secrets Manager & MS Azure Key Vault are pretty similar. They're the default secrets manager on their respective cloud platform.

The choice comes down to where your infra resides on.

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

I have used the Apple cloud, but if you forget your password into that, once again, you’re at the mercy of calling customer service. With Keeper, you can use the thumbprint option to log on, and there’s any of your needed passwords. It’s fast and simple, and you don’t have to wait online to unlock the app you’ve locked yourself out of.

• Costs are suitable
• ROI is positive

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

• The spreadsheets and printed papers being passed around the office with passwords on them have gone! This is a huge security hole plugged.
• Users actively use the software which says something - it is easy to use and intuitive. When software is not intuitive, it tends to not get used.
• It gives IT control over who does what with passwords, and while difficult to quantify it is certainly a dramatically positive impact on the organization.

Incentivized