- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
10-04-2018 01:29 PM
Regarding the syslog setting, the recommended is the best practice. If your syslog queue goes above 1k,then something is wrong.
Regarding AIM, on default 3 min setting they cause some significant load on the vault when there are dozens so you usually would update them to either 15 min queries or work on a satellite vault.
10-04-2018 02:35 AM
On SIEM, I find lot of events VAULT-PROD CEF: 0|Cyber-Ark|Vault|10.3.0000|56|Failure: Find Files|7|act="Find Files" suser=Prov_host fname= dvc= shost=IP dhost= duser= externalId= app= reason= cs1Label="Affected User Name" cs1= cs2Label="Safe Name" cs2="safe" cs3Label="Device Type" cs3= cs4Label="Database" cs4= cs5Label="Other info" cs5= cn1Label="Request Id" cn1= cn2Label="Ticket Id" cn2= msg=
These are related to AIM CP, is there a way to contain these events?
10-04-2018 01:29 PM
Regarding the syslog setting, the recommended is the best practice. If your syslog queue goes above 1k,then something is wrong.
Regarding AIM, on default 3 min setting they cause some significant load on the vault when there are dozens so you usually would update them to either 15 min queries or work on a satellite vault.
10-09-2018 05:09 AM
Thanks Kostya for your response. Figured out the root cause and addressing it. Apparently there was no need to adjust the syslog setting.
On the AIM, the issue was not with password queries of existing objects, it was more to do with mis-configuration of the application that has created huge traffic of password requests for non existent objects.
10-09-2018 07:43 AM
Glad you had this solved 🙂
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!

