Snort mailing list archives
Sensor 'sanity'
From: "Paul Halliday" <paul.halliday () gmail com>
Date: Thu, 8 Nov 2007 21:33:24 -0400
Hi, I am not sure about how most people deal with this but I would love any insight. In an overtaxed environment where I just don't have the time to coddle each sensor, what is a common practice to make sure that the sensors are actually still sane? Most of my sensors are sittings on span/mirrored ports on gear that I don't directly manage. Is/would it be possible to construct a preprocessor that could actually fire and tell me that the link isn't 'typical' anymore? Thanks. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Snort-users mailing list Snort-users () lists sourceforge net Go to this URL to change user options or unsubscribe: https://lists.sourceforge.net/lists/listinfo/snort-users Snort-users list archive: http://www.geocrawler.com/redir-sf.php3?list=snort-users
Current thread:
- Sensor 'sanity' Paul Halliday (Nov 08)
- Message not available
- Re: Sensor 'sanity' Paul Halliday (Nov 09)
- Message not available
- Re: Sensor 'sanity' Jason Haar (Nov 11)
- snort virtualization Youngquist, Jason R. (Nov 14)
- Re: snort virtualization Justin Heath (Nov 14)
- snort virtualization Youngquist, Jason R. (Nov 14)