David Waugh

How to Forward Syslog from a Remote Log Collector to another destination

Blog Post created by David Waugh Employee on Sep 23, 2016

(I've only managed to get this method working with UDP)


Customers often want to forward syslog traffic that is being sent to Netwitness for Logs to another syslog destination, so that the syslog traffic is processed by both Netwitness and the other syslog receiver.


There are many ways that this can be achieved (such as Configure Syslog Forwarding to Destination - RSA Security Analytics Documentation ) but here is another method.


1) On the Remote Log Collector go to Event Sources -> Syslog and Config.

2) Disable the current syslog sources. These will typically be upd514 and tcp514. To disable edit each source and untick the Enabled box.


3) Set up new TCP and UDP listeners on a different port. In this case we use UDP 5514 and TCP 5514.

4) Stop and start the Syslog Collection Method

Make sure that in explore view under logcollection/syslog/eventsources/syslog-tcp and syslog udp that you set the following headers to true. This will ensure that when security analytics processes the message the original IP is seen.



5) Confirm with netstat -na |grep -i 514 that the system is only listening on your new ports 5514

 netstat -na |grep -i 514
tcp 0 0* LISTEN
tcp 1 0 CLOSE_WAIT
tcp 0 0 :::5514 :::* LISTEN
udp 0 0*
udp 0 0*
udp 0 0 :::5514 :::*


6) Edit the file /etc/rsyslog.conf


Uncomment the following lines:

# Provides UDP syslog reception
$ModLoad imudp
$UDPServerRun 514

# Provides TCP syslog reception
$ModLoad imtcp
$InputTCPServerRun 514
And add the line

$PreserveFQDN on


7) At the end of the file add the following lines:


*.* @@




*.* @


This will forward all TCP traffic to port 514 or all UDP traffic to


Also add one of the following lines


*.* @@localhost:5514




*.* @localhost:514


This will forward all syslog traffic to our log collector for processing. The difference is that if @ is used the traffic gets forwarded as UDP syslog 514. If @@ is used the traffic gets forwarded as TCP. Forwarding as TCP is better as large syslog messages can be transferred and TCP has more robust packet delivery than UDP.


7) Restart the rsyslog service with service rsyslog restart