Welcome Guest. | Log In | Register | Membership Benefits
Dark Reading's evil-bytes Weblog

Topics:   Evil Bytes

New Snort Front-End Adds Speedy Analysis, Ease Of Use

Snorby is a new free, open-source analysis front-end to the popular Snort IDS that is fast and usable

Dec 30, 2010 | 12:13 PM | 

By John H. Sawyer
Dark Reading

I've spent years with the Snort intrusion detection system. It's often a love/hate relationship as I massage the rules in order to get to meaningful and actionable data. Often it comes down to parsing the resulting alerts from the command line and then digging deeper into anomalies that stood out from the usual noise.

During DEFCON’s Capture the Flag competition, Snort proved invaluable as I provided network analysis and defense for our team. I used it to detect attacks and block them using the "inline" blocking capabilities based on rules written on-the-fly. When tuned properly and with the right rules, Snort is an incredibly powerful tool.

One thing that has been lacking is a free, usable, and speedy interface to the alerts produced by Snort. And free. Did I mention free, because there have been few truly usable free and open-source interfaces that are fast. Many interfaces have come and gone, but I've never actually found one I really enjoyed using that was also reasonably efficient at both reviewing alerts and drilling down into the events of interest.

I think that's why a lot of time I ended up relying on the custom scripts to query a database containing the Snort alerts. Something I should point out real quick is that I have not worked extensively with commercial products that support Snort alerts and cannot speak to their features and capabilities.

During a recent flight, I decided to try out a newly updated analysis interface called Snorby. I'd previously downloaded the Snorby "live" CD image that provides a quick way to get started with a working Snorby system. It can run directly from the CD or be installed to a hard drive. Within about five minutes, I had it installed within VMware and was ready to log into the Web interface.

The first thing I noticed was the nice-looking dashboard that is presented to the user immediately upon login. It provides a count and graph of the different High, Medium, and Low severity alerts. There is also an interactive graph and information on the right about top users, top sensors, and last five unique events.

On top of having a well-done interface, what surprised me most was Snorby's speed. I processed more than 50 GB of network traffic with Snort (and an untuned ruleset) that resulted in about 700,000 alerts that I imported into Snorby's database using Barnyard2. Browsing through the alerts using hotkeys to switch to the next page and classify alerts was surprisingly fast, and the details of each alert, including payload, was accessible quickly by just clicking on the event summary.

The caveat I must make regarding speed is that my analysis was done after all the alerts were imported and no new updates were being made to the database. In a busy environment with several sensors feeding alerts into the underlying database, Snorby's performance could be impacted.

One area within Snorby I think could be improved is the searching capabilities. The current search fields are based on the main fields in a Snort alert (signature name, IPs, ports, severity, etc.), but does not include payload, which can be very valuable during an investigation when correlating different data sources where you might have filenames or URLs you're interested in.

Also, searching for events with a particular name and choosing "Unclassified" returns all events instead of just events that have not been classified. To get around those issues, I ended up parsing through the raw Snort alerts on the command line and then using Snorby to drill down into the packet payload.

Overall, I think Snorby is a useful tool that can speed analysis of Snort alerts, helping analysts make efficient, well-informed decisions. Take it for a test drive and let me know what you think.

John Sawyer is a Senior Security Analyst with InGuardians. The views and opinions expressed in this blog are his own and do not represent the views and opinions of his employer. He can be reached at johnhsawyer@gmail.com



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS









  1. Cookies, Social Media And FireSheep
  2. SMB Guide To Credit Card Regulations, Part 2: The Low-Hanging Fruit
  3. HP And The Scary Corporate Fifth Column Concept
  4. Taking USB Attacks To The Next Level
  5. NoSQL: Not Much, Anyway
  1. Taking Cybersecurity Lessons To The Bank
  2. Researchers See Real-Time Phishing Jump
  3. 'BlackSheep' Sniffs Out Firesheep WiFi-Hacking
  4. Slideshow: Ten Free Security Monitoring Tools
  5. A Different Spin On Sleuthing Stuxnet
  6. M&A Activity Muddles Database Security
  1. Secure Managed Web Hosting Saves 960.gs from Malicious Hackers
  2. Access Governance as a Business Service: An Integrated Strategy for Automation with ITSM
  3. Business Driven Access Management and Governance: Simplifying the Delivery and Governance of Access Throughout
 
 


 
  Ars Technica
Boing Boing
Channel 9 Forums
CRN Blogs
Dr.Dobb's Portal: Blogs
Engadget
Gizmodo
GrokLaw
  Lifehacker
Schneier on Security
Slashdot
TechCrunch
Techdirt
Techmeme
Valleywag
 
  May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
  June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
 
Featured Webcasts
Featured Whitepapers
Featured Reports