From: LC Bruzenak <lenny@magitekltd.com>
To: "Pittigher, Raymond - ES" <Raymond.Pittigher@itt.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: log files
Date: Fri, 17 Jun 2011 13:27:00 -0500 [thread overview]
Message-ID: <1308335220.7213.6.camel@lcb> (raw)
In-Reply-To: <6815A555A0B82148AEFE4966093BBBF5366DD7A644@USFWA1EXMBX3.itt.net>
On Fri, 2011-06-17 at 14:15 -0400, Pittigher, Raymond - ES wrote:
> What do the users of this list use to read the log files? I have tried
> Spacewalk (which is nice) but is a lot of software to install to read
> logs. I have looked at Prewikka but do not have it totally configured
> yet to give it a OK or not.
My experiences (I assume you specifically mean the audit logs):
Prewikka would be for IDS events only with the prelude plugin.
I use the audit-viewer with pre-constructed list tabs to match events
necessary for verification testing.
For faster results when looking for specific events or investigation, I
use the command line tools aureport and ausearch.
What would be great IMHO is to have a prewikka-like web interface for
the audit events.
HTH,
LCB
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next prev parent reply other threads:[~2011-06-17 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 18:15 log files Pittigher, Raymond - ES
2011-06-17 18:27 ` LC Bruzenak [this message]
2011-06-17 18:32 ` Pittigher, Raymond - ES
2011-06-17 18:57 ` Dominick Grift
[not found] ` <1308337014.7213.10.camel@lcb>
2011-06-17 19:15 ` Pittigher, Raymond - ES
2011-06-17 19:56 ` LC Bruzenak
2011-06-17 21:33 ` Pittigher, Raymond - ES
2011-06-17 18:38 ` Steve Grubb
-- strict thread matches above, loose matches on Subject: below --
2004-06-17 7:48 Log Files Patrick Nelson
2004-06-17 7:55 ` Marc Haber
2003-07-03 6:13 Log files Steven Mugassa
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=1308335220.7213.6.camel@lcb \
--to=lenny@magitekltd.com \
--cc=Raymond.Pittigher@itt.com \
--cc=linux-audit@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.