From: "Derick Anderson" <danderson@vikus.com>
To: Gene Dellinger <gene@poh.com>, netfilter@lists.netfilter.org
Subject: RE: log analysis
Date: Thu, 27 Oct 2005 11:16:10 -0400 [thread overview]
Message-ID: <FAC4E024BF776842876169173CE2F01328C2@mailbox.vikus.com> (raw)
Inline.
> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org
> [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of
> Gene Dellinger
> Sent: Wednesday, October 26, 2005 11:14 PM
> To: netfilter@lists.netfilter.org
> Subject: log analysis
>
> A couple of questions:
> Anyone have a recommendation on a good log anlaysis tool for
> iptables/netfilter?
Yes. It's called Snort. =)
> How difficult is it to perform Intrusion Detection using
> iptables, any real world stories(good and bad) desired.
Next to impossible unless you start writing your own string-based
signatures and get the string match or l7 support I keep hearing about.
> Thanks
> Gene D.
>
I don't log with netfilter. I use Snort and BASE for NIDS. There are
many viable options for NIDS and HIDS (like Tripwire). In my opinion the
only purpose of the LOG/ULOG targets are testing rules on live
firewalls. The default netfilter logs don't include the packet payload
anyway, which can tell you whether the M$ command banner Snort flagged
is real or just Bugtraq.
Derick Anderson
next reply other threads:[~2005-10-27 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 15:16 Derick Anderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-27 3:13 log analysis Gene Dellinger
2005-10-27 7:33 ` Ruprecht Helms
2005-10-27 13:19 ` Bob
2005-10-27 13:22 ` Eric Leblond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FAC4E024BF776842876169173CE2F01328C2@mailbox.vikus.com \
--to=danderson@vikus.com \
--cc=gene@poh.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox