Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Steve <mckinneysj@ornl.gov>
Subject: Re: Monitoring events
Date: Thu, 8 Jun 2006 10:39:07 -0400	[thread overview]
Message-ID: <200606081039.07731.sgrubb@redhat.com> (raw)
In-Reply-To: <44883291.90804@ornl.gov>

On Thursday 08 June 2006 10:22, Steve wrote:
> >> Ideally, I would like to only capture (or parse) events pertaining to
> >> rules I have created (since other system processes are using auditd as
> >> well).  Is there's any kind of identifier that ties events to rules?
> >
> > Which kernel are you using? Are your events only watches or do you care
> > about syscall auditing as well (meaning you have set some syscall audit
> > rules) ?
>
> kernel-2.6.16-1.2212.2.8_FC6.lspp.34.i686 on Fedora Core 5
>
> At the moment they are only watches,

OK, the lspp series (so far) does not support the idea of a "key tag" as RHEL4 
did. The key would have allowed you to recognize events you are interested 
in. That said, you can look for events that have an AUDIT_PATH record in 
them. Those would likely be yours.

> I may add others (syscall rules) later.

That would complicate the analysis somewhat. But you could still do it. You 
can also look over the list of message types and see which ones you do not 
want and reject those early in the filtering.

-Steve

  reply	other threads:[~2006-06-08 14:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 13:55 Monitoring events Steve
2006-06-08 14:04 ` Steve Grubb
2006-06-08 14:22   ` Steve
2006-06-08 14:39     ` Steve Grubb [this message]
2006-06-08 14:57       ` Steve
2006-06-08 15: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=200606081039.07731.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=mckinneysj@ornl.gov \
    /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