Slashdot Mirror


Is Open Source SNORT Dead?

alphadogg writes "Is Snort, the 12-year-old open-source intrusion detection and prevention system, dead? The Open Information Security Foundation, a nonprofit group funded by the US Dept. of Homeland Security to come up with next-generation open source IDS/IPS, thinks so. But Snort's creator, Martin Roesch, begs to differ, and in fact, calls the OISF's first open source IDS/IPS code, Suricata 1.0 released this week, a cheap knock-off of Snort paid for with taxpayer dollars. The OISF was founded about a year and a half ago with $1 million in funding from a DHS cybersecurity research program, according to Matt Jonkman, president of OISF. He says OISF was founded to form an open source alternative and replacement to Snort, which he says is now considered dead since the research on what is supposed to be the next-generation version of Snort, Snort 3.0, has stalled."

42 of 127 comments (clear)

  1. No way by gparent · · Score: 4, Funny

    Netcraft hasn't confirmed it yet.

  2. It's not dead. by saintlupus · · Score: 5, Insightful

    Snort is nowhere near dead - it's still used in tons of production environments, especially in higher ed (where we've always got plenty of Unix nerds on hand, and never have any money).

    I would imagine Marty's objections probably have something to do with his desire to move people from Snort to the commercial IDS offerings from Sourcefire. That easy upsell doesn't exist if people start off on another product.

    --saint

    1. Re:It's not dead. by Arathrael · · Score: 2, Interesting

      I suspect in a lot of places where Snort is used, it's mostly just sitting there quietly generating thousands of mostly '(http_inspect) DOUBLE DECODING ATTACK' alerts and being completely ignored. It's easy enough to set it up, but out of the box it typically generates an awful lot of noise in the form of largely useless alerts, so it takes some configuring (and understanding of exactly what those alerts are) to get it to a point where it's really useful.

      And yes, I reckon that the commercial aspect to Snort probably is a key factor in this argument. They push that quite heavily IMO with (e.g.) new rules only being available to subscribers and other users having to register and wait until they're 30 days old to download them.

      I'm curious as to whether Suricata is any good, I might have to check it out. Also, meerkats.

    2. Re:It's not dead. by saintlupus · · Score: 4, Informative

      According to Marty, when asked about IPv6 support at this year's EDUCAUSE Security conference, Snort will happily inspect IPv6 traffic if you configure the HOME_NET to be an IPv6 network.

      There's no explicit option to turn it on, because it shifts from v4 to v6 when the rest of the configuration is set up properly. This subtlety seems to elude people. Well, either that or the guy who initially wrote the software doesn't know how it works.

      --saint

    3. Re:It's not dead. by alexborges · · Score: 2, Insightful

      "Out of the box" IDS's are crap.

      IDS and IPS is a process that needs a human analyst. Pretending that software will adapt and respond to attacks by humans is just the wrong way to go about the network security issue. In that area, nothing beats snort: it is THE best tool for a good analyst to do the best possible job.

      --
      NO SIG
  3. Is this a fork? by Anonymous Coward · · Score: 2, Insightful

    Is this a fork or is DHS replicating Snort without copying the code?

    Why is it that I have a queasy feeling in my gut about network security tools supplied by DHS?

  4. "Rip Off"? by Anonymous Coward · · Score: 2, Interesting

    Seriously? Having use Suricata...a lot...I can tell you it's much of what SNORT should have become. A rip off it is not. Multi-threading alone is a God-send.

  5. Great summary quote by MikeBabcock · · Score: 3, Informative

    For people who don't read the article:

    Suricata's top speeds today may be slower than Snort's. Jonkman is citing Suricata at 8 to 10 Gbit/sec and Roesch cites Snort at 50 Gbit/sec, with both acknowledging a lot of range due to platform use. But beyond that, Roesch says Suricata is basically a "sub-set of Snort's functionality at a fraction of its performance." He even calls Suricata a "clone of Snort" as it uses Snort signatures. The OISF's description of Suricata does include how to use Snort signatures with Suricata and transition off of the Snort platform.

    "They've produced a clone of Snort that performs worse at taxpayer's expense," Roesch says. "They haven't advanced IDS."

    So, the taxpayer paid good money to develop a slower and less functional version of an already open-source product. Brilliant.

    SELinux was a good investment of taxpayer dollars. This was not, as far as I can tell.

    --
    - Michael T. Babcock (Yes, I blog)
    1. Re:Great summary quote by Hylandr · · Score: 5, Interesting

      Having been a Navy contractor in just this exact field, my experience with govt / military jobs indicates to me that this is a lot of stovepipe rooster crowing.

      Self important BS Hype to justify the tax dollars and get the pats on the back. The positive comments here for this 1.5m hack of snort is more than likely astro turfing. Up until now, I haven't even heard of Suricata.

      Can someone provide a link where this has been in some mainstream IT circles being debated as Beta release candidates were released etc?

      - Dan.

      --
      ~ People that think they are better than anyone else for any reason are the cause of all the strife in the world.
    2. Re:Great summary quote by Anonymusing · · Score: 2, Informative

      Of course, Jonkman does not mention any features that Suricata has, which Snort does not, like multithreading...

      --
      Liberal? Conservative? Compare perspectives at Left-Right
    3. Re:Great summary quote by LWATCDR · · Score: 2, Insightful

      I do not know if that is a fair conclusion.
      Snort is single threaded.
      Suricata supports multi-threading.
      So with Snort you are tied to a single core. Not an ideal situation today.

      This is starting to look a lot like KDE vs GNOME security throw down.
      Snort has been stalled for a while. It is a great program but is not adding any new features.
      Suricata is a new FOSS security system. If nothing else competition will make both of them better.
      And as to the waste of money? Well maybe it was but I do not think so. If nothing else I feel it is GREAT that this is being done as a FOSS project.

      As to the performance claims. What platform was running the tests? What was the load on the platforms? 8 to 10 Gbit/sec is going to do the trick for what Percentage of users? How many people have a single internet connection that matches that?
      And being multi threaded Suricata may very well scale better than Snort in the future as we are going for more and more cores vs faster cores.
      As I said sometime competition is a good thing.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    4. Re:Great summary quote by Sancho · · Score: 2, Informative

      Multithreading is really only a feature if it gets you some benefit (usually that benefit is increased performance.) There are reports which mirror my own findings that indicate that Snort performs much better on one core than Suricata. Snort's Vulnerability Response Team has a blog post that just went up on this exact subject--of course, they have a vested interest in promoting Snort.

      http://vrt-sourcefire.blogspot.com/2010/07/innovation-you-keep-using-that-word.html

      The same physical machine ran Suricata and Snort, and Snort ran almost four time faster:

      "Suricata peaked at about 300 Mb/s without dropping packets, provided no rules are loaded.
      With rules loaded, Suricata runs up to about 200Mb/s.
      Snort, with rules, hits 894Mb/s with no drops" -- Internal VRT Report on Suricata Performance

      Now they don't talk about their testbed, so I'm assuming the worst case for Suricata--single core. At four cores, then, Suricata could match Snort's performance. Scaling up further, it could in theory beat it.

      Now Suricata is also taking an ethical stand against compiled rules, which I like--to a degree. I recognize that there are tests which are hard or impossible to perform using Snort's rules language, but at the same time, I want to be able to look at the rule and see how likely it is to be a false positive. Over the years, the VRT has put out some rules which I would consider laughable. In a highly tuned context, they might work okay. In a larger context (say an ISP or a university, where the sniffers don't necessarily control every machine on the network) they false like crazy. Snort doesn't publish any information on how likely a rule is to false, and so if I can't read the rule, I can't gauge that at all.

    5. Re:Great summary quote by Sancho · · Score: 2, Informative

      Snort runs pretty fast, even if it only uses one core. If you can split your traffic, you can also run two instances of Snort on the same box. Not an ideal solution, but it's an option.

      Once Suricata starts getting better performance, I'll re-evaluate it. For now, in our environment, Snort still outperforms it on the hardware which is within our budget.

    6. Re:Great summary quote by MikeBabcock · · Score: 2, Interesting

      Multi-threading a stream isn't implicitly better. A lot of the work for analyzing a packet stream needs to be single-threaded anyway (or have a lot of locks, eliminating multi-thread benefits) because the packets are coming in one at a time.

      Even if you were to break up the incoming packets into streams, then spawn or call a worker thread to handle each stream independently, you'd quickly become resource-bound (due to large numbers of simultaneous streams).

      This isn't even remotely like KDE vs. Gnome. Neither is a fork of the other, and there were political issues as well.

      --
      - Michael T. Babcock (Yes, I blog)
    7. Re:Great summary quote by Sancho · · Score: 2, Interesting

      Absolutely. But usually, you need to be pushing the envelope in order to get your competitors to do the same. Suricata isn't there yet, so Snort can still rest on its laurels.

  6. So in short by Anonymous Coward · · Score: 5, Insightful

    Okay, so a competing product comes out, they declare their competitor is dead, said competitor says "i'm not dead yet" and accuses them of being a cheap knockoff. Both sides continue to point out flaws or perceived flaws and throw FUD at each other.

  7. Confusing Story Considering Snort's Activity by eldavojohn · · Score: 3, Interesting
    If you go to the page, 2.8.6-1 was released in April of this year. I guess that's a sign of recent life. Granted, 3.0 appears to be a year before that. I don't think competition between two open source projects is a bad thing. Hell, it's great for the end users. Roesch claims OISF's tool is way slower than SNORT. So let the two fight it out and reap the benefits.

    I think the most serious claim against SNORT came at the end of the article:

    "Sourcefire controls the intellectual property and the update cycle for changes. They use the install base of Snort to market their commercial solutions," Stiennon says. "I am not saying that is a bad thing for Snort users but it is limiting to the overall development of threat mitigation technology from the open source community."

    If that's true, that is not cool. I hate it so much when I'm just trying install PDFCreator or some other GPL'd tool and part of the install process involves a default click box to also install Yahoo's toolbar in all my browsers. It's great to see companies back particular open source projects but I do not care for companies that take hold of the reigns and/or use it to propagate their own proprietary tools. It's one of the reasons I'll consider Flex better than Silverlight but never will I consider it open source despite the SDK source being available. It's got vendor lockin associated with it.

    --
    My work here is dung.
    1. Re:Confusing Story Considering Snort's Activity by martyroesch · · Score: 5, Informative

      That's not true, Snort development continues in the open and contributions are still taken from the community. We don't use the community to market our commercial solutions at all, in fact we have strict prohibitions against marketing commercial solutions on the Snort mailing lists.

      Stiennon takes the next wrong step by saying that we're preventing the ENTIRE OPEN SOURCE COMMUNITY from developing threat mitigation technology. Completely wrong. You can still add your own patches to Snort either as a contribution to the project or as an external patch, Sourcefire does nothing to prevent that.

      We also don't require that you install anything other than Snort when you grab it from snort.org, getting and installing Snort today is just like it was before Sourcefire started. If you don't have the problems that Sourcefire solves (scalability and manageability for the mid to large enterprise) you'd probably barely notice we're out there.

    2. Re:Confusing Story Considering Snort's Activity by Animaether · · Score: 3, Insightful

      I hate it so much when I'm just trying install PDFCreator or some other GPL'd tool and part of the install process involves a default click box to also install Yahoo's toolbar in all my browsers. It's great to see companies back particular open source projects but I do not care for companies that take hold of the reigns and/or use it to propagate their own proprietary tools.

      Aren't those Yahoo! Toolbar, Google Toolbar, Google Earth, Ask.com default homepage, StarOffice etc. options implemented by the developer by choice in order to get a kickback (some fractions of dollars, I suppose) - rather than the companies behind these solutions 'taking hold of' the projects and inserting them?

  8. Why, it's not Open Source . . . it's . . . by PolygamousRanchKid+ · · Score: 5, Insightful

    The OISF was founded about a year and a half ago with $1 million in funding from a DHS cybersecurity research program . . .

    Open Pork!

    --
    Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
  9. From the OISF site... by Capt+James+McCarthy · · Score: 3, Informative

    "The Suricata Engine is an Open Source Next Generation Intrusion Detection and Prevention Engine. This engine is not intended to just replace or emulate the existing tools in the industry, but will bring new ideas and technologies to the field. "

    You make the call.

    --
    There are no loopholes. It's either legal or it's not.
  10. ls is dead by vlm · · Score: 4, Funny

    In other news, the ls command is also dead. When was the last major functional change for ls? When was the last time you saw a major support contract signed for the ls command? Note that I am accepting $1M contract offers to implement the next generation directory listing program, which I will be naming dir.exe, although I haven't decided whats more trendy, enterprise Java, ruby on rails, or maybe erlang?

    --
    "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    1. Re:ls is dead by blincoln · · Score: 4, Insightful

      When was the last major functional change for ls? When was the last time you saw a major support contract signed for the ls command?

      When was the last time the landscape of Unix-style directory listings changed significantly? Security-related products need to constantly adapt to new types of threat as well as new variations on older types.

      Think about how much the world of computer security has changed over the last couple of decades. When I had my first dialup shell account with internet access, the idea that there would be a major black-market industry for professionals writing malicious code was literally science fiction.

      Meanwhile, the standard Unix-style directory listing still seems to work fine for most people. I haven't looked into the more specialized (SELinux) variations, but I imagine if there were significant changes to the Unix filesystem security model (e.g. if very complicated NTFS-style permissions were implemented), then ls would probably be significantly extended so that it would accurately represent the additional information.

      --
      "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    2. Re:ls is dead by drinkypoo · · Score: 2, Insightful

      I imagine if there were significant changes to the Unix filesystem security model (e.g. if very complicated NTFS-style permissions were implemented), then ls would probably be significantly extended so that it would accurately represent the additional information.

      POSIX.2 allows for ACLs and all major Linux filesystems (Among others, but that's my current area of expertise in computing) have support for them. No mention of "acl" or "ACL" in the manpage for ls.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:ls is dead by amorsen · · Score: 2, Insightful

      (e.g. if very complicated NTFS-style permissions were implemented)

      They are, it's just that nobody uses them. Well except me. Linux with ext3 has had them for ages, and e.g. HP-UX had them in '94 -- probably earlier, but that's when I used them for the first time.

      ls doesn't do much useful with them on Linux though. You need getfacl/setfacl for that.

      --
      Finally! A year of moderation! Ready for 2019?
    4. Re:ls is dead by skids · · Score: 2, Informative

      Hey, say what you will about Lua, for example "who in their right mind uses 1-based array indexing", but at least it has coroutines, which is more than lots of languages can say for themselves.

  11. Snort's just fine by guruevi · · Score: 4, Insightful

    It may not be developed on very actively but that's because it doesn't need to be. It does everything it needs to do and for the rest, the community and any capable sysadmin can make their own rules. At some point the product is finished and all you can do is bugfix it. Adding features makes stuff bloated and is only necessary if you need to sell the stuff in a commercial setting. That's the power of open source, once a product is finished, it's done with. Eventually somebody will rewrite it (if the code is really bad) or make it run better (if architectures change) but a well-written program won't need either in the near future.

    Look at the rsync library. The only thing that was fixed recently is a 64-bit handle to allow for files larger than 4GB to be handled. I don't believe the original programmer is even around anymore to fix stuff on it since the 4GB patch is not included in the official rsync distribution. But it's still widely used without any problems, works as intended and isn't going away soon.

    --
    Custom electronics and digital signage for your business: www.evcircuits.com
    1. Re:Snort's just fine by ta+bu+shi+da+yu · · Score: 2, Informative

      What, Tridgwell isn't accepting patches? Someone call UNSW!

      --
      XML is like violence. If it doesn't solve the problem, use more.
  12. Snort is live. 3.0, OTOH... by savanik · · Score: 5, Interesting

    .... is pretty much DOA.

    Speaking as a security professional, we could REALLY use multi-threaded support in our Snort deployments, and the last time I heard 'multi-threaded support is just around the corner' was in 2008.

    Right now, the fact that one Snort instance runs as one process linked to one interface in your ethernet stack means that only one core can run it. And with us hitting the plateau in computing speed on a per-core basis, and traffic still increasing, multi-threaded support had better show up in the next couple of years at the latest or I'll have to find some other network-based IDS product, at least for some extreme instances.

  13. North Texas Snort Users Group by technoid_ · · Score: 3, Informative

    Just a heads up. The North Texas Snort Users Group is being revived. I have nothing to do with it, but heard about it at the North Texas Linux Users Group (NTLUG) meeting.

    Check out nt-sug.org.

    Technoid_

    --
    Two wrongs don't make a right, but 3 lefts do - Lew of GO magazine
  14. Snort's not dead... by martyroesch · · Score: 5, Insightful

    I should know, I wrote it.

    Snort is developed at Sourcefire these days, the company I started and where I still serve as CTO. I am the lead developer on the Snort 3.0 project right now which is undergoing restructuring after the initial few releases showed performance issues that we weren't ready to live with.

    Snort 2.x is developed by Sourcefire's engineering team, we release several updates a year to the code and updates to detection almost weekly via the Sourcefire VRT. I don't work on the 2.x code base day to day anymore but I do contribute from time to time. Snort 2.9.0 is slated for release this fall and continues 12 years of development on the engine technology which includes some significant innovation in the field of intrusion detection.

    My issue with Suricata is that it has implemented the exact same *detection model* as Snort, it does nothing new from a detection standpoint but wraps it in a multithreaded framework that they're trying to call innovation all on its own. True innovation would be to develop a new way of detecting threats on the wire and they haven't done that, they effectively have implemented the same idea as Snort (processes Snort rules, buffers streams into chunks before processing, etc) on a slower software platform. They implemented what is effectively a Snort fork and did so at taxpayer expense, they got the government to pay them to develop something that the government already gets for free (Snort's detection model) with less features and lower performance.

    Someday Suricata might be a really interesting engine but to go out to the press in a concerted push and advance the idea that "Snort is dead" reflects a stunning amount of hubris and wishful thinking. Snort is the most widely deployed IDS/IPS on the planet, there have been millions of downloads and there are hundreds of thousands of registered users and the community is still growing steadily. Snort's engine development is still moving forward and we have plans to continue to innovate in the field of intrusion detection. If the Suricata team wants to displace it they have a tremendous amount of work to do, they're not even close yet.

    1. Re:Snort's not dead... by rotide · · Score: 4, Informative

      Did you even look at the downloads page?:
      http://www.snort.org/snort-downloads

      Second link is "source".

      If you want the 3.0 source go to:
      http://www.snort.org/snort-downloads/snort-3-0/

      Maybe these weren't the sources you were looking for?

    2. Re:Snort's not dead... by seek3r · · Score: 2, Informative

      I have to agree that Snort is not nearly dead. The team at Sourcefire is working to improve the capabilities of both the open source Snort and the commercial product. With the integration we have put together with NTOSpider (web application security scanner) where NTOSpider is able to generate custom Snort rules for web application vulnerabilities it discovers, this can make Snort a reasonable Web Application Firewall (when in block mode) for accomplishing virtual patches to completely custom web apps. As the Sourcefire team continues to push integration and the Snort rules format to other complimentary technologies, I see an interesting level of advancement on the horizon.

    3. Re:Snort's not dead... by Gerald · · Score: 2, Funny

      I went to linux.com and for the life of me I can't find any Linux source code. You're right. These people are losers.

  15. Re:Nonsense by Anonymous Coward · · Score: 2, Informative

    A million dollars in government money actually only buys you about $1000 in actual work.

  16. Angry by C_Kode · · Score: 2, Insightful

    Martin sounds angry. Suricata is new, I wouldn't expect it to blow away the competition at such an early stage. High speed/quality IDS/IPS isn't something that you can xerox off new competitors in 15 minutes. I suspect it's like Firefox's new scripting engine. It was initially slower than the old one, but with time it will overtake it.

    Martin makes his money off Snort and doesn't want other free software encroaching on his livelihood. Well Martin, maybe you should put forth more effort into Snort rather than just resting on your laurels.

  17. Ever notice? by Anonymous Coward · · Score: 2, Insightful

    Ever notice how funded "non-profits" and new commercial efforts always start by declaring the open source version "dead"? That's a bit like Tesla motors coming out and declaring Ford dead. Whether or not it is true that "Ford is dead", the "competition" has a serious conflict of interest and is in no way qualified to make the declaration. In fact, their need to make such declarations indicates that it is actually far from true.

    A better wording for the OISF:
    "We think our product is better and we wish Snort would just go away, because we are so tired of hearing from our potential customers 'We use Snort, and it does all that already, why would we switch?'."

    OISF is also probably getting really tired of trying to justify every year the expenditure of taxpayer dollars to support a capability that Snort already provides for free. If they really had such a great capability, they wouldn't have any need whatsoever to spread Snort bashing FUD.

  18. OT: Dear Slashdot Admins: PLEASE FIX the mod box by Qubit · · Score: 2, Interesting

    I'm forced to post something in this thread to throw away an accidental mod of "Troll".

    If the moderation box gets focus for any reason, it's going to fire off and moderate the person once you exit it. No ifs, ands, or buts.

    So here I am, having to throw away 4 or 5 reasonable (well, I thought so, anyway) mods to this article in order to not unfairly peg someone as a Troll.

    Plus I have to write this lame post. I mean, who wants to see this lame post?

    Sincerely,
    -- Us

    --

    coding is life /* the rest is */
  19. GPLv2 Plus "Non-GPL" by PSaltyDS · · Score: 2, Interesting

    From the OISF Download page:

    "The Suricata Engine and the HTP Library are available to use under the GPLv2."

    Followed on page 2 of same by this:
    "Membership in the OISF Consortium Group provides a non-gpl limited license for the Suricata IDS engine in return for ongoing support. There are multiple tiers available for consortium participation that simplify the varying levels of support and involvement possible for all types of interest. Contributions may range from man hours in development assistance, technology donations, hardware and infrastructure, to financial assistance."

    I get that if the code is their copyright, they can dual license at will. But doesn't the above mean any contributions from either a community or "Membership" cannot themselves be GPL, since any code accepted will in turn be distributed "non-gpl" among the membership? Also, are there "multiple tiers" of "non-gpl limited license"?

    --
    Any technology distinguishable from magic is insufficiently advanced. - Geek's corollary to Clarke's law
    1. Re:GPLv2 Plus "Non-GPL" by BitZtream · · Score: 2, Informative

      And this is handled all the time by saying 'when you contribute code, you transfer the copyright to us' and then its over.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  20. Snort's Better by helix2301 · · Score: 2, Interesting

    Snort is not dead Snort is a superior tool for network detection. Snort can be ran as a simple dump tool all the way to integration a MySQL database for analyst. Companies build snort into there tools like AlienVault and many others. Snort is a veteran tool that can do packet sniffing, packet logging and full-blown IDS. Snort can also be used with other veteran tools like Barnyard and Sguil. Suricata looks like a great product but it's not Snort.

  21. Re:How can that be now? by rtfa-troll · · Score: 3, Informative

    This is not a good thing for anyone concerned !!

    Open source project dead? How can that be now?

    Well actually, that's not 100% true. Snort is an "open core" project. Sourcefire make most of it's money on the IDSs and other add ons on top, which they don't release under open source licenses. This means that sourcefire doesn't want to put features into snort because they want to profit from them on their upper layers. Also other developers don't want to contribute to snort because they don't think they will get their value back; their features will be taken but sourcefire will not continue their development except where there is benefit for their own solution.

    Worst of all; the existence of open source snort makes it difficult for other competing projects to get off the ground; just look at all the snort forks and how little they change it.

    The death of snort may be a chance for a better challenger to come up with no open core vendor sucking the life from it.

    Having said that, snort has been really valuable; this may also be the thing which motivates Sourcefire to get back into the open source game properly. Let's see if they try to compete or run off into proprietary locked off systems.

    --
    =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();