public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: LC Bruzenak <lenny@magitekltd.com>
Cc: linux-audit@redhat.com
Subject: Re: Audit format utility
Date: Thu, 25 Sep 2014 23:05:37 -0400	[thread overview]
Message-ID: <20140925230537.5a6b5eb0@ivy-bridge> (raw)
In-Reply-To: <54243FE1.3090800@magitekltd.com>

Hello,

On Thu, 25 Sep 2014 11:16:33 -0500
LC Bruzenak <lenny@magitekltd.com> wrote:
> On 09/23/2014 05:03 PM, Steve Grubb wrote:
> > Hello,
> >
> > I have been doing some thinking about allowing user defined formats
> > to be declared as a parameter to ausearch. Before I commit to that,
> > I thought it might be interesting to create a "mockup". I have
> > placed a utility here:
> >
> Steve,
> 
> I'll be testing this ASAP to see what shakes out for me.
> For user-defined formats, are you thinking maybe along the lines of
> allowing a regexp ability to ausearch which would be like the
> ausearch-expression capability in libauparse?

Not exactly. A regex would be for searching for events that match some
criteria. That might be useful in and of itself. What this proposal is
about is allowing one to specify how an event is output. For example,
you may want some kind of xml looking thing. Or maybe html, or maybe
json looking. Or maybe you just want it your way...just because.

I know one of the limitations is that each event is unique. I am
planning to address this in the near future by having a classifier that
you just ask, what is the subject, what is the object, what was the
action, what was the result. It would supply the answer. Then I could
go back to this and add some new classifier virtual fields that could
be $SUBJECT, $OBJECT, etc.

But this proposal is purely about output and not searching.

-Steve

  reply	other threads:[~2014-09-26  3:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 22:03 Audit format utility Steve Grubb
2014-09-25 16:16 ` LC Bruzenak
2014-09-26  3:05   ` Steve Grubb [this message]
2014-09-26 15:24     ` LC Bruzenak
2014-09-28  4:52       ` Burn Alting
2014-10-01 18:44         ` Steve Grubb
2014-10-01 21:44           ` Burn Alting
2014-10-02 21:23             ` 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=20140925230537.5a6b5eb0@ivy-bridge \
    --to=sgrubb@redhat.com \
    --cc=lenny@magitekltd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox