BeyondTrust Password Safe Reviews

Typically, we would allow users to connect with their regular user ID, a non-privileged user account, and automatically connect to a designated privileged account managed by BeyondTrust. This account would be onboarded to target systems or databases, preventing users from using their user account as a privileged account. Instead, it would act as a surrogate, using only a managed, dedicated account the user could access.

The platform's most valuable feature is its architecture capabilities, which allow for creating and supporting high availability and failover through designated server components.

The initial server implementation tasks could be easier to process. 

I have been working with BeyondTrust Password Safe for four years.

While some initial server implementation tasks may appear to hang, they are simply processes communicating with each other. 

Overall, the solution is very stable and intuitive.

Thousands of users were utilizing the product across our sites. I rate the scalability a nine and a half out of ten. 

The technical support and customer services are phenomenal. There were instances when we experienced outages during scheduled updates in the middle of the night. On one occasion, an update hung, and we couldn't resolve it. We got technical support that night, which was extremely impressive.

Positive

The initial setup is very straightforward if you understand network architecture. 

Once all the documentation was created, the deployment took about two to three days per site. As the security architect, I was responsible for the documentation, while another team member typically handled the actual implementation. I did step in to handle some implementations myself when one team member had an emergency.

It requires maintenance, typically a weekly manual process or monitoring updates. While most updates can be done automatically, some require manual triggering. One person per site handles the weekly updates, though one person could manage all five sites.

The task of managing the updates is relatively low-level and is often assigned to newer team members. I created very detailed documentation, so they needed to log in, follow the instructions, and let the processes occur. The most time-consuming aspect is waiting for the update processes to complete, which occurs only once a month or every two weeks.

Four team members were involved in the deployment because we managed five separate international locations.

I rate BeyondTrust Password Safe a nine out of ten. 

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.

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.

On-premises

BeyondTrust Password Safe is used to protect privileged accounts and record any activity when using those accounts. Password Safe is able to record and report anything in SSH. It's mainly used for auditing purposes.

We downloaded the virtual appliance and deployed the solution on-premises.

My company's goal is to have mature security and privileged account management. It's mainly used for security purposes and to avoid the usage of credentials.

The ability to manage privileged account passwords is the most valuable feature. It gives us the capability of rotating passwords as soon as an event is triggered. Even if Password Safe protects the privileged account, like an admin account, we can request the password from the profile. As soon as it detects that we have the password and it's used for the first time, the password will automatically change so it can't be used again. The strength of the password will be the same.

Smart Rules were created to automatically assign the credentials that belong to each user and their profile. We use the Smart Rules feature for automated privileged account management.

The Password Safe user interface is simple and very intuitive. I would rate it as a four and a half out of five. It just shows us what we need to see.

We weren't aware that the Password Safe virtual appliance runs on a Windows server. As part of our monthly patching process, we ran into an issue. BeyondTrust Password Safe wasn't compatible with the patching we used to put on our server.

We cannot download patches from the Microsoft Windows server and deploy them on the solution. The solution starts failing, and we run into incidents. This is a major issue that they need to fix. We have to wait for months for Microsoft to release security patches.

I used BeyondTrust Password Safe for less than one year.

In my previous organization, I worked on a project to manage all of the privileged account passwords and rotate the passwords to protect the usage of those accounts from unknown credentials.

The solution is stable. We had an issue with upgrading the operating system, but it has otherwise worked flawlessly.

I would rate technical support a three out of five. They take too long to fix issues, but that could be the fault of the person who opened the case.

Neutral

I have also used CyberArk. My privileged account was already onboarded, and I was just an end user. The user interface of CyberArk is less intuitive than BeyondTrust Password Safe. CyberArk is too IT-oriented for the interface, while BeyondTrust is easier to use.

The setup wasn't complex. Installation was straightforward, and we received training before we started to run the solution. We aren't experts on BeyondTrust, so we needed an expert to help with deployment.

BeyondTrust provided a single appliance with everything we needed for deployment. We were able to switch to the second data center where we installed BeyondTrust Password Safe. They accompanied us when we installed and configured it.

We used a third party for integration.

We have seen an ROI because we have audited evidence to show what has happened when there's an incident.

I would rate this solution a nine out of ten. 

We had some challenges with migrating admins to Password Safe. Before we started onboarding, we created a test and faced an issue with the GPU. It prevented Password Safe from rotating passwords. BeyondTrust needs to give more guidance on what to look at when we want to manage our privileged accounts. 

Overall, it's a very good, well-designed solution. You need to have a basic understanding of managed accounts, functional accounts, Smart Rules, and the capabilities to configure SSL and TLS.

Before making any changes to the platform, my advice is to ask BeyondTrust to make sure it won't cause any incidents.

On-premises

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.

On-premises

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.

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.

The pricing is not cheap, but it could be better.

I'm familiar with BeyondTrust. I have been with it for around a year.

The stability is perfect.

It is highly scalable.

The technical support is very good.

I'm familiar with both BeyondTrust and Password Safe. It's actually a Privileged Access Management (PAM) solution. It is a good competitor to Deliena, One Identity, and WALLIX.

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 pricing is nice. It is a yearly basis license. I would rate the pricing a seven out of ten, where one is cheap and ten is expensive.

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

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. 

On-premises