nerdexam
GIAC

GSEC · Question #350

Use sudo to launch Snort with the, /etc /snort /snort.conf file In full mode to generate alerts based on incoming traffic to echo. What is the source IP address of the traffic triggering an alert…

The correct answer is I. 10.10.201.150. This hands-on lab requires launching Snort IDS in full alert mode and reviewing generated alerts to identify which source IP sent traffic destined for port 156.

Network Security

Question

Use sudo to launch Snort with the, /etc /snort /snort.conf file In full mode to generate alerts based on incoming traffic to echo. What is the source IP address of the traffic triggering an alert with a destination port of 156? Note: Snort Is configured to exit after It evaluates 50 packets.

Exhibit

GSEC question #350 exhibit

Options

  • A192.168.^.30
  • B10.72.101.210
  • C10.10.28.19
  • D10.11.10.11
  • E10.10.10.66
  • F192.168.87.68
  • G10.12.10.112
  • H10.11.12.13
  • I10.10.201.150
  • J10.10.199.146

How the community answered

(38 responses)
  • A
    8% (3)
  • C
    3% (1)
  • E
    13% (5)
  • G
    3% (1)
  • I
    74% (28)

Why each option

This hands-on lab requires launching Snort IDS in full alert mode and reviewing generated alerts to identify which source IP sent traffic destined for port 156.

A192.168.^.30

192.168.1.30 does not match the source IP recorded in the Snort alert corresponding to destination port 156 within the first 50 evaluated packets.

B10.72.101.210

10.72.101.210 appears in network traffic but is not the source IP associated with the alert triggered by destination port 156.

C10.10.28.19

10.10.28.19 may appear in other captured packets but is not the source triggering a port 156 alert in the Snort output.

D10.11.10.11

10.11.10.11 does not correspond to the source IP in the alert with destination port 156 as shown in the Snort analysis.

E10.10.10.66

10.10.10.66 is not the source IP identified in the Snort alert for destination port 156 traffic.

F192.168.87.68

192.168.87.68 does not match the source address in the relevant Snort alert for port 156.

G10.12.10.112

10.12.10.112 is not the source IP associated with the destination port 156 alert in the Snort output.

H10.11.12.13

10.11.12.13 does not appear as the source in the Snort alert triggered by traffic to port 156.

I10.10.201.150Correct

When Snort processes the first 50 packets from the interface using the specified configuration file, the alert generated for traffic destined to port 156 records 10.10.201.150 as the originating source IP address. This is determined directly from the Snort alert log output, which captures source and destination IP and port for each rule match.

J10.10.199.146

10.10.199.146 does not match the source IP recorded in the Snort alert for destination port 156.

Concept tested: Snort IDS alert analysis and traffic source identification

Source: https://www.snort.org/documents/snort-users-manual

Topics

#Snort#IDS#intrusion detection#network alerts

Community Discussion

No community discussion yet for this question.

Full GSEC Practice