From: John Dennis <jdennis@redhat.com>
To: kunal chandarana <chandarana.kunal@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: Linux-audit Digest, Vol 40, Issue 9
Date: Wed, 16 Jan 2008 07:27:14 -0500 [thread overview]
Message-ID: <478DF822.7010809@redhat.com> (raw)
In-Reply-To: <770716a30801152259l3b97d79crea2de5bd66033d1e@mail.gmail.com>
kunal chandarana wrote:
> In audit logs fields are generated for specific type. Each log has
> different type and depending on type there are different fields shown in
> audit.log files. Is there a way to map this audit type to the fields.
>
> Like if i have type=XYZ then log will contain n fields. So how to find
> these N fields.?
I'm not sure if you're asking how do you know which fields will appear
for a specific type or how can you easily parse the fields.
If it's the former there is no such mapping I'm familiar with, there is
however a dictionary with all the possible fields in the set of all
messages (http://people.redhat.com/sgrubb/audit/audit-parse.txt)
The field names are a product of the current kernel and the auditing
messages it happens to contain. I don't think anybody has gone through
the source code to produce such a map. In addition the message are
subject to change based on the discretion of kernel developers. This is
one of the frustrations of the current auditing system. However, the
messages have been fairly stable so over time it's possible to get a
pretty good idea. The source code in the kernel which produces the
messages is pretty regular, I don't think it would be too hard to write
a tool which scanned the kernel source tree and produced such a map, but
I'm not aware of such a tool ATM.
If you want to find the fields in the sense of parsing then the auparse
library will be of help.
--
John Dennis <jdennis@redhat.com>
next prev parent reply other threads:[~2008-01-16 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080114170028.0385D73507@hormel.redhat.com>
2008-01-16 6:59 ` Linux-audit Digest, Vol 40, Issue 9 kunal chandarana
2008-01-16 12:27 ` John Dennis [this message]
2008-01-16 13:59 ` 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=478DF822.7010809@redhat.com \
--to=jdennis@redhat.com \
--cc=chandarana.kunal@gmail.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