- 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.
08-12-2026 10:47 PM
We are using CyberArk PAM Self-Hosted, and we have selected the all available message codes while generating the Activity Log report.
However, for the same time period, we are seeing the following behavior:
CyberArk Activity Log Report:
The report contains only three action types:
ArcSight SIEM:
For the same time period, ArcSight is receiving many other CyberArk Vault events, for example:
The ArcSight events show:
We have also verified that the time period being compared is the same. However, the CyberArk Activity Log report is not showing the same activities/events that are being received by ArcSight.
For example, ArcSight is receiving multiple CyberArk event types, while the CyberArk Activity Log report for the same period displays only the three actions mentioned above.
Could anyone please clarify the following?
Our ultimate requirement is to identify the CyberArk audit events/message IDs for the following activities:
We need to verify whether these activities are actually recorded by CyberArk, determine their corresponding message/event IDs, and then confirm whether those events are being forwarded to ArcSight.
Could you please advise what could be the root cause of the difference between the CyberArk Activity Log report and the events received by ArcSight, and what would be the recommended troubleshooting procedure to identify and resolve the issue?
08-13-2026 10:47 PM
hi @Viv V the PVWA Activity Log report and the Vault audit stream sent via Syslog are not the same data set nor are they intended to be a 1:1 .
Based on the screenshots:
08-14-2026 01:54 AM
When you generate the Activity Log report, make sure to select all the Activities you need.
For example, if you don't select the User Login Activities, you won't see the Logon/Logoff activities
08-15-2026 04:06 AM
The main difference is the filtering applied at each layer. In the PVWA Activity Log report, the report is generated based on the activity/message codes selected under the Activities filter; if certain codes or activity categories are not selected, those events will not appear in that report. On the SIEM side, the events forwarded from the Vault are controlled separately through the SyslogMessageCodeFilter
parameter in DBParm.ini. Therefore, the PVWA report and the SIEM output do not necessarily have to contain the same events unless the same set of relevant audit codes is included in both configurations. In your current configuration, 0-999 allows a very broad range of Vault audit events to be forwarded to ArcSight, which can generate a significant amount of unnecessary SIEM traffic and noise. I would recommend identifying the audit events that are actually required by the organization, client, security team, or SOC, such as access assignment/removal, administrative user changes, password retrieval, PSM sessions, logon/logoff, etc. and configuring the required message codes accordingly, rather than forwarding every code from 0-999.
Also, I would recommend to remove PTA.xsl and the issue codes that are being forwarded to PTA after |, in case you are not using it. Just to be on clear side, 0-999 are being forwarded to your ArcSight and issue codes that are present after | are being forwarded to PTA. In case your requirement is to forward the logs after | to your ArcSight, I would request you to put them in place of 0-999.
@Chetan Chaudhari @Prem Yadav
08-19-2026 04:50 AM
Hi Iroman,
We understand that the PVWA Activity Log report and the Syslog forwarding mechanism are separate, and that Syslog forwarding is controlled by them SyslogMessageCodeFilter and parameter in DBParm.ini
Before troubleshooting the Syslog/ArcSight side, we would like to confirm whether the following activities are actually being recorded as audit events within CyberArk Vault:
Our main question is:
Where can we verify these original audit events inside CyberArk PAM before they are forwarded through Syslog to ArcSight?
Could you please clarify which CyberArk report, audit log, or Vault log should be checked to verify these activities?
08-19-2026 04:50 AM
Dear Team,
We understand that the PVWA Activity Log report and the Syslog forwarding mechanism are separate, and that Syslog forwarding is controlled by them SyslogMessageCodeFilter and parameter in DBParm.ini
Before troubleshooting the Syslog/ArcSight side, we would like to confirm whether the following activities are actually being recorded as audit events within CyberArk Vault:
Our main question is:
Where can we verify these original audit events inside CyberArk PAM before they are forwarded through Syslog to ArcSight?
Could you please clarify which CyberArk report, audit log, or Vault log should be checked to verify these activities?
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!

