- 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.
01-29-2026 02:41 AM
Hello,
Previously Windows Events were forwarded to PTA using agent, but that solution is sunset (last version v13.0).
What is the way to do it now? According to the documentation of pta docs.cyberark.com send information to Windows Event Forwarder server and from there send events to the PTA server via any forwarding agent over syslog, meaning I would need something like NXLog forwarder or other tools?
I've tried to go with single WIN server > promote to WEF > gpedit.msc > Event forwarding > Target Subscription Manager > PTA IP:514
But this approach is not working, any body got it working with out of the box windows tools to get it directly send to PTA?
01-29-2026 11:46 AM
Hey @Richard Preisinger 1. Windows events are collected using WEF, then sent via Windows NXLog to PTA. The current configuration from NXLog is most likely causing an unsupported format for logs, etc.
I recommend adjusting NXLog's config so that it sends logs in the default XML format which PTA can parse:
https://docs.cyberark.com/pam-self-hosted/14.0/en/Content/PTA/Configuring-WEF-Forward-syslog-messages.htm
https://nxlog.co/community-forum/t/1222-how-to-forward-the-raw-xml-for-windows-logs
01-29-2026 11:46 AM
Hey @Richard Preisinger 1. Windows events are collected using WEF, then sent via Windows NXLog to PTA. The current configuration from NXLog is most likely causing an unsupported format for logs, etc.
I recommend adjusting NXLog's config so that it sends logs in the default XML format which PTA can parse:
https://docs.cyberark.com/pam-self-hosted/14.0/en/Content/PTA/Configuring-WEF-Forward-syslog-messages.htm
https://nxlog.co/community-forum/t/1222-how-to-forward-the-raw-xml-for-windows-logs
09-10-2026 08:07 PM
Hi,richard.preisinger
Do you know if there is any solution to this problem at present? I have also encountered the same issue.
After using NXlog, it definitely failed to meet the requirements. The two main functions of PTA, namely Unmanaged Privileged Accounts (UPA) and Suspected Credential Theft (SCT), have basically been rendered ineffective.
09-10-2026 11:55 PM
Hi Hao,
Well the proposed solution from CyberArk after sometime is not the best... community edition nxlog is not supported anymore (if you don't mind not updated, it will serve the purpose) enterprise nxlog should substitude the requirements of cyberark agent. For sure I'm using it for unmanaged privileged accounts and activity done on them, but I'm using custom parser. For SCT i have not tested it, but if it was using previously the agent and it's based on logs from the server and information in vault, it should work.
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!

