- 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.
03-05-2019 02:53 AM
Hello community,
just recently we experienced the following problem at our company: the shutdown of several endpoints was taking more than 10 minutes to complete, when normally it takes less than 30 seconds.
I had the problem on my computer as well and in the Windows Events Logs I found that during the shutdown, two CyberArk processes were being created every 2 seconds, preventing the computer from shutting down.
In the CyberArk Logs, I was looking for something that might have caused that, and based on the date when the issue appeared, I found out that the Threat Detection Policies were responsible for that and more specifically the "Windows Credentials Harvesting" policies, which initiate the SIP.exe process.
The shutdown issue could be resolved after disabling these policies. Now we would like to activate them again.
Have you also experienced the same problem? Do you know what could cause this and how we can fix it?
Best regards,
Anique
P.S. Attached our configuration:
CyberArk SAAS Platform
Windows 10 endpoints
Agent version 10.7.0.815
05-22-2019 03:46 AM
Hi,
2 hints:
> do you know which exact threat detection policy causes the slowdown?
> have you tried to update the agent to the newest version and does the problem still exists?
Best Regards,
05-22-2019 03:51 AM
Hello,
and thanks for the answer.
Best regards
05-22-2019 05:18 AM
Hi,
Ok.
As I see the SIP process is a CyberArk process. Please double-check if the executable/folder where the executable is placed is excluded from your antivirus system.
Best Regards,
Fabian
05-23-2019 04:43 AM
Hi,
some other troubleshooting hints, after checking the antivirus exclusions.
Are there any other (security) products running on the devices?
Maybe you have to exclude the CyberArk processes in these 3rd party solutions too and the other way round to exclude these processes from CyberArk EPM.
> try to isolate the issue by uninstalling several agents/software which runs on the system to identify which one is causing the issue - or similar approach.
Best Regards,
Fabian
05-23-2019 04:52 AM
Hello,
I just tested yesterday and with or without the exclusions on the Antivirus System, the problem remains.
Best regards
06-04-2019 01:03 AM
Hello Fabian,
thanks for the answer.
How can I exclude a process from CyberArk EPM? Should I add them as Trusted Sources?
Best regards
06-04-2019 02:49 AM
You can globally exclude executables and folder within the "Advanced" > "Agent Configuraiton" Section inside your instance:
07-23-2019 11:36 PM
Hello again,
thanks a lot for the information and the support.
After bilaterally creating exclusions between CyberArk and 3rd party solutions, we have determined, that the shutdown issues still exist.
Are there any other suggestions from your side, or should we wait for the major release and test again?
Best regards
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!

