topic Splunk for Snort Event Question in All Apps and Add-ons

Splunk for Snort Event Question

phillijc — Wed, 10 Jul 2013 13:17:47 GMT

I'm running a bunch of sample test PCAP files through and getting output in Splunk for Snort but the events seem to be kind of random with different dates, destination IP's, etc within a single event. This is probably a dumb question but I'm wondering what categorizes an event in Splunk for Snort could someone give some insight?

Thank you

EDIT: I see in the opt/splunk/var/lib/splunk/defaultdb/db/ that there are the same number of folders as events. Gives me a little better view of what's happening but not the full picture.

Re: Splunk for Snort Event Question

Ayn — Sat, 13 Jul 2013 15:51:00 GMT

Could you please provide much more details about what you're seeing and what you're expecting? It's very hard to say something useful without any actual details.

An event in Splunk for Snort is pretty much what you would consider to be an event yourself when reading the log files.

Re: Splunk for Snort Event Question

phillijc — Mon, 28 Sep 2020 14:20:32 GMT

Thank you for your reply. I just thought that with a whole folder of different PCAPs who are proven attacks would trigger more events. Here's a little more info:
Data inputs monitors a file /var/log/snort/alert
Source Type: Manual, snort
Event types, these basically search the classification of the alerts. I'm currently only getting network trojans and the snort-alert (of coarse). I'm thinking my data may just simply be limited:
- snort-alert
- snort_dos
- snort_exploit
- snort_information_leak
- snort_login
- snort_potentially_bad
- snort_privilege_gain
- snort_scan
- snort_trojan

Re: Splunk for Snort Event Question

Ayn — Mon, 28 Sep 2020 14:20:40 GMT

OK, the main problem I see with your setup is that you have set the sourcetype "snort". As the installation docs for Splunk for Snort state, you need to set either snort_alert_fast for alert_fast format or snort_alert_full for alert_full format. This is because these two need to be parsed differently in order to achieve correct event breaking, and I suspect this is what is causing you problems - events are not breaking properly so event boundaries in Splunk will not correspond to event boundaries in the original log file.