What is our primary use case?
We primarily use it to ensure that all our people store their passwords in KeeperPAM and do not have multiple sources for their passwords, including Excel.
We also share passwords through KeeperPAM for shared login IDs, like for our demo system. We do not allow people to store passwords on local machines. So it's for account management.
What is most valuable?
There are a couple of things. One is the BreachWatch feature. It's one of the most useful things because it shows us who on our team has weak or compromised passwords. So, it checks the passwords and helps improve them.
There's also a security audit that shows us how many passwords are weak and how often they're being changed. Some people haven't changed their passwords for months, even though applications force them to change every 45 or 90 days. So you can catch those issues and warn them.
Most applications allow for rotation, but some don't. I've seen people use the same password for years. At least Keeper tells us these passwords haven't been rotated, and we can warn them to change them manually since we can't force people to change the password.
What needs improvement?
We had some challenges with the initial setup.
For how long have I used the solution?
I have been using it for six to eight months now.
What do I think about the stability of the solution?
How are customer service and support?
I contacted customer service and support. They were able to solve most issues quickly, but the domain issue was a challenge for them, too. Eventually, KeeperPAM support and our IT team figured it out.
Overall, I am satisfied with the support.
Which solution did I use previously and why did I switch?
I have worked with password managers, but not an enterprise-level tool like this before.
We moved to Keeper for password security because everyone in our organization was using different tools. Some people were using their own computers to store passwords, and some were using Excel. It was a nightmare. We moved to Keeper primarily for that purpose.
How was the initial setup?
The initial setup was straightforward. The POC and initial implementation went smoothly. However, the final implementation was challenging because we had to roll it out to three different departments within the same umbrella, each with its own domains. The domain integration created a mess. It was a unified implementation.
The first implementation took about two weeks. But due to the technical challenges, the entire process took about 45-50 days.
What was our ROI?
It gives us more peace of mind from a security perspective. So, it has a relational impact.
What's my experience with pricing, setup cost, and licensing?
It's good value for money.
Which other solutions did I evaluate?
We looked at multiple tools like Teampass, Microsoft's product, and 1Password. We liked KeeperPAM for its user-friendliness, ease of implementation, and its ability to help us combine tools since our domain servers are spread across Google AD and Microsoft AD.
What other advice do I have?
I would recommend KeeperPAM to others. It's a great tool.
Overall, I would rate the solution an eight out of ten.