AWS Identity & Access Management vs. Keeper

AWS Identity & Access Management is well suited to managing AWS application access between services. Very helpful for both third-party products and in-house developed software. Very happy with how easy it is to create access keys and then share them in our environment. AWS IAM can also be used to manage individual users, but I highly recommend using AWS SSO for that purpose instead. Much easier to deploy for console access and from a security side easier to turn off in one click from your SSO provider.

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.

• Customized access per key to limit scope
• Safely distributes access keys
• Provides access audits

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

• Better integration with roles and policies so you don't need three windows open to create a new IAM user
• Display recommended configurations based on services being used
• Easier options to base config on existing users

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

We would be unable to manage the interconnected nature of our AWS services without AWS IAM.

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

While we do not use Microsoft Azure for our servers and other customer-facing services. If we did, we would have to use Microsoft Azure Active Directory to manage access to services appropriately. It's difficult to quantify the differences between the services as they are truly different. I would recommend choosing AWS or Azure, then using the identity management provided by the same vendor.

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.

• Without IAM, it would be difficult to use AWS across services. Increased ROI

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