What is our primary use case?
We use the solution for privileged access to internal systems and multiple customer environments.
We have distributed PSM and CPM components throughout multiple sites and customer domains access over the VPN, with PSM load balancing handled via third-party hardware load balancers.
Environment segregation and security are high on the criteria for the implemented solution, however, not at the overall expense of performance.
We tend towards providing access to privileged admin applications direct from the PSM servers wherever suitable, yet offload additional workloads to siloed RDS collections if the need arises.
How has it helped my organization?
I appreciate the ease of use for support analysts. We provide a single pane of glass access to our analysts where segregated admin access is provided via safe access groups. The overall goal is to provide the analysts with just enough access to function without being totally impaired by security constraints. With the piece of mind that the auditing and recording capabilities allow. We provide access to fully managed systems via distributed PSMs, or where the need arises we can provide access to online third-party access points via a central pool of web-enabled PSMs.
What is most valuable?
The most important feature is the password rotation and recording to align with customer security requirements.
The reporting and auditing functions allow us to provide evidence-based accounting to customers or security personnel when or if required. Being able to prove that "it does what it says on the tin" is a very key selling point or point scorer in project and planning sessions.
The marketplace default connectors are constantly evolving and simplifying administration. In the case of one not being available then the majority of additional requests can be catered for with some clever AutoIT scripting.
What needs improvement?
Remediation of some of the platform settings in the master policies section would be handy.
Overall what I would really love to see is the third-party PAS reporter tool pulled more into the overall solution, ideally as its own deployable component service installation package, that could be installed/branded alongside the PVWA service, and build out API integration so that third party calls could draw valuable data directly out of the management backend with very little amount of additional admin overhead.
For how long have I used the solution?
I've used the solution for eight years.
What do I think about the stability of the solution?
The solution is very stable; if instability is ever experienced it is likely to be as a result or symptom of a problem elsewhere, such as external factors (updates, network etc.).
What do I think about the scalability of the solution?
The solution is fairly scalable, although depending on how far and wide you stretch your footprint, you may be better suited to multiple smaller vaults and component environments, than one large pot.
How are customer service and support?
Initial call logging can be tedious at times. If you clearly articulate an issue yet are then required to collate entirely irrelevant logging information or jump through a default set of "have you tried this" questions it can cause frustration. Call escalation via account management has improved and when needed we have then progressed with support at a faster pace.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have not worked with a solution with a focus explicitly for PAM.
How was the initial setup?
The initial setup was both straightforward and complex in equal measure.
What about the implementation team?
The majority of the setup was in-house. On occasion, we have engaged the vendor team and always had a positive outcome.
What was our ROI?
I'm not in the loop to be able to answer to ROI.
What's my experience with pricing, setup cost, and licensing?
Engage with Cyberark account management and professional services to fully understand your current, expected, and future requirements.
Some default settings applied early on may be very time-consuming to amend at a later date (for example, set a default attribute in a platform, extrapolate that platform out to 300 other platforms and a single change may then have to be retrofitted 300 times). So the more scope you can define at deployment the better.
Which other solutions did I evaluate?
I believe other vendors were evaluated prior to selecting CyberArk.
What other advice do I have?
I'd advise other users to take their time, measure twice, and cut once.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.