- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
10-04-2024 01:52 AM
For some reason I cannot post new questions here. Sorry for hijacking.
When creating files vf_agent.exe delays file creation by reading group policy registry keys every time.
The point is that the file creating overhead while not excluded is many factors higher than it should be. CyberArk is reading for EVERY file, one creates, 302 registry keys 24 times resulting in 7248 registry queries while creating a file. This has nothing to do with security that is simply a performance bug. File security does not get better by reading registry keys very often in loop.
Why is this the case? MS Defender is also active but this consumes only a small fraction of the overhead compared to CyberArk. See this picture where a sample application creates 10 files in c:\temp\parallel where at the beginning Defender scans but when the files are closed CyberArk delays everything by over 200ms by querying domain registry keys like
\Registry\Machine\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\S-1-5-21-462691900-2967613020-3702357964-582536\GroupMembership : Group0
...
\Registry\Machine\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\S-1-5-21-462691900-2967613020-3702357964-582536\GroupMembership : Group302
24 times each. This is an insane overhead.
See the Minifilter delays where overhead is spent. CyberArk wins by a large margin. This should not be the case. These registry keys are not highly volatile and should not be read every time again when a file is being closed.
10-04-2024 04:44 AM
hey @Alois Kraus
This is a new post, just posted in a Resource Center rather than the discussion forum area. This is a perfectly fine spot to post and you are not hijacking anything!
Please send me an email with the details about not being able to post if you would like to investigate it: [email protected]
-Matt
10-04-2024 05:33 AM
@Alois Kraus thank you for your detailed information.
May I ask for those details to be provided in a support case so we can take this FW with RD to analyze?
thanks
10-04-2024 05:36 AM
@Ilan Tsanany I have found in the meantime the support ticket page. Ticket # is 3807841.
10-04-2024 05:41 AM
@Alois Kraus thank you, the case is in a "New" status. I'll ask to escalate, and investigate.
cheers!
10-04-2024 05:50 AM
@Ilan Tsanany : Thanks for pushing this!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

