Q: 14
You just set up a security system in your network. In what kind of system would you find the following string of characters used as a rule within its configuration? alert tcp any any -> 192.168.100.0/24 21 (msg: ““FTP on the network!””;)
Options
Discussion
D . The 'alert' and 'msg' keywords are a giveaway for an IDS rule, not iptables or FTP configs. A is tempting if you only look at IP/port, but those don't use this style.
D. Had something like this in a mock and it was definitely IDS syntax, not firewall or router. Pretty sure it's D.
C . Seen ACLs use similar logic with IP and port filters, though the 'alert' part is throwing me off a bit. Maybe router iptables can use something like this? Not fully sure so open to corrections.
I get that some folks might confuse this with a firewall rule, but the alert tcp ... msg part is pure IDS stuff. Firewalls don't use 'alert' or msg options like that. Seems obvious for D, unless I'm missing a weird trick in iptables config?
Maybe D, matches IDS rule syntax but not 100% if router iptables ever use this.
D , pretty sure that's IDS rule syntax, especially with the 'alert' and 'msg'. Had something like this in a mock and it pointed straight to Snort. Unless there's a weird config for iptables I've never seen?
C or D. The string looks just like a Snort IDS rule but I saw something similar in a practice that mentioned router ACLs. Pretty sure it's D because of the 'alert' and 'msg' parts, but resources like the official guide and lab scenarios are worth double-checking. Anyone got another take?
D imo. The alert tcp any any -> part is classic Snort/Suricata IDS rule syntax. Firewalls (A/C) use different formats, and option B doesn’t make sense for an FTP server rule. I think some mix this up with iptables but that never uses the 'alert' action or this msg format. Correct me if I’m missing something though.
Be respectful. No spam.