2018-02-07 04:42 AM
Currently the customer log sources are first sending the logs to a Kiwi syslog forwarder, before forwarding the logs to the VLC. At the SA Head UI, the logs being seen are all via one device ip. The analysts are creating correlation rules based on event source grouping. ( below is the diagram of the traffic flow).
Can we do a Parse to solve the issues single device IP or there are some configuration that need to be done to resolve this issues?
2018-02-07 08:34 AM
Hi Clement,
Are you seeing the original device ip address in Netwitness collected logs?
If not, Please enable "Retain the original source address of the message" option is checked.
Reference: Kiwi Syslog Server
If you are able to see the original IP address, it will be easy to tweak the parsers.
2018-02-07 08:59 AM
Clement
Have you configured the Kiwi Software to spoof the packets(this requires winpcap to be loaded) ? This only works with UDP however, as far as I know.
Dave
2018-02-07 01:20 PM
Clement,
Can you also comment on, why Customer prefers to use a relay in between and not send it to LD/VLC directly? The original log in the format accepted by NW should be forwarded by the relay. And the IP of the relay (Kiwi SYslog Server) should be captured in forward.ip ideally.
2018-02-08 09:15 PM
Hi Sravan,
Yes we are seeing the original IP address.
2018-02-08 09:21 PM
Hi Saket,
The customer want to consolidate all the event and use a single point to send it to the VLC.
Then if i need to do grouping base on device group I cannot use the source device/ or source IP?
2018-02-11 10:31 PM
Hi Dave,
If we configured the Kiwi Software to spoof the packets(this requires winpcap to be loaded) .
Will i see the Device IP?
Clement