BeyondTrust Password Safe Reviews

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 BeyondTrust Password Safe for server and database management of the accounts noted. We will be moving ahead with application management as well.

BeyondTrust Password Safe has good reporting and Smart Rules which makes it easy. Though Smart Rules are easy, those who do not have much experience with such things may find it difficult to understand how it works. Otherwise, I find Smart Rules very easy to work with.

There are multiple features that have issues, although they could be specific to our environment. What we have seen is that whenever a user gets added to the authentication store, the sync between Password Safe and the authentication store, which is generally easy, takes a lot of time. It does not occur immediately.

This is persistent for Password Safe used by administrators who require immediate access. If immediate access is not possible, then access should be made possible at least within one hour or so. This does not happen in our environment. The access takes more than three to six hours to happen.

Whenever a new end user is provisioned for access, it would take twelve hours to twenty-four hours. Since they are end users, the time taken is fine. However, when we consider administrators, they might need access at different times. The three-hour time frame for the administrators in our environment is a lot of time.

I have been using the solution for more than one and a half years.

I would rate the stability of this tool as seven out of ten because of the immediate access.

The scalability is good and I would like to rate it eight out of ten. We have around 1200-1500 users.

The support that we have from BeyondTrust is good.

The setup for BeyondTrust Password Safe is not so easy and not complex as well. They have documentation available.

I had compared many vendors sometime back in 2019. The other vendors have either added new features or merged with others.

I would rate the solution an eight out of ten. I would recommend it for monitoring.

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.

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.

Positive

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.

BeyondTrust replaced the leading password management solution, offered vulnerability management and gave me a third-party patch management that integrates with Microsoft. To me, that was a win-win. 

It improved our overall return on investment by at least two-fold and gave us more intelligence on our assets than we expected.  

The sharing of intelligence gathered by scanning, and data warehouse cubes on the backend that gives us the ultimate visibility into our assets. 

I would love if they integrated Bomgar's SSO with BeyondTrust for the session recording that we use for vendors. 

Less than one year.

It has no problems. It's very flexible.

It will scale and has a built-in capability to augment expansion via external databases. 

Support has been very very good. 

We used CyberArk, and we found for an SMB that the product required more FTEs than we could handle. CyberArk is really meant for 100K FTE enterprises and requires a serious.

It is a complex product that has a lot of capabilities and does take some learning. They recommend taking their foundations class to understand and get the most out of the product. 

Very good.  (A-, or B++).

Good

Talk to references, look at Gartner and the positive and negative comments. BeyondTrust has the least negative comments of all the products and ties vulnerability management, scanning, password management, session recording, inventory management, intelligence gathering on attached assets. And when you look at all this together and price out separate options, the TCO is easy to justify. 

CyberArk's password safe.

It is a steep learning curve, but once automated, it makes your life a lot easier. 

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. 

The use case was to integrate BeyondTrust with the organization and onboard servers and accounts. We created Smart Rules and used other features for automatic onboarding and integrating BeyondTrust with various components in the organization, such as SNMP, SIEM, and AD.

It reduces risks. Beyond Password Safe manages all privileged credentials. It takes care of the automatic rotation and connection to the target servers. It reduces a lot of risks of cyber attacks, malware, and ransomware.

It is very important to us that Password Safe provides integrated password and session management in one solution.

Its customization features help us to manage most assets, databases, and applications. With the plugins and customization features, we can connect to databases. We can also connect to Windows and Linux. When I worked with it in 2018, we also had to use one of the plugins to connect to a mainframe. It supports a lot of different platform connections.

The Direct Connect feature allows us to use existing tools such as MobaXterm, PuTTY, or SecureCRT. There is a feature that power users can use to connect to the log server every day. This way, they don't have to go through the web portal. They can just connect to their target server by using MobaXterm, PuTTY, or SecureCRT.

Smart Rules is a nice feature in BeyondTrust. It is a unique feature that BeyondTrust has as compared to other vendors such as CyberArk. With Smart Rules, you can do automatic onboarding of accounts. There are a lot of options and features. For example, you can do onboarding based on different AD attributes. It is a nice feature in BeyondTrust that some of the other PAM vendors don't have. With other vendors, we have to create our own scripts, whereas, with BeyondTrust, we can just use the in-built Smart Rules.

In terms of the intuitiveness of the user interface, I find it to be pretty good as compared to the other products. It is user-friendly, and in terms of the looks and feel, it is one of the better ones.

I find it a little bit confusing because you have the management console, and then within the management console, you have access to different admin consoles. There are probably two or three different ones. I wish they would place all those different types of consoles into one main one so that we don't have to access two or three different consoles to do the work.

When we deploy BeyondTrust, we have to deploy our own database on a SQL server. It doesn't deploy the database. I wish BeyondTrust packages the whole solution in one and includes the MySQL database so that when you deploy it, it deploys everything for you. BeyondTrust gives you the software, but you are in charge of setting up your own database. It is a single appliance just for the BeyondTrust portion but not the database. Unless that has changed in later releases, you have to set up your own database for BeyondTrust Password Safe. I find that part complex because we then need the expertise and help of the database team to set it up, which also increases the deployment time. If they can deploy the database, it will reduce the deployment time.

Their documentation is not very detailed and thorough. In case of any issues, a lot of times, we have to go through their professional service. They need to update their documentation and create a good knowledge base for us so that when we run into problems, we can go there and search for common issues or problems.

I have been working with this solution for about three years. I have used it on and off depending on the companies I worked for.

It is average because we did have issues with some parts of the solution.

Its scalability is good. It is very scalable. We didn't have too many users because we switched over to CyberArk after two years, but the plan was for 500 end users.

We don't have plans to increase its usage because we switched over to Cyborg earlier this year.

Their documentation is not very detailed. A lot of time, we have to go through their professional service. We do get really good people, but they should provide more and better documentation and knowledge base so that we can solve a lot of issues on our own instead of going through their professional service.

Their professional service or technical support is very good. When we opened a case, sometimes, they answered within a day, and sometimes, it took five days before someone answered the ticket, but when we do get someone, in general, I found most of them to be very good. I would rate them an eight out of ten.

Positive

We didn't use any other solution before BeyondTrust, but we recently switched over to CyberArk.

The process of migrating end users to Password Safe varies from organization to organization, but overall, if you have all the proper workflows, it isn't difficult. With PAM, half of the work is related to processes and policies, and the other half is related to technology. In terms of the technology, I found it to be pretty straightforward, but you need to have all the policies defined in advance.

It wasn't too difficult for us to integrate Session Management into existing business processes. You have to provide the connection strings. The difficulty level was average.

I was the integrator for one of the projects. As a part of their purchase, they also got a certain amount of hours of professional services from BeyondTrust.

We had a team of about five people for its deployment and maintenance. There were two DevOps and two BeyondTrust admins.

We didn't see a return on our investment.

The pricing of BeyondTrust is very good as compared to other products. That was the main reason we decided to go with BeyondTrust at first.

I wasn't involved in its procurement. They had to go through their due diligence. They probably had four PAM vendors, and they went through their procurement process.

Functionality-wise, it works. Everything works well, especially with using Smart Rules. There is a big learning curve to deploying and maintaining it because when you buy this solution, it doesn't come with a Password Safe database. You have to deploy that yourself. If they can package a database with Password Safe, it would be better and more user-friendly. It will cut down the deployment time. They should also improve their documentation, knowledge base, and support on their website. There is not a lot of good information.

I would rate it a six out of ten.