BeyondTrust Password Safe Reviews

I use Password Safe as a fully-fledged conventional PAM solution; for SSH and RDP brokering to servers, whether that's Linux or Windows, as well as SQL and Oracle.

I also use the product to publish applications using a jump box server and as a vault for user credentials to provide normal use and REST API through CI/CD integration.

We have active and passive appliances and an offsite cold spare.

The RDP and SSH session recording is good. The associated UI is  pretty straightforward, and Direct Connect is a good feature.

Integration with Active Directory is a handy feature. 

The CI/CD and REST API are also satisfactory; the solution has a full PAM feature set and they all work well. 

Password Safe is relatively straightforward to run. 

We use PowerShell and Shell scripting using the solution's libraries. We also use the .NET library, where I worked with developers to create .NET extensions for use in solutions built in-house. We used the product's software development kit to develop plugins to some extent, and mainly we integrated with the REST API for our Azure-developed CI/CD pipeline. This capability is essential because DevSecOps becomes a requirement at some point. We're dealing with privileged accounts to do releases, which must be carefully managed and require password rotation. Thus, we need a source system for these release management pipelines to provide passwords, allowing the user to continue with the following deployment steps. Highly privileged accounts, by their nature, require regular password changes, which is a critical element in our DevOps.

I'm not too fond of the Smart Rules feature, mainly because too many features can cause complexity.

There is a limited capacity on the appliance, which I wasn't informed about when I purchased the product. I can have a maximum of 150 rules per appliance; any more than that and rule processing becomes very complex, especially regarding password revision. Hitting a capacity limit you don't know about can be problematic. Ideally, we would not have a limited capacity, allowing us to be in a completely managed state with password rotation for every service account, not just the highly privileged ones.

The solution does not indicate an issue, but when we hit the capacity limit, rules can become erratic, resulting in password resets during the middle of the day when they're in use. This can be an issue, especially as there is no performance counter so we can track how close we are to the limit, nor is there an indication of when we cross it. This is an element that could use a redesign.

Another feature that could be improved is the password rotation schedule; as a financial organization, that's very important to us. We sometimes require the maintenance window to be on a Saturday instead of during the week. The solution gives the option for the fifth day of the month, the tenth day of the month, the first day of the week etc., but not more specific. I want to be able to set the rule that password changes only happen on a Saturday, for example, and I can't do that.

To compensate, BeyondTrust tells us we can write scripts to set the password resets. This needs to be improved because it results in additional work for us, and they could fix the small scheduling gap in their product.

The MSA element of the solution is fine; there are no significant issues implementing MSA with the interface. However, the interface can be somewhat complicated for admins, though not for end users. Precisely, when troubleshooting user issues, we encountered strange errors. We needed to go into the appliance log to understand what was happening, and the UI needed to be more intuitive to help us.

We were late refreshing the UI, so it had pretty old components until about 2020, and we experienced browser issues. After 2020, the UI improved, but the look and feel of the application are still dated. I carried out POCs for CyberArk and SafeGuard, and both of their interfaces are much better than Password Safe's. I liken the solution to a Toyota; it's a good all-rounder, and it isn't bad though it has some issues.

We had an issue with the Team Passwords feature: the privilege concept needed to be improved. There was no differentiation between contributors of privileged information and the consumers of it. Additionally, until very recently, there was no REST API integration with Team Passwords, so we couldn't publish secrets using REST API. This could have been better, as it meant we needed a different team for CI/CD and Team Passwords, resulting in some cases of duplication.

I've been using the solution for five years. 

The solution is relatively stable, though the stability could be improved as we often encounter issues of various kinds. As such, the tool requires a large team to manage it and stay on top of any problems that occur.

My experience with customer support has been mixed; the US and UK teams are the best, while the others could have been better. The UK and UK support staff are highly professional people who seem very close to the developers and have excellent knowledge of their products.

Some of our cases took up to four months to resolve because there is a difference between Password Safe, the software layer, and the UVM appliance layer, which BeyondTrust essentially treats as a separate product. There have been some significant problems with the UVM appliance layer, especially compared to Password Safe. The latter has some specific issues, but they are usually quick to resolve, whereas, with UVM, we can hit a dead end, even with support.

ROI is tough to measure, as the solution isn't generating profit. We implemented automation with CI/CD, reducing human effort and saving time on previously manual tasks. I can't tell if this has yielded an ROI, but we achieved a target in that we are more secure, our highly privileged accounts are rotated etc.

I rate the solution a six out of ten. 

The earliest version of the solution's interface could have been more intuitive, and we sometimes experienced issues with request check-ins and check-outs. However, the recent introduction of the Team Password feature allows users to collaborate and share passwords within a managed team. Some elements of this feature lagged in our first few weeks with it.

We used some of the solution's customization features, and it works fine; however, we had some significant issues when doing Discovery Scans. We encountered strange errors, especially on custom platforms, and it took a lot of work to understand the problems. As a result, we stepped away from customization as the issues around Discovery became extremely hard to deal with for us. 

We saw the benefits of using the solution very quickly, especially for the more basic elements at the beginning of the implementation. By targeting highly privileged accounts in the first round through the Active Directory, those can be up and running in two weeks maximum. The more complex and detailed configuration becomes, whether with discovery, dependency, or multiple-layer applications, the time to value increases correspondingly. 

I advise potential users to stay manageable and not try to do everything simultaneously. Build slowly and keep an eye on the capacity; only deploy with one appliance, or you are destined to fail and will run out of capacity fast. It's better to refresh the UVM appliance version every two to three years with a new image and migrate rather than upgrade because upgrading is the worst part of this product. It'll cost money to keep migrating to newer appliances, but it's worth it to avoid the experience of upgrading.

Our use case was allowing users to connect with their regular, non-privileged user ID and automatically connect to a designated privileged account for target systems or databases. This prevented users from using their regular account as a privileged account. Instead, it used a managed, dedicated account in BeyondTrust Password Safe that only that the user could use. For example, my account "Gary.Jolley" might have a domain admin account "dam-Gary.Jolley" that I'd automatically connect to.

The most valuable feature is the architecture capabilities, which allow designated server components for high availability and failover. It works well with identity and access management solutions, allowing users to be automatically onboarded and offboarded. The account mapping feature makes rollout seamless. The session monitoring capabilities are excellent, with keystroke and graphical monitoring. This enhanced our security posture by providing detailed accounts of user actions. It helped us pass our SOX audits.

The only improvement I could suggest would be standardizing documentation, but that's more the responsibility of the implementing engineer rather than BeyondTrust Password Trust itself. The documentation must be specific and narrow for implementation, not just broad guidelines.

I have been using the product for four years. 

BeyondTrust Password Safe is incredibly stable. During initial server implementation, some processes might appear to hang, but they're actually communicating with each other. It's very intuitive.

On a scale of one to ten, I'd rate the scalability as nine and a half. BeyondTrust Password Safe's scalability allows different roles and strategically placed servers for better failover. We had thousands of end users across our sites.

The technical support is phenomenal. They were available even for middle-of-the-night outages during scheduled updates.

Positive

BeyondTrust Password Trust's main advantage is its network architecture implementation. It's similar to CyberArk, but CyberArk has some features, like privileged threat analytics, that the solution doesn't.

The initial setup is straightforward if you understand network architecture. Four people helped with deployment across five international locations, taking about two to three days per site after documentation was created. It requires weekly maintenance, which can mostly be done automatically, but some updates need manual triggering. One person could maintain all five sites, and we often assigned this task to new employees as the process was well-documented.

The use cases are essentially the same as those for any PAM solution. Like addressing security compliance, securing the network against threats, and protecting all identities with intelligence and minimal concerns.

It also includes cloud security management, handling different shifts, and addressing workforce access, passwords, and the likes of compiance. It simplifies analytics, reporting, and secret implementation.

Additionally, it reduces servers while increasing stability in privileged access. These are the general use cases that apply to all PAM solutions.

BeyondTrust Password Safe provides proper security for your network. Its primary feature is identity governance. It allows you to manage your users effectively and implement robust governance. The solution includes reporting, which aligns with the National Security standard and enhances cybersecurity resilience.

This protection safeguards against attacks. When discussing the management of essentials post-classification, BeyondTrust Password Safe also assists with this. It plays a critical role in preventing cyber identity theft. Without BeyondTrust Password Safe, your system is more susceptible to identity theft. It's an all-encompassing solution that significantly reduces such risks.

BeyondTrust Password Safe is specifically designed to limit cyber identity theft. It's highly effective in preventing incidents of identity theft.

It is very easy to deploy. It's easy to use. That's the major thing I like about it.

It is very easy to set up. It is very easy to deploy. Depending on the environment, it can be deployed quickly. So it's very good. I like it.

The deployment model depends on the customers.

The solution was implemented to secure privileged access management in a large-scale corporate environment.

Privilege access management protects the accounts that have administrative privileges and secures those in a secure and encrypted vault so that they are secured and protected. Not having the credentials "on the wire" is only one part of what the solution offers. If the credentials are exposed on the network, they can be exposed to various vulnerabilities and increase the attack surface areas.

Protecting privileged accounts reduces the attack surface area. It is estimated that around 70% to 80% of all compromises in cybersecurity are due to unauthorized privileged credential exposure, either by lateral movements or phishing attempts. By securing those accounts, we tackle a significant part of the problem. 

Additionally, knowing who, when, and how the privileged credential is being used via the reporting and analytics module allows visibility into a previously unknown area.  

The actual innovations offered by the vendor stand out to me. They are quick to respond to market demands and the changing environment of privileged access management. I see BeyondTrust Password Safe as an innovation leader compared to some of the other vendors in the market.

Documentation is the primary area of improvement. Their documentation has improved over the last three to five years, but there's still room for improvement. A more intuitive search and not having disparate documentation categories would be helpful.  

While they are quick to market for improved features, there are still additional features that other vendors have that they don't have like a credential injection for the users' web browser extension.  

I have been using this solution since 2013. 

The solution is very stable. Part of my role is to design and implement disaster recovery and business continuity planning. Although planning is important, these are rarely put to use.

The solution is very adaptable. The solution can be deployed in environments with a single domain and then scaled up to handle multiple domains positioned globally as well as adding cloud security. 

Customer service and support are great! 

Positive

I worked with Delinea, which used to be called Thycotic and CyberArk.

The decision that clients typically make to choose BeyondTrust is often from a proof of concept (PoC) or through an extensive advisory engagement. One differentiator is shown between a user-centric environment versus an asset-centric environment. The two clear differences between BeyondTrust and CyberArk are that BeyondTrust is more asset-driven, while CyberArk is more user-driven. Both have their advantages, but it depends on the workflow and architecture that suits the client.  

As a person that has been involved in multiple deployments of BeyondTrust Password Safe for various companies, I can say the initial setup is fairly straightforward. 

In-house deployments can be challenging and so leveraging a delivery provider that specializes in PAM deployments provides numerous benefits. PAM/IGA/IAM are unlike many other security solutions as it has their own language and unique demands that are often not as intuitive. Knowing how to overcome project crawl, analysis paralysis, adoption challenges, and executive buy-in can be helpful.  

The ROI can be quickly realized for BeyondTrust vs. some of their competitors. The ease of implementation and the speed to get that initial return on investment is impressive.  

With the BeyondTrust solution, you have the capability to deploy the more secured layered solutions such as Secure Remote Access (SRA), Endpoint Privilege Management (EPM), and Identity Security Insights (recently released this month) that are all designed to protect the entire enterprise.

BeyondTrust has migrated towards subscription-based licensing/annual renewals. They remain competitive and on par with their pricing, often coming in under other competitors. Pricing is one of the reasons clients choose BeyondTrust, but it's not the only reason.

Overall, I would rate the solution an eight out of ten. 

One of the more important areas to focus on is knowing your environment pertaining to the assets and accounts before deployment is attempted. Not knowing what needs to be protected will make the deployment more challenging. Although BeyondTrust excels in the discovery of assets and accounts, knowing WHERE to look can be challenging. 

Deploying the product using only a percentage of its capabilities can lead to frustrations and reduced ROI. Not managing service accounts, networking, and database teams that are typically more challenging can lead to vulnerabilities as well.

You can't just focus on privileged access management. Privileged Remote Access, as well as solutions such as endpoint privilege management, are all part of a complete identity and access management solution that must be designed and deployed correctly. If not designed and deployed correctly, it will have the opposite of making the environment secure. 

Least privilege, zero trust, and cloud security awareness are all buzzwords we see often. Privileged Access Management (PAM) is a part of the layered security approach that will keep your company out of the cyber news headlines. 

We use the solution as a password safe to keep the privileged credentials secret to make sure they aren't stolen or lost.

We don't have to remember passwords. It's automated. There is a rotation of privileged passwords, which keeps me from memorizing things. 

I like that I don't have to memorize passwords. The whole process is fully automated.

Advanced auditing and forensic features are great.

It simplifies your compliance and tracking to benchmark other credentials and analytics.

The solution can scale.

Their support is not good.

The extensible API is the feature that I like to learn. However, we aren't using it at the moment. 

It has crashed on us in the past.

I've used the solution for about a year.

I'd rate stability six out of ten. It has crashed a couple of times on us.

The solution can scale. I'd rate the scalability eight out of ten. 

We have a user base of less than 250. We do not have plans to increase usage. 

We were down early Friday, and we tried to get a team to help us. It took a whole weekend. They need to be better at supporting and helping fix issues quickly.

Neutral

We previously had other solutions, including Tenable. 

I was not part of the initial setup process. 

We have a three-year license.

The pricing isn't part of my scope. I don't directly deal with licensing.  

We are using the latest version of the solution. 

It's important to do a POC for over a month and negotiate on the pricing. There are other powerful tools that are out there that are easier to use.

Your deployment tends to involve other tools, so check its ability to integrate with them.

I'd rate the solution seven out of ten. 

We deploy in client environments. It's not deployed in our environment. Generally, its deployment depends upon a client's environment. Sometimes, it's hybrid. Sometimes, it's on-prem, and sometimes, it's on a virtual hypervisor or VMware.

We are currently deploying it for one of our Indian clients. For this client, we are deploying SaaS-based Password Safe, which is purely on the cloud. They also have BeyondTrust Remote Support. We are integrating both of them. BeyondTrust Remote Support is for tech support for their teams, and Password Safe is for password rotation, screen recording, and monitoring of their employees.

It helps to automate password rotations and manage privileged accounts. If your employees are supposed to rotate passwords for some period of time but they are not doing that, you can automate that.

It provides ultimate security through automation and Smart Rules. You can enforce password policies and access policies. For example, you have local administrator accounts on local systems. If you didn't write any Smart Rules for the local administrators, any employee with administrator privilege can make an administrator account, but that account will not get detected in our system. With Smart Rules, Password Safe can detect that administrator account and onboard and manage that account through an automated process.

The database team of a client had scripted or hard-coded passwords for databases. We were able to use the API scripts provided with the BeyondTrust Password Safe to retrieve the passwords. The database team had already written a script for database login. So, anytime the database team wanted to log in using that script, the password was retrieved from BeyondTrust Password Safe vault.

They offer a jump server or terminal server where we can configure the databases or other applications. A lot of customers have in-house applications, and even products such as CyberArk or Saviynt CPAM do not provide connectors to those because they are not common. BeyondTrust provides some flexibility there for application integration. We can write our own scripts. We can do scripting in our way and integrate it with any application.

Its user interface is easy to use. I also work with other non-PAM solutions, such as SailPoint and Oracle, and as compared to those solutions, BeyondTrust has a very user-friendly interface, and everything is also very well documented.

Screen recording is valuable, and integration with applications is easy. We can customize whatever we want. We did a lot of application integration using scripting.

We don't have much control over the appliance. When anything happens in the backend, we have to depend on the support team. We need to raise a case so that they can update the appliance. If we have control over it, we would be able to troubleshoot easily. 

They can improve application integration. They can provide out-of-the-box connectors for common applications so that we don't need to do the customization and write scripts from scratch for lots of applications. They can provide an application catalog with pre-configured connectors.

It has been two and a half years.

It's pretty stable. From version 21 onward, it has been more stable.

It's scalable. We can add as many active-active appliances. If the number of users of a client increases, we can increase the active-active appliances anytime.

One of our clients from the Middle East has a big environment with almost 55,000 users. That's our biggest client. There are also small-sized and medium-sized clients.

Their support is pretty good. They are available for any issues. I would rate them an eight out of ten.

Positive

I used CyberArk and Saviynt CPAM, but BeyondTrust Password Safe is better than both of them. CyberArk is the leader, but BeyondTrust Password Safe can easily take the position of CyberArk.

BeyondTrust Password Safe provides flexibility for customized application integration. BeyondTrust also provides lots of other solutions for remote support and privilege management for Windows, Unix, and Linux. We can also manage Linux servers in the Active Directory domain by using BeyondTrust AD Bridge.

Saviynt also has good capabilities. They don't have a very mature product for privileged access management, but with IGA, they're providing privileged access management, which is a plus point for them. 

BeyondTrust provides a single appliance with everything we need to deploy in the cloud. Nowadays, they're providing UVM appliances, UVM20 and UVM50, which are user license-based. We just need to do network configuration and minimal appliance configuration, such as default settings, threshold settings, etc. Deployment is very quick and easy nowadays.

Generally, the deployment takes a week, but it also depends on a customer's requirements and environment, such as whether they have a high availability environment with two or three appliances, whether we need to open certain ports, and whether we need to integrate with a database for session recording storage. Configuration of a single appliance only takes one or two hours, but there could be some delay from the client side in taking care of all the dependencies, such as opening required ports. That's why we keep one week for deployment in our plan.

Our implementation strategy depends on the client's environment. It depends on how the client wants the environment and whether they want high availability.

I have not handled the process of migrating end-users to Password Safe, but a colleague of mine has handled migration from CyberArk to BeyondTrust Password Safe. It was not very difficult. They could easily do it.

One person can do the deployment and administration of basic things for a mid-scale or small-scale client. It also depends on a client's requirements. If a client wants it done in a short time, we would need another consultant, but generally, one person can easily do these tasks.

You can follow its documentation for implementation. BeyondTrust has documented everything very well. They have clearly mentioned the port requirements and system requirements. They have good training resources on their website. You can easily follow them.

I would rate BeyondTrust Password Safe a seven out of ten.

We're using it as a vaulting solution. We're doing password vaulting, and we're doing password rotations. We also do session management and session proxies.

We probably are using version 7.2. 

From a management and audit perspective, we've seen a lot of improvement because now, we're secure in the sense that we know where that access is coming from, and we know who is requesting the access. From that perspective, we're very happy, and it has provided a lot of value, but from a user perspective, it has been negative. When we talk to our frontline guys, who actually use this solution, they're not too happy with the whole solution itself only because they feel that it has added a step in their whole process and procedures.

We use PuTTY, and we didn't find it very difficult to integrate session management into existing business processes. It was pretty good. It all comes back to how you would define the users and how you define the administrative access. If sudo and those types of things are kept out of the picture, then by getting access to a privileged role or group or SSHing into a session with the root privileges, they're able to do everything they need to do without having to go through the virtual model of sudo to access something. The seamlessness was that they didn't have to go and make that connection happen. It was just all integrated within the solution itself. They just click on the asset that they wanted access to, and it would provide SSH access to that system.

So far, we have been able to integrate session management without disrupting business processes, at least for the assets that we've been on. That's very important to us. The main feature is the session recording. If we can continue to have session management, and we get those session recordings, that's the key for our auditing team.

The vaulting features are valuable. 

It provides integrated password and session management in one solution, which is important for us because, from an auditing standpoint, we are accountable for the type of access being used. We need to ensure that accounts are securely stored and there is the right type of accountability around who is gaining the access. After gaining it, how they're using it, where they're using it, etc.

In terms of intuitiveness, the UI for a generic user is good. I wouldn't call it great because, at times, some of the capabilities are difficult. While trying to get to the password itself or trying to find the asset itself, it sometimes gets difficult to narrow down or identify which asset you can get credentials for. There were some search features and the ability to have a favorite, but in a lot of cases for our user community, it wasn't very useful.

The RDP access needs to be improved. I wasn't very keen on that. It downloads an RDP file every time you want to access the solution. It builds up these sessions on your laptop. That was one of the pain points that a few of our administrators had talked about.

Named accounts don't work well in this solution. If you use named accounts for your administrative access, the way Smart Rules work is that it takes your SAM account name and matches it to the account name of your privileged ID, which creates limitations on size and how big those names can be because the directory has a 20-character limit. 

I've been using BeyondTrust since 2018. So, it has been about four years.

It is very stable. It is good. We haven't had any major incidents with the product.

It is good. It is very easy to add new VMs to the solution and integrate them with the existing hardware. Scalability is very easy.

To date, if I remember correctly, we have 200 users as administrators using the solution today, and they are the domain admins from a Windows perspective and the root access administrators on a Linux box.

Its usage is not as extensive as the organization first hoped. They are not planning to make it any larger than it is today.

I didn't like it at all, but that was about two years ago. I'm not on the site anymore. I was the architect, and during the time of implementation, there were things on which our developers had more input than the BeyondTrust team. I would rate them a five out of ten.

Neutral

In the organization I'm in, we had CyberArk previously. We made the switch because there was an initiative to improve our stance on privileged access management, and the CyberArk solution that was deployed wasn't kept up to date. It was outdated and needed to be upgraded. 

It was a real competition between CyberArk and BeyondTrust, and the company eventually chose to use BeyondTrust. Between CyberArk and BeyondTrust, there were no real big differences at the time. Both of them achieved whatever goals that we wanted, but it was really a cost factor. BeyondTrust was significantly cheaper than CyberArk at the time.

We didn't deploy in the cloud. We deployed on-prem. It was a VM image that they provided to us. It was a huge factor that it was so quick to deploy, and they gave us that VM image. We went into VMware and created a space where we could deploy that image, and it was ready to go.

The initial setup was pretty straightforward. We needed their help a little bit, but for the most part, it was pretty straightforward. Their documentation was good at guiding us through. It mainly had the configure/next type of screens. So, it was a lot easier to implement and deploy.

In terms of duration, the server build wasn't very long. It took us a few weeks up to a month at the max. However, the actual implementation of getting the accounts in, identifying privileged accounts, and getting all those things sorted took roughly about a year and a half. 

We didn't have to go through the migration strategy. So, it didn't apply to us. We have gone through an upgrade process with Password Safe. It was much more difficult than the actual setup. It wasn't as easy as we thought it would be. There were a lot of components. For example, the database required special scripts to be run against it. That was more complex than we'd like. As per my Ops teams, the biggest issue was some of the coordination with database teams because when the upgrades happened, there were some schema changes or custom changes on the database that had to be implemented. Coordinating these changes was a bit difficult, but application-wise, the solution itself wasn't very hard to upgrade.

We used BeyondTrust and Optiv. Our experience was interesting because midway through, the BeyondTrust resource that we had either left or was let go, but we had continuity after that. Depending on who you talked to, it was mixed in terms of engagement.

For maintenance, we have a centralized identity management group that manages a solution, and then we have a database group that helps. Altogether, there are roughly about five resources to keep the solution up and running.

You see the value in it based on your data leakage and your ability to secure privileged access to the systems. I don't know if you see a real value right off the bat, but the biggest value you'll see is on your auditing side. After a year, during the audit, the audit team will see its benefits.

At the time, BeyondTrust was significantly cheaper than CyberArk. Pricing-wise, if I remember correctly, it goes by assets. The pricing was negotiated for our instances based on the number of assets that we onboard into the system. It is a little different from CyberArk, where the pricing is by users. So, it depends. If you have a lot of assets, it can get very expensive.

We also evaluated the CA solution. The reason why the CA solution was immediately taken off the shelf was that a client was required on every desktop. That was one of the main reasons why the organization didn't want to go with that solution.

The biggest lesson that I have learned from using this solution is that named accounts don't work well in this solution.

My advice would be to really understand your use cases. If you have use cases that are specifically for named access where your privileged access is not shared but it is named to specific users, then you might want to look at their Smart Rules capability and what it can do. If you're using a shared pool of administrative access and you're reusing privilege access from that shared pool, the solution beats everyone out there, hands down.

We haven't used the Team Passwords feature to securely store credentials owned by small groups outside of traditional privileged user roles. It came up afterward, and we haven't yet implemented it here. We also didn't try to customize anything because we try to go out of the box as much as possible.

I'd rate it an eight out of ten.

We use this solution for password management. It allows us to control and manage passwords in a safe and secure way, and it records sessions.

The solution is deployed on-premises. It's being used extensively in my organization.

Before implementing BeyondTrust Password Safe, our server engineers and database engineers were storing passwords on an actual sheet, which is a plain text password. Since implementing BeyondTrust Password Safe, they're not doing that anymore. We eliminated the risks from storing passwords on plain text. We also have clear data that shows who modified a file.

We use the Team Passwords feature to securely store our passwords. Our team has a lot of shared passwords. Those passwords were shared in SharePoint or in the common share folder. We wanted to eliminate that because it's a risk. Team Passwords lets us securely save a password that's shared between a group of people so nobody else can see it. It's secure, and we don't have to save the password in an Excel sheet.

The Team Passwords feature has affected our level of security in a completely positive way. With a shared password, everybody could see it and someone could log in and change the password. They could also share it with someone else, like a third-party vendor or with someone outside the organization.

Team Passwords gives us better control over our passwords. Someone outside the team isn't able to get the password. Even if it's shared, we're able to see who checked the password.

It's more secure to use and better than using Excel or Notepad to save passwords. It's a really good option.

I like the session recording feature. I also like the analytics and reports. You can pull up a report, and the UI is fantastic. The system is recording when nobody's there, so we have a record of what's happening.

The Smart Rules feature is one of the coolest features. It allows us to automatically onboard accounts based on the criteria instead of manually onboarding. It allows us to manage assets or accounts based on the criteria we search for in Smart Rules. 

The UI is cool. They have different symbols and icons. I think the UI is better and more informative than other solutions.

The customization features help me manage most assets, databases, and applications. It's more than sufficient for us. The default connectors and plugins are capable of managing the database in the server, units, and systems.

The banners could be improved because they aren't informative. For example, if something is not correct and I open the error notification, the dialogue box simply says, "This is an error." It would be great if they could provide some valuable comments about how to fix the errors. If I try to remove something, the error box says it cannot be removed, which isn't helpful. I have to wait for the account to check in, and then it will be removed. 

The information description in the logs and the error reporting could be improved. For someone who's inexperienced, it's hard to understand.

I have used this solution for more than three years.

The stability is really good. Our setup is Active/Active, so we have more than eight appliances, and everything works well. It might differ for companies that decide to choose Active/Passive and only have two appliances. 

We have enough appliances in our organization, so we don't feel that the stability is lagging.

The scalability is good.

I would rate technical support as nine out of ten. 

Technical support is really good. If we need help, we contact somebody from the customer portal. We don't need to wait. We get a reply from an engineer right away, telling us what we need to do. If somebody's not available, a senior engineer will respond.

I'm amazed by the response time. They are as quick as possible. They have enough support people across the globe.

Positive

Before using this solution, I used Hitachi ID PAM.

There are multiple reasons why we switched. They don't have 24/7 support. We're on Asia Pacific Time, but most of their technical support staff are in Canada and the United States. If something happened in our time zone, they weren't available. Their product is very expensive, but they don't have as many features as BeyondTrust.

Comparatively, BeyondTrust has a lot of features and database inclusion. I would say BeyondTrust is 100 times better than Hitachi ID.

The setup isn't a complex process. There are two different setups. They provide the UVM-based installation and software-based installation. We selected the UVM-based installation.

The installation itself is pretty easy. The documentation is very structured. It's not complicated.

Migrating end users to Password Safe was hard in our case because no one in our organization knew about the solution. People were using Excel or Notepad and manually changing passwords. We created an internal document system, but migrating the accounts was a difficult task. As soon as the host was set up, it was pretty easy.

It's easy to maintain. All our appliances are connected to the internet. We receive patches and updates directly from BeyondTrust. We don't need to ask anyone to provide an update or patch. It's up to us to choose and schedule a proper time for updates.

We did the implementation in-house, but we had a consultant assist us from BeyondTrust. We had a good experience with him. 

We have definitely seen ROI. It's worth buying.

We only pay for Password Safe. Session management is included, but we don't use it. 

There aren't any additional costs besides the standard licensing fees. We pay for an annual license.

We also evaluated CyberArk, but we chose BeyondTrust because of the cost. It's affordable compared to CyberArk.

I would rate this solution a nine out of ten.

The installation is straightforward. If you just follow their instructions, you don't need any experience. They also provide automated ways to onboard accounts. The documentation is very structured.

We use the solution to login through remote application solutions. 

The product has improved security and login due to the system recordings. In case, there is a doubt that someone has done something which they shouldn't have been doing, we can just go back and check what the user actually did. 

I am impressed with the product's session-logging features. We can also do multi-factor authentication with the product. 

We face screensaver timeout issues and problems with the server. I would like the product to include a server visibility feature. 

I have been using the solution for a year. 

I would rate the tool's stability a seven out of ten.

I would rate the tool's scalability a seven out of ten. If we need to add more users, then we need to add more servers to the environment. Around 500-600 users use the tool on a daily basis in my company. 

The technical support is through our vendor.

Neutral

The solution is difficult to setup due to settings. You need a specialist to configure the product. I would rate the solution's setup a five out of ten. We have two people involved in the tool's maintenance. 

I would rate the product a seven out of ten. 

We primarily use the solution to keep passwords.

The solution offers session monitoring and has a good connection profile. It directs users to specific commands that our organization needs.

The user interface is very nice.

The performance is good. It does depend on how much you are giving to the appliance, however, we've never had any issues.

It's quite interactive.

It's stable.

The solution can scale.

Technical support is helpful and responsive.

We'd like to have incremental backups to ensure the solution's information is protected regularly.

I've been using the solution for three and a half years. 

The solution is stable, and the performance is good. There are no bugs or glitches. It doesn't crash or freeze. It's a very mature solution. 

The solution scales well. I'd rate the ability to scale eight or nine out of ten. We've seen that customers have 120 or 130 users, and they are using it as active-passive. They can also convert it to active-active, and it's fine. It can support more users as well. They can go up the 150 or 155 with no issue. 

Depending on the use case and the willingness of the customer, it can work well for a wide variety of companies, from small to large, including enterprises that can easily buy and implement it. 

I've dealt with technical support in the past, and they are quite good. When I had a critical case, they were available within half an hour. 

I am working with another solution. I've found other options aren't as stable. 

The implementation process is quite simple. I'm using it on-premies, however, they also provide a cloud version.

Having the prerequisites ready in necessary as it does require those for the service account, and often customers don't have that ready. 

We can implement the solution for our clients. 

I'm not aware of the exact pricing.

I have not compared the solution to other options. This is quite an exceptional solution, and I've been happy with the products.

We are partners. 

I'd rate the solution eight out of ten.