Re: Announcement: Alert Verification for Snort

From: Martin Roesch (roesch_at_sourcefire.com)
Date: 10/24/03

  • Next message: Craig H. Rowland: "RE: Announcement: Alert Verification for Snort"
    Date: Fri, 24 Oct 2003 10:23:33 -0400
    To: PPowenski@oag.com
    
    

    Hi,

    We declined because we're on the cusp of releasing our 3.0 IMS product
    (combined sensor and management console appliances) with a new GUI, new
    backend, upgraded Snort and a variety of other features (new data
    analysis UI, new incident handler UI, new reporting modules, new policy
    wizard for generating sensor configuration sets, etc) and we didn't
    really want to immortalize our current 2.7 software in an article that
    would essentially be stale a month after it came out, leaving people
    with the impression of a system that we aren't even shipping just as
    we're going to market with our New And Improved (tm) systems. We tried
    to get more time to be able to get our 3.0 system into the test, but
    publishing deadlines and our release schedule didn't line up.

    With the advent of 3.0 we'll be happy to participate in tests if we
    believe we can get a fair shake (i.e. tested by clueful people) and
    assuming the publishing deadlines and everything else line up. If you
    want to see our stuff in action, we do give qualified leads the
    opportunity to evaluate our technology for 30 day periods.

          -Marty

    On Oct 24, 2003, at 3:21 AM, PPowenski@oag.com wrote:

    > Would like to hear why your company declined ?
    >
    > Enterprise Networks / Security /
    >
    > Review:
    > IDS finds niche as analytical tools
    >
    > By Joel Snyder, David Newman and Rodney Thayer, Network World Global
    > Test
    > Alliance
    > Network World, 10/13/03
    >
    > While we invited more than a dozen vendors to participate, only
    > Barbedwire
    > Technologies, Cisco, Internet Security Systems (ISS), Intrusion and NFR
    > Security took part in the end. (See "Equipped to play" for detailed
    > description of the hardware and software each vendor brought to the
    > test.)
    >
    >
    > We also invited Sourcefire, the company where Snort's authors work, to
    > submit their commercialized version of Snort for review, although it
    > declined.
    >
    >
    >

    -- 
    Martin Roesch - Founder/CTO, Sourcefire Inc. - (410)290-1616
    Sourcefire: Snort-based Enterprise Intrusion Detection Infrastructure
    roesch@sourcefire.com - http://www.sourcefire.com
    Snort: Open Source Network IDS - http://www.snort.org
    ---------------------------------------------------------------------------
    Network with over 10,000 of the brightest minds in information security
    at the largest, most highly-anticipated industry event of the year.
    Don't miss RSA Conference 2004! Choose from over 200 class sessions and
    see demos from more than 250 industry vendors. If your job touches
    security, you need to be here. Learn more or register at
    http://www.securityfocus.com/sponsor/RSA_focus-ids_031023 
    and use priority code SF4.
    ---------------------------------------------------------------------------
    

  • Next message: Craig H. Rowland: "RE: Announcement: Alert Verification for Snort"

    Relevant Pages

    • RE: [Snort-devel] RFC: Forking Snort
      ... I am very happy with Snort, it's sigs, plugins, etc.. ... The number of core developers on the Snort ... contributions to the codebase while not being insignificant are not what ... > wildly successfully open source project and Sourcefire (a growing, ...
      (Focus-IDS)
    • Re: Windows based (H)IDS
      ... It may seems so obvious that snort library is very ... Security but it is a commercial product. ... > softwares can be added to the ... > over a network. ...
      (Focus-IDS)
    • Re: IDS vs. IPS deployment feedback
      ... It is not accurate to state that the IPS ... Those two IPS technologies are NFR and Snort. ... signatures for the same vulnerability, ... Snort rules are developed by volunteers (or Sourcefire). ...
      (Focus-IDS)
    • Re: [Snort-devel] Re: RFC: Forking Snort
      ... > back out to the community at large. ... Combine that with my commitment to keeping Snort open source ... >>> own success. ... >>> successfully open source project and Sourcefire (a growing, ...
      (Focus-IDS)
    • Re: [Snort-devel] Re: RFC: Forking Snort
      ... back out to the community at large. ... Subject: [Snort-devel] Re: RFC: Forking Snort ... >>own success. ... >>successfully open source project and Sourcefire (a growing, ...
      (Focus-IDS)