🚨 BREAKING news: CyberArk is officially rebranded as IDIRA® by Palo Alto Networks — announced live on stage today! The future of cybersecurity just got a name. 🔐
I was browsing Twitter yesterday and came across a very interesting tweet from https://twitter.com/jelleverg to the severity of this, I wanted to pass the information on.
While CyberArk has mitigated the vulnerability with an update to the encryption of credential files in newer versions of CyberArk, there are many org’s that cannot upgrade their CyberArk deployments to newer versions. Therefore, the vulnerability would still exist in those environments. A compensating control could be to further restrict access and/or implement robust monitoring on the different CyberArk component servers.
I searched all of the security bulletins, but did not find anything for this. Now that there is a PoC in the wild, I feel it would be prudent for CyberArk to release a security bulletin.
Both organizations look forward to providing additional information on the transaction during an investor presentation at 6:30 am (PT) on July 30, 2025. Webcast link.
Hey folks! I just wanted to let you know that we are now posting some of our more popular tools on the marketplace as well as on Labs.CyberArk.com. Take a look and let me know if you have any questions.
ACLight - Advanced discovery of domain privileged accounts and Shadow Admins.
We know how cool it is that that Reddit has this Forum for all the Cyberarkers of the world to ask and provide help with topics related to all the products that Cyberark has to offer.
We have also created an interactive and "live" community of people in Discord.
We carry on conversations around the Cyberark products, the components and help each other in almost real time with howto fix and deploy the solutions. The beauty of it is that we are there and if you ask a question you are bound to get an answer almost right away.
Today the community is made up of around 120 very smart people and we are hoping that it continues to grow.
The link below is a direct invite to the "CYBERARK-ENG" community.
Hey guys, I just passed the Defender exam and I feel like I am trying to take Sentry and do the CDE Challenge shortly after, any tips for Sentry and the challenge? I can't wait to finally finish CDE as I have been putting off taking the exam for the past few months, any advice for both would be very helpful!
I've got great news! You can now get PowerShell code snippets from within Postman!
Just enable "New Code Generation Mode" in Settings within the Postman app and you'll notice a new language when trying to get a code snippet called "PowerShell - REST Method".
CyberArk said on Monday it will acquire cybersecurity firm Venafi from equity firm Thoma Bravo in a deal valued at around $1.54 billion.
The firm will acquire Venafi in a combination of $1 billion in cash and around $540 million in stock, and expects the deal to close in the second half of 2024.
Venafi is also expected to add around $150 million in annual recurring revenue and will be accretive to CyberArk's margins immediately, the company said.
I have not directly work with PAM because my organization does not require it. I am considering a position for a Lead PAM Engineer at a different organizationand the day to day would IAM and PAM stuff. I do have transferable skills from being a security and Server administrator. Using AD and experience with IAM. How easy would it be for me to pick up cyberark if I am new to it but a fast learner. I want to get opinions of people who have experience with cyberark. Thanks
Why does CyberArk upgrade always cause issues? Not even one time it goes smoothly, and it is very frustrating to see this. All of cyber ark product behaves in the same manner. And support is worst of all
When I work with the CyberArk solution, I am by now only frustrated. First, the support is really bad - 1st level is a complete disaster and the answers in the upper support levels that are really poor as well. But the worst is the performance since updating to v12 , I guess they made some changes to the database but I get so many complaints from my users.
Furthermore, none of the highly voted feature requests are implemented, not to mention the "new" v10 user interface, which lacks many features of the classic user interface, even though so many years have passed since the release. :-(
I have the feeling that CyberArk deliberately wants to get rid of on-prem customers and push them in the direction of SaaS solutions. Is it the same for you, are you also frustrated or am I just an isolated case? I do not want to start a shitstorm here, but I am now really desperate because I no longer know how I should deal with it.
I just stumbled on this guy's channel. It is quite useful if you want to learn how to setup and troubleshoot the installation of the CyberArk modules..
I just wanted to share my happiness, this is my second attempt, it was really difficult, and the course itself does not cover everything, you have to read the docs.
Everyone at /r/CyberArk would love to hear the community’s upgrade plans, experiences, and thoughts of Version 10.
This is CyberArk’s biggest update in YEARS bringing speed and performance to the forefront, not only in components such as the Central Policy Manager NextGen (CPM-NG), but also to the User Interface by making CyberArk’s REST API the backbone for the AngularJS User Interface. Forget that old ASP Password Vault Web Access (PVWA)! No more restarting services!
Let /r/CyberArk know your thoughts as CyberArk usher in a new era of automation and performance in version 10!
CyberArk has a new way to help you get your shift together for cloud. The existing Secure Cloud Access product has recently launched a new free trial to help cloud platform teams get in, make a decision and get out without having to talk to a single soul in sales. If you'd be willing to try it, we'd like to show our appreciation for your time by entering you in a giveaway for the ultimate lab setup. Any takers? Sign up here.
Wanted to share our experience in case anyone might be having this issue or run into it in the future.
So we were having issues with our Linux admins who typically transfer files from Linux ----> Linux using SCP. But once we introduced CyberArk and they started using the PSMP, they were unable to do this. We know CyberArk supports SCP, but it wasn't working. Also note here that we use Active Directory accounts almost exclusively. So 6 weeks ago we opened a case with the vendor and we finally got it working today. The issue is that when referencing a domain account using the PSMP for SSH, the "@" character in the UPN needs to be replaced by the "#" and that works fine. But SCP doesn't support the "#". Luckily the components.conf file has syntax to change this. We had to make the following modification:
this globally changes the "#" to the "%", for both regular SSH connections and SCP, which resolved the issue. At best this is poorly documented. As the documentation specifically talks about an "additional" delimiter, which is NOT what is required in this scenario. If you are interested, you can see that documentation here.
Want to point out here, that CyberArk premium support was horrible on this. Up until last week they were urging us to upgrade from 11.7 to 12. 6. They were saying this was a bug in 11.7. But could not povide any evidence of this. We had to urge them to continue working with us to get this resolved. Not a great experience.
Before reading this article, I want to say that in case you are a client of CyberArk / you want to be convinced about CyberArk as a tool, I can say this tool is great. The tool works very well once installed but this is an "Engineer Review" performing the installation of Cyberark. This does not reflect on the usage / quality of the tool. The tool works amazing and gives your company a lot of value. What is important to take away from this review is to not start your PAM journey without a partner that has experience with implementing this tool. This is crucial for your successful PAM journey as the technical documentation is not the best. But from your partner, this should be better :)
I am a CyberArk Core PAS Solution designer / functional Analyst person myself but never got into contact with tool technically. This was my journey on implementing the tool myself to get a feeling of what engineers have to go through. And oooh boy do I have a story for you Mister or Misses reader.
Currently I am busy with the installation of a Cyberark lab, purely using the documentation you can find online. The documentation in general, in my eyes is: 50% Incomplete, 50% Unstructured and 50% not Practical. With this post I want to show you my frustration, the feelings I had during the installation and most importantly provide information for Cyberark to improve upon:(For reference, I tried to install Cyberark V11.2 on Windows 2016 Datacenter machines)
0. Install the VM machines and make sure all components can ping each other before doing any installations. Making sure my network was correctly setup and I had an Active Directory machine correctly configured. Also joined the PVWA, CPM and PVWA machine to the domain.
Test the different components on the way and then start experimenting with Cyberark for clients. Be done in 3 days-4 days. (also think: all VM's have 2GB RAM, so installs go SLOW, but nothing you can do about that, my device it's fault, not CyberArk)
I must say, it was not all bad. The vault installation was quick, with no issues and a very clear and correct explanation. But then the first issue occurred:
I forgot to put the installation binaries from the Private Ark client on the vault.
Why is this a problem? I hardened the vault... --> no copy pasting was working anymore for my Virtual machine. Ended up writing this post about it. (The solution was attaching a disk to the vault with the files on it, then copy the binaries on it and install it.)
Once the connection was tested with the administrator user, I was going to test the fall back procedure for the master user to check whether this procedure would work.
Unfortunately, it is not easy to find what this procedure is. I remember from the Defender Certification you need a recovery key and the master password that is stored on the CD but how to perform it for your lab or what the "emergency procedure" is, no clue... "Googling" the docs of CyberArk doesn't help either. The words: "Master user", "Disaster recovery procedure", "Emergency procedure", "Error reading recovery private key" or "Use the Master user" do not give much detail back.
Just filling in the password and trying to login to the Vault gives the following error:
Eventually by talking to colleagues, I find out that there is a file called "dbparm.ini" that contains the path of where the recovery key is located and it must point to the correct location. So said so done : Yeah!!! The master user works.
Vault installation and emergency procedure complete.
Click on the installer, see the following message:
The documentation says:
During installation, Safes and a User are created to enable the Password Vault Web Access to work. In order for the installation to create these successfully, the Vault user who will carry out the installation
This is not "exactly" the same. Documentation is not complete at this part so I wrote this question to CyberArk and received a reply fairly quickly (KUDOS to the person who answered almost immediately --> great client support):
Here is where the issues started. The clear documentation pointing exactly where to look disappeared, and suddenly the documentation assumed you were in certain applications. More specifically here.
The part about "trusted networks" Is this in the Private ark client, is this somewhere in the PVWA? Is this located in the CPM? Where do you need to adept this setting? It was frustrating to look for it but eventually found it under the Private Ark client, under the "User" tab.
Now I can already feel some opinions from people reading this: "When you install CyberArk, you need to know certain things and where to find it! Your an 'id**t!" --> okay great, but how do you expect people to learn how to install CyberArk, if the documentation officially provided by the supplier is not 100% correct? Everyone can "read context" but sometimes you need more information to do that successfully. The sentence "Enter the private client and add a trusted network" could have saved a lot of frustration.
Eventually, you get to the following page. (Test the CPM page) this page refers to this page. (Test CPM installation in PVWA) --> Why is this referal needed? But okay, as long as you have the answers, it's all good right? Nope....
You follow the steps that is in the the guide, you configure the safe as said and you try to add a user. What happens? Nothing, this error happens:
I just installed this thing and I am already getting an error. The error itself is not explained in the guide, so the only thing you can do, is "Google" CyberArk again. The following words were used: "safe does not support properties" --> not really find anything. So I start Googling (on google.com) the issue and find this CyberArk page containing the answer (but not how to configure the answer)
Apparently there is a setting in the your safe property --> you need to enable file properties for your account creation to work. Once this setting was enabled, everything went smoothly. Now to test the CPM on an AD account --> Success!
Let's test on a local account from a server --> Failure --> still stuck with this one and will update my review according my time, as I only had 4 days.
Let's continue with the PSM for now, as the "CPM Works" but has a specific issue with a local machine. Let's go to the installation page of the PSM. At first it seems okay, you click "Next --> Next --> Finish" and everything works right? That's what the documentation says, but in reality it's not.
Here you see that CyberArk gave up writing, as the structure has always been:
- Before installation
- Considerations
- Installation
- Post-installation (mostly hardening)
- Testing the installation
The only part you find here is: Installation. The rest cannot be found. I have no clue how to test my PSM, nor do I know if it works. but "Hey, I successfully ran the installer and clicked the buttons." "It must work right?". The connect buttons are grayed out and cannot use them on the domain accounts.
First check if your connection components are enable. You can find it here. If you have checked if those components are enabled for your "Safe" it's "Platform" you need to check one more setting.
Apparently there is a setting in the "Master Policy" you have to enable. This setting is called: "Require Privileged session monitoring and isolation". --> If you don't know what this setting does, do not enable it in the "Master Policy". Add it as an exception to a platform you want to test this policy on. You can add an exception by clicking the big blue button in the right bottom corner called "Add Exception"
Once you enable this, the connect button becomes available in the PVWA. Let's test the connect button. --> Failed
Right now I am here, and we are 3 days later since when I started my installation. I probably have to debug the RDP connection from the PVWA --> PSM and also from the PSM --> Target.
This is not for today, but will be for another time. I will edit this post in case I do it. I do think I will achieve my goal with this post. I want to let CyberArk now, the installation is not straight forward like they say in there guide, and hopefully bring awareness to it that it really needs updating. Most of the text you will find is still referencing things from the "Classic portal" and not the new portal. This should also be referenced in the documentation.
Have a nice weekend everyone! Hopefully this can get some attention and other engineers can out there frustrations about the "documentation".
PS: I wanted to add a Reddit "Flair" to this post with "V11.2" but that has not been done yet.
PPS: I am just starting my technical journey, but if it is already like this, I don't know how the rest will be and what will come after this. More chaos?
Update 1: Have looked through the older documentation and have found the issue with the PSM installation. Looking at this older documentation about the PSM it is fairly easy to spot what I missed.
Basicly, what I did after reading the article, was to read out the log CyberArk created after the installation of the PSM. The following line was present and confirmed what was missed:
21/02/2020, 13:37:58 User decision: For successful installation, CyberArk Privileged Session Manager requires Remote Desktop Services to be installed. Would you like to continue the installation without it? This will install a partial PSM environment.
21/02/2020, 13:38:03 User chose [Yes].
21/02/2020, 13:38:03 The user continued the installation although installation prerequisite of Remote Desktop Services was not met. Additional Info: Launch result = 1
This requirement is found in the new documentation, but it is not that obvious. You can find that requirement on this documentation. Scroll down to : "Preparing your PAS components" and you will find the thing I forgot.