G2

Denis R.

Information Security Manager

Enterprise (> 1000 emp.)

10/1/2025

"Deployment and usage of KeeperPAM"

4/5

What do you like best about KeeperPAM?

It is easy to use since it integrates directly with the Keeper Vault. The distinction between users and devices simplifies managing credentials and allows sharing access with others without revealing the actual credentials. For us, the main use case was being able to grant developers access to production environments only when necessary, which helps minimize potential attack vectors. Review collected by and hosted on G2.com.

What do you dislike about KeeperPAM?

The main difficulty I encountered was with the documentation. Although the system and its features are well-documented, the information is dispersed across numerous pages and sections, which often makes it challenging to gain a clear understanding of how the system functions. Review collected by and hosted on G2.com.

What problems is KeeperPAM solving and how is that benefiting you?

Our primary objective was to remove privileged access for developers on production systems. KeeperPAM allowed us to accomplish this by keeping access credentials under the control of the Infrastructure team, while still enabling on-demand access when required. The built-in session recording feature proved especially valuable for troubleshooting and monitoring user actions. Moreover, the use of ephemeral accounts significantly reduced the attack surface, as accounts are provisioned with only the necessary privileges and exist only for the required duration.

That said, there are inherent risks. Most notably, the KeeperVaults must be secured to the highest standard, as a compromise could potentially allow an attacker to circumvent the very security controls the organization has put in place. Review collected by and hosted on G2.com.