Splunk Enterprise

IP duplication problem for syslog transfer

kevinsteeee
Explorer

Hi, I always appreciate your taking the time to answer my question.


We will connect independent systems using the L3 Switch and send the syslog to the cyber security operation center (CSOC) like attached picture. (Network switch will send via syslog function, and Splunk forwarder will be installed on workstation)

 

Since the application that was installed in the workstation cannot be modified, the IP address of server cannot be changed.

For example, if there is an application that communicates with a server having address of 192.168.0.10, it is impossible to change the server IP address because the application code cannot be modified.

 

Splunk Enterprise SIEM will be installed in CSOC, and Heavy Forwarder will be used as the agent for syslog transmission.

If IP addresses are duplicated between independent systems, is there a problem in transmitting logs?

Also, is there a function to transfer syslog by changing the source IP address to distinguish assets?

Or is there another way to differentiate between assets?

 

Best regards,

첨부 그림.JPG

 

Labels (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...