This guide shows you how to integrate a Windows server (or desktop) into the Secure60 platform using NXLog.
For most Windows environments the simplest path is the native Secure60 Win Log Agent (or the agentless Windows Log Receiver) — no third-party tooling to run. See Windows devices for the options. This guide covers the NXLog approach, which still works well where you already run NXLog. Either way, the events feed Log Management and detection in SIEM.
This guide explains how to forward Windows event logs to a Secure60 Collector using NXLog. As always, if you have any further questions, don’t hesitate to contact Secure60 Support.
C:\Program Files\nxlog\conf\nxlog.conf with the following content:<Input eventlog>
Module im_msvistalog
Query <QueryList>\
<Query Id="0">\
<Select Path="*"> *</Select>\
</Query>\
</QueryList>
</Input>
<Output out>
Module om_udp
Host <S60_COLLECTOR_IP_ADDRESS>
Port 514
Exec $nxlog= "NXLOG";
Exec to_syslog_ietf();
</Output>
<Route 1>
Path eventlog => out
</Route>
Ensure you replace <S60_COLLECTOR_IP_ADDRESS> with the actual IP address of your Secure60 collector.
To restart the NXlog service, execute the following commands:
net stop nxlog
net start nxlog
To check the status of NXlog, use the command:
"C:\Program Files\nxlog\nxlog.exe" -v
To enable NXlog integration in the S60-collector, modify the .env file as follows:
ENABLE_NXLOG=true
Logs and alerts can be viewed in the Secure60 portal.