From: Steve Grubb <sgrubb@redhat.com>
To: "Wieprecht, Karen M." <Karen.Wieprecht@jhuapl.edu>
Cc: linux-audit@redhat.com, "Thomas, Daniel J." <Daniel.Thomas@jhuapl.edu>
Subject: Re: Tools for reviewing audit logs ?
Date: Tue, 12 Dec 2006 17:29:03 -0500 [thread overview]
Message-ID: <200612121729.04049.sgrubb@redhat.com> (raw)
In-Reply-To: <FC11D747323EB24493CDC753367EEB929E57BD@aplesnation.dom1.jhuapl.edu>
On Tuesday 12 December 2006 17:08, Wieprecht, Karen M. wrote:
> Steve, I'm testing the RHEL4 audit 1.0.14 now with the sample capp.rules
> , and I am generating data. UGLY data. I am wondering what
> tools/GUIs/scripts people are using to look at this data.
Some one published a perl based viewer to this mail list earlier this year. I
forget when. The aureport program was supposed to fill the immediate role of
breaking the data down into something a little more useful. My intentions are
to use that as the basis of a GUI based tool. The work is going slow and I'm
at the poiint of writing the parser library.
> but I don't want to reproduce effort if there are nice scripts or GUIs
> available already.
Aside from that perl based viewer and aureport, nothing I know of. It would be
helpful to me to know what your use cases/requirements are.
Thanks,
-Steve
next prev parent reply other threads:[~2006-12-12 22:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061211170024.6F9DF7337D@hormel.redhat.com>
2006-12-11 17:15 ` Linux-audit Digest, Vol 27, Issue 2 Thomas, Daniel J.
2006-12-11 18:20 ` Steve Grubb
2006-12-11 19:20 ` Thomas, Daniel J.
2006-12-11 19:33 ` Steve Grubb
2006-12-11 20:32 ` Wieprecht, Karen M.
2006-12-11 23:03 ` Steve Grubb
2006-12-12 2:16 ` Wieprecht, Karen M.
2006-12-12 22:08 ` Tools for reviewing audit logs ? Wieprecht, Karen M.
2006-12-12 22:29 ` Steve Grubb [this message]
2006-12-13 16:36 ` Jonathan Abbey
2006-12-13 17:21 ` Steve Grubb
2006-12-13 20:12 ` Wieprecht, Karen M.
2006-12-13 16:45 ` Wieprecht, Karen M.
2006-12-13 17:09 ` Steve Grubb
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=200612121729.04049.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=Daniel.Thomas@jhuapl.edu \
--cc=Karen.Wieprecht@jhuapl.edu \
--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.