Initial setup was very straightforward. It's basically a hardware appliance. It's a software appliance, but it's a hard-coded appliance. It's just a black and white screen, and it has everything inside. BeyondTrust is a Windows-based server, and they usually harden the machine and have their own patches on it, even though it's a Windows machine, so we can easily log into it.

With the current solution, it's very difficult to log in. It's just a black and white screen, and you need a support account to log in onto it. It feels more secure. It's a shell, and the database is embedded. But with BeyondTrust, it's SQL-based and Windows-based, so it's vulnerable.

When we first set up the solution, it was only a few endpoints to give access to the vendors. Now, it's around 400-500 machines.

It required a lot of maintenance. There were a lot of new patches and new versions of the appliance, and then the appliances would move out of support very quickly, which is another reason we are moving to BeyondTrust. At the moment, we are using the version which is very stable, but it is out of support within six to seven months. They keep asking you to upgrade to the new version, which is challenging. Once we upgraded, we had a lot of issues that support couldn't fix.

Appliance setup was not difficult. We did have issues with network setup (behind a load balancer, or not; these were mostly internal issues and not the problem of the product). We selected this product (in part) because of the initial ease of implementation. We did a PoC and had the appliances set up in less than a day.

Setup was straightforward once we linked to Active Directory and had our network firewall group access completed.

It is very easy to set up the initial piece. We even did it without CA on-site for the first day. We got it up and running, then they came in and helped us tweak it and make it a little bit more efficient. However, setting it up out of the box, it was a no-brainer. It was very quick.

It was a straightforward setup.

We have ten appliances and the setup was straightforward. We had no issues setting up our infrastructure.

I don’t know about the initial setup. I was not involved in the initial setup.

I was not part of the bank at that point.

In the PoC, it seems very easy to get started.

We did not have any team members who were trained in Xceedium. For the setup, we got directions from the manual that was provided by the reseller.

We then went to Xceedium, which is now CA. They helped us if we had any issues from the technical point of it.

I would rate the setup as 80/20: 80% being simple and the remaining 20% needed some help from the technical folks at CA.

The initial setup is not complex. The design and integration can become complex without the proper solution architecture and understanding the impacts changes in technology place on a companies operational process and employee behavioral management. These topics became more complex to manage and establish than the product itself.

Initial setup was straightforward, but we had some problems initially understanding what needed to be done to get an end device under management and how to set up the networking.

The setup was complex. It took one month and we needed collaboration between various different departments. We used a consultant to help us. We needed two people to integrate the solution and we currently employ one person for maintenance.

The product is easy to install.

The initial setup was straightforward and very easy to setup.

Initial setup is pretty straightforward.

The initial setup/configuration was easy. It was more troublesome in finessing the rule sets/processes that needs to be used, which isn’t a product issue but an internal walkthrough of how we wanted the access to be controlled and in what manner.

It was a little bit of both. There's some internal politics, and the internal infrastructures, as well as bringing in a new product,; but overall it was fine.

There was lack of knowledge from my team; and then learning from the other team, as well as the professional services team learning our infrastructure and its intricacies.

How do you get a change control approved so we could do something quickly?

The initial set up is very straightforward. The complexity is not so much of a problem, but that’s up to the organization.

The initial setup was easy and straightforward.

Initial setup is very straightforward and ease to configure. It is similar to any appliance-based network security device.

The initial setup was straightforward.

When we set up CA PAM, it's a OVA. It's an appliance, a virtual appliance, that we just needed to throw in VMware, spin it up, and there it is. From there it was just connecting in other things like our storage, our time server, and whatever else. Very very simple to set up.

I did not personally do the setup. From what I remember, it took a couple of weeks for the security lead to do the work. That's not out of the question or a surprise with a security product, because just getting it operating usually takes a little bit, then getting it fine tuned takes a whole another round of work.

The first setup was complex. The implementation, to me, was very bad.

It was a challenge for our newer staff members to install. 

Session management is pretty straightforward as is the password management. We were able to get it up and running in no time. It might be a bit complex to follow the flow of creating the devices, users, and single sign on using the password vault, so that process could be simplified for those getting started with the solution.

Once you have a network, then the reach-out is added. They have something called Outer Discovery, which discovers all the accounts and all the servers’ end points and groups.

I'm not going to say it's very easy, but on the flipside, I'm not going to say it's terribly hard to do it.

The reason it was not easy, was that the end points of the system administrators that have access to PAM needed a version of Java and some Java libraries on the end point.

With logged-on systems in the DOD space, or with the federal space, it's really tough to get those versions installed. The federal government, the central IT, update the Java versions and we don't have control over that. Every time we have an upgrade, it breaks the accessibility of the software.

Even though they say it's a web based tool, they still need a Java version that is compatible and libraries have to be on your client to do it. The Java competence has been a nightmare.

The product installation by itself is fairly easy, but the accessibility is very difficult.

We did reach out to CA and submitted a ticket with them, saying, "Okay, you need to get out of this Java thing, and then have something like HTML-file-based access, so that we don't have to have any of these Java things."

They said, "Great," but nothing has happened so far.

The deployment was very fast, as it is commonly deployed as a virtual appliance.

Simple for me.

I didn’t get involved in the initial setup.

The setup was straightforward.

I didn't do the initial setup, so I can't answer this question.

The initial setup is really easy. The only thing to worry about is to add all needed networks to your virtual appliance prior to the initial boot. This is a pain and should be fixed in my opinion.

The setup is one of the advantages of CA PAM, as compared with the other solutions.

The initial was setup straightforward and simple. The solution does not need any complex customization to deploy and start using it.

The deployment was straightforward, and the provisioning, too. In general, it's not complicated to work with this solution.

Initial setup was simple because of the rule-based configuration.

It's easy to configure and with the help of their documentation, one can easily do that.

The initial setup was straightforward.

Some rollover scenarios can complex to achieve.

The setup was not simple, design took a lot of time, and we had a consultant from CA.

Straightforward. We recently migrated from Physical to Virtual Appliance.

Very straightforward.

The initial setup was complex. The system itself was easy to install, but the configurations were highly complicated.