312-50V11 · Question #795
You are a Network Security Officer. You have two machines. The first machine (192.168.0.99) has snort installed, and the second machine (192.168.0.150) has kiwi syslog installed. You perfrom a syn…
The correct answer is D. tcp.dstport= = 514 && ip.dst= = 192.168.0.150. To verify Snort is forwarding alerts to the Kiwi Syslog machine, the Wireshark filter must match the destination IP of the Kiwi server and destination port 514.
Question
You are a Network Security Officer. You have two machines. The first machine (192.168.0.99) has snort installed, and the second machine (192.168.0.150) has kiwi syslog installed. You perfrom a syn scan in your network, and you notice that kiwi syslog is not receiving the alert message from snort. You decide to run wireshark in the snort machine to check if the messages are going to the kiwi syslog machine. What Wireshark filter will show the connections from the snort machine to kiwi syslog machine?
Options
- Atcp.srcport= = 514 && ip.src= = 192.168.0.99
- Btcp.srcport= = 514 && ip.src= = 192.168.150
- Ctcp.dstport= = 514 && ip.dst= = 192.168.0.99
- Dtcp.dstport= = 514 && ip.dst= = 192.168.0.150
How the community answered
(26 responses)- A4% (1)
- B12% (3)
- C8% (2)
- D77% (20)
Why each option
To verify Snort is forwarding alerts to the Kiwi Syslog machine, the Wireshark filter must match the destination IP of the Kiwi server and destination port 514.
tcp.srcport==514 is incorrect because port 514 is the destination port on the syslog server - the Snort machine sends from an ephemeral source port, not from port 514.
The IP 192.168.150 is a malformed address missing one octet, and srcport==514 applies the wrong directionality for this traffic flow.
ip.dst==192.168.0.99 targets the Snort machine as the destination, which captures traffic arriving at Snort rather than traffic being sent from it to Kiwi.
Syslog messages are sent TO the Kiwi syslog server at 192.168.0.150 on its listening port 514, so the filter tcp.dstport==514 && ip.dst==192.168.0.150 correctly isolates those packets. Running this on the Snort machine will confirm whether alert traffic is actually being transmitted toward the Kiwi server, isolating whether the issue is in Snort's output configuration or the network path.
Concept tested: Wireshark display filters for syslog traffic analysis
Source: https://www.wireshark.org/docs/wsug_html_chunked/ChWorkBuildDisplayFilterSection.html
Topics
Community Discussion
No community discussion yet for this question.