|
|||||||||||
|
Re: [Security Basics] Portsentry and Snort
From: Dan DeVoe <ddevoe(at)zeus.netset.com>
Date: Fri May 09 2003 - 12:39:42 EDT
Snort, in my opinion, is primarily useful for sticking on a bridge in front of the machines you're protecting. Custom patterns combined with acidlab really does let one sleep better at night. The reason that I prefer to use snort in a standalone configuration is mainly the curve between CPU usage and network traffic. YMMV. Snort, though, is definitely a useful tool. PortSentry, in addition to apparently not being a supported, developed product anymore, is of questionable value anyway. A decently strict, logging iptables setup plus fwlogwatch[0] provides more functionality (user-configurable response rather than simply throwing up a drop rule). In addition, fwlogwatch can send out nightly (or another interval) summary e-mails of logged packets, and generate HTML formatted pages of the same data. Should you decide to go with a logging firewall and fwlogwatch, I suggest you look into ulogd[1] so that you don't clutter your /var/log/messages. [0]: http://cert.uni-stuttgart.de/projects/fwlogwatch/ [1]: http://gnumonks.org/projects/ulogd -- Dan DeVoe, System Administrator | http://www.netset.com Ohio NetSet Enterprises, Inc. | (614) 527-9111 **************************************************************** -* Opinions herein are the author's and are not necessarily *- -* shared by his employer, though they certainly should be. *- **************************************************************** On Thu, 8 May 2003, sjm wrote:Received on Fri May 9 15:12:53 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:04:18 EDT |
||||||||||
|
|||||||||||