Snort Alert Monitor Changelog

What's new in Snort Alert Monitor 0.6.0

Dec 10, 2009
  • Add database table prefix
  • Add MaxMind's database
  • Add style to the user's table
  • Nagios check not correctly providing perf data
  • Removed redundant arin link on events page
  • Add preference page to iPhone site
  • Add ability to map where threats are coming from
  • Add authentication
  • Add Country code to IP addresses on the dashboard
  • Color code priority

New in Snort Alert Monitor 0.4.2 (Dec 4, 2008)

  • A bug where the threat index wasn't being calculated correctly was fixed.
  • A bug where high priority attacks on the dashboard weren't being filtered correctly was fixed.

New in Snort Alert Monitor 0.4.1 (Nov 26, 2008)

  • The events page didn't understand the minutes_ago param, so clicking a link from the dashboard would force the events page to run through the full database instead of that timeframe.
  • Also, the Threat Index didn't include high and medium severities in the same calculation, so you might see the same IP twice, and not the aggregate as you should have.
  • These issues have been fixed.

New in Snort Alert Monitor 0.4.0 (Nov 23, 2008)

  • A bug was fixed so that the default dashboard now shows the correct timeframe.
  • Dashboard widgets now refresh automatically.
  • ARIN links were added to all IP addresses.
  • A visual cue was added for high threat indexes.

New in Snort Alert Monitor 0.3.0 (Nov 17, 2008)

  • An iPhone Web version was added.
  • JSON and XML API support was added.
  • CSV export options were added to the events page.

New in Snort Alert Monitor 0.2.0 (Nov 2, 2008)

  • Postgres support was added.
  • Online signature references were added.
  • UI cleanup was done.
  • An about page was added that lists contributors, libraries, and other contributions made directly and indirectly.

New in Snort Alert Monitor 0.1.0 (Oct 15, 2008)

  • A Ruby on Rails Web interface is now used instead of a Java GUI.
  • All features from the GUI are available in the new version and many more.
  • There is currently no README for the deployment, but the only requirements are Ruby on Rails 2.1 and MySQL.