NEW – Suricata 1.4.6 pkg v0.1 BETA package released
-
@jflsakfja:
How about adding the unix epoch timestamp to the alert? Not visible (to reduce clutter), but a clickable button to take you to the file. That should be directly related to the file that is created by the alert. If that's not possible, there should be a direct relation to the alert time and the file creation.Haven't tested the package yet, I'm super busy this weekend, so can't really say how the pcaps are related to the alerts.
That might work. I will look into it. Thanks for the suggestion.
Bill
-
To keep the various rule sets separated (since the names duplicate within ET and VRT), each enabled vendor rule set is prefixed with a label to identify the source. So for example, the "drop.rules" in ET-Pro rules would be listed under CATEGORIES as "etpro-drop.rules" while the ET-Open version would be "emerging-drop.rules". You should see them listed that way under the CATEGORIES tab.
They are there in Snort, but not in Suricata. Due to having both running?
I have a temporary ET-Pro subscription I was using for testing, and those rules are there for me in Suricata. Let me quickly test an ET-Open VM to see the result. As for Snort and Suricata running together, that should not figure in as each has its own directory for storing stuff and doing rule extractions and such.
Bill
-
They are there in Snort, but not in Suricata. Due to having both running?
I figured out what the problem is. It is a naming convention anomaly. Turns out those files are named slightly differently in the ET-Open tarball as opposed to the ET-Pro tarball I did the majority of my testing with. This one slipped by me during my testing. I will fix it and get it into the next update. I'm working on v0.2 of the Suricata package now.
Bill
-
I'm working on v0.2 of the Suricata package now.
Strict curiosity but any thoughts on when you will complete the "Block Offenders" feature of Suricata?
-
@jflsakfja:
All the "emerging-*" ET rules show under the Categories. However, the following are in suricata.yaml but are not there:
- botcc.rules
- ciarmy.rules
- compromised.rules
- drop.rules
- dshield.rules
- rbn-malvertisers.rules
- rbn.rules
- tor.rules
http://rules.emergingthreats.net/open/suricata/rules/
…. should they be?
You shouldn't actually be using those rules, that's pfblocker's job. see https://forum.pfsense.org/index.php/topic,64674.0.html
The only problem with using pfBlocker for those rules is that they are based on the ET OPEN RuleSet. If you have a paid ET subscription, Snort will still pick up IPs that are not in the OPEN list.
Maybe, Snort/Suricata could create a list of IPs in theses categories above and generate a list for pfBlocker to use?
-
I think I found an issue that is similar to an issue we have had with snort, more then 1 instance of it running… I have a feeling its because of apinger reloading interfaces. I am running Suricata on 2 interfaces, WAN and LAN. I have them stop in suricata_interfaces.php, I tried to stop them in Services but Suricata remains running. I'll have do some more testing but wanted to let you know.
root 16637 5.4 14.9 506440 467016 ?? Ss 9:48AM 5:35.82 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 35615 5.2 6.3 523848 197992 ?? Ss 11:29AM 89:14.46 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 6687 4.9 8.1 523848 252860 ?? SNs 11:29AM 88:19.67 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 39904 4.9 14.8 518724 461212 ?? SNs 12:13AM 40:26.23 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 96654 4.9 2.6 336516 80580 ?? SNs 11:29AM 85:44.73 /usr/pbi/suricata-i386/bin/suricata -i em3 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_50725_em3/suricata.yaml --pidfile /var/run/suricata_em350725.pid root 6132 0.0 0.2 30972 5536 ?? SN 11:29AM 0:02.12 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 34024 0.0 0.0 3644 0 ?? IWN - 0:00.00 /bin/sh /usr/local/etc/rc.d/suricata.sh start root 38206 0.0 0.2 30972 7780 ?? SN 12:13AM 0:01.06 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 58340 0.0 0.0 3644 0 ?? IWN - 0:00.00 /bin/sh /usr/local/etc/rc.d/suricata.sh start root 95639 0.0 0.0 3644 0 ?? IWN - 0:00.00 /bin/sh /usr/local/etc/rc.d/suricata.sh start root 96518 0.0 0.2 30972 5496 ?? SN 11:29AM 0:02.07 /usr/pbi/suricata-i386/bin/suricata -i em3 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_50725_em3/suricata.yaml --pidfile /var/run/suricata_em350725.pid
-
I think I found an issue that is similar to an issue we have had with snort, more then 1 instance of it running… I have a feeling its because of apinger reloading interfaces. I am running Suricata on 2 interfaces, WAN and LAN. I have them stop in suricata_interfaces.php, I tried to stop them in Services but Suricata remains running. I'll have do some more testing but wanted to let you know.
root 16637 5.4 14.9 506440 467016 ?? Ss 9:48AM 5:35.82 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 35615 5.2 6.3 523848 197992 ?? Ss 11:29AM 89:14.46 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 6687 4.9 8.1 523848 252860 ?? SNs 11:29AM 88:19.67 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 39904 4.9 14.8 518724 461212 ?? SNs 12:13AM 40:26.23 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 96654 4.9 2.6 336516 80580 ?? SNs 11:29AM 85:44.73 /usr/pbi/suricata-i386/bin/suricata -i em3 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_50725_em3/suricata.yaml --pidfile /var/run/suricata_em350725.pid root 6132 0.0 0.2 30972 5536 ?? SN 11:29AM 0:02.12 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 34024 0.0 0.0 3644 0 ?? IWN - 0:00.00 /bin/sh /usr/local/etc/rc.d/suricata.sh start root 38206 0.0 0.2 30972 7780 ?? SN 12:13AM 0:01.06 /usr/pbi/suricata-i386/bin/suricata -i em2 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_40502_em2/suricata.yaml --pidfile /var/run/suricata_em240502.pid root 58340 0.0 0.0 3644 0 ?? IWN - 0:00.00 /bin/sh /usr/local/etc/rc.d/suricata.sh start root 95639 0.0 0.0 3644 0 ?? IWN - 0:00.00 /bin/sh /usr/local/etc/rc.d/suricata.sh start root 96518 0.0 0.2 30972 5496 ?? SN 11:29AM 0:02.07 /usr/pbi/suricata-i386/bin/suricata -i em3 -D -c /usr/pbi/suricata-i386/etc/suricata/suricata_50725_em3/suricata.yaml --pidfile /var/run/suricata_em350725.pid
Thanks for the report. I have noticed that sometimes, for an unknown reason, Suricata seems to need two consecutive "stop" commands in order to actually stop. During the initial development I just worked around it by calling "kill" on Suricata twice in succession from the GUI. Might have to incorporate the same thing into the shell script that pfSense uses to start/stop services.
As I have continued working over the weekend on the next 0.2 update of the BETA, I've found some dumb bugs and logic flaws that I am fixing from the v0.1 release. I hope to get out the v0.2 BETA package in the next few days to address all of those problems and some of the ones reported here by users. Blocking in Suricata is still a bit farther out, though. For true inline IPS-mode, some changes to the pfSense kernel code are required and Ermal is looking at those. Since those kinds of changes are sort of major, I don't look for that to happen until at least pfSense 2.2. However, it is possible to patch/hack Suricata to work like Snort on pfSense and use an alias table in the packet filter for blocking. I have that plan in my back pocket as a temp solution for blocking.
Bill
-
@BBcan17:
The only problem with using pfBlocker for those rules is that they are based on the ET OPEN RuleSet. If you have a paid ET subscription, Snort will still pick up IPs that are not in the OPEN list.
Maybe, Snort/Suricata could create a list of IPs in theses categories above and generate a list for pfBlocker to use?
This is coming soon, and hopefully in the next Snort release. I want to implement the IP Reputation preprocessor in Snort. This uses simple text files with one IP address or network per line. Lists are distributed with the ET-Pro rules and, I believe, some other packages. Read up on the IP reputation preprocessor here: http://manual.snort.org/node17.html#SECTION003219000000000000000. The preprocessor offers high performance because it's a simple SRC or DST IP address compare. No CPU-intensive pcre matching of traffic content, etc.
Bill
-
This is coming soon, and hopefully in the next Snort release. I want to implement the IP Reputation preprocessor in Snort. This uses simple text files with one IP address or network per line. Lists are distributed with the ET-Pro rules and, I believe, some other packages. Read up on the IP reputation preprocessor here: http://manual.snort.org/node17.html#SECTION003219000000000000000. The preprocessor offers high performance because it's a simple SRC or DST IP address compare. No CPU-intensive pcre matching of traffic content, etc.
Bill
Thats Great news.
If pfBlocker could incorporate .CSV, there are several other lists that can be added.
-
I'm working on v0.2 of the Suricata package now.
Strict curiosity but any thoughts on when you will complete the "Block Offenders" feature of Suricata?
Sorry AhnHEL to be so late responding to your question about the "Block Offenders" feature. I am about to release a Suricata v0.2-BETA update that fixes all the bugs reported thus far (and some more I found while fixing the reported ones). Hopefully this 0.2-BETA will be a more or less "done" package in terms of basic functionality with everything working but blocking. After that, my next priority is to update Snort to the 2.9.6.0 version of the binary and make a few feature ports from Suricata over to Snort (like the new Barnyard2 page with its additional output options, for example). When that is done, then I will work on the blocking feature for Suricata. In terms of a date, a guesstimate right now is maybe the end of March or early in April for the blocking feature.
Bill
-
A feature I always wanted was common block lists in case of a CARP cluster. Is there anyway for the master to sync over the blocked hosts to the slave AND vice versa?
-
@jflsakfja:
A feature I always wanted was common block lists in case of a CARP cluster. Is there anyway for the master to sync over the blocked hosts to the slave AND vice versa?
In theory, I believe so. Now actually implementing this might be a bit tricky. Probably one of the seasoned pfSense Core Team developers is better suited to answer the question. I can ask them via e-mail and see what they say. Since the blocks are really just entries in an existing pf alias table, if the firewall tables are replicated, then the blocks should be going along for the ride. I don't run a CARP cluster, though, so I'm a bit ignorant of how pfSense does it. I'm more familiar in my old professional life with VRRP on Nokia and Checkpoint products.
Bill
-
Thanks for the new Suri package, been looking forward to this for a bit. :)
Feel free to disregard, but I was wondering how hard it would be to implement an options tab similar to the oldschool Snort IDSControl Center (see example)
I like the idea of being able to quick select options for a custom starting command line and then being able to save that Suri/Snort profile for later use.
-
Thanks for the new Suri package, been looking forward to this for a bit. :)
Feel free to disregard, but I was wondering how hard it would be to implement an options tab similar to the oldschool Snort IDSControl Center (see example)
I like the idea of being able to quick select options for a custom starting command line and then being able to save that Suri/Snort profile for later use.
Be on the lookout for a substantial update to the Suricata package to be posted sometime over the next few days. I will be submitting the Pull Request shortly. This will be version v0.2-BETA of the package. There are lots of bug fixes and some other enhancements (such as an included Dashboard Widget, better rule update management and logging, and a Bro output option for Barnyard2).
As for some control over command-line options, that is certainly possible. Right now a fair number of parameters are configurable in the GUI and then provided to the Suricata binary via the suricata.yaml conf file. Are there some Suricata-specific command-line options you need that are not available in the GUI? If so, post a list and I will see what I can do.
Bill