public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: How to read audit log?
Date: Tue, 25 Sep 2007 10:33:23 -0400	[thread overview]
Message-ID: <200709251033.24433.sgrubb@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.64L.0709250917510.2611@mint-square.mit.edu>

On Tuesday 25 September 2007 09:21:59 Scott Ehrlich wrote:
> Could someone please produce a sample audit log line or two and break down
> what each piece means, or direct me to a web page that does so?

For the quick view of your system, use the aureport program. It can give you 
summary information and produce reports for various aspects like failed 
logins or denied file accesses.

aureport --start this-month
aureport --start this-week --login --failed -i
aureport --start this-week --file --failed -i

But there comes a time when you just want to see the raw information since 
there are more details. ausearch is the tool for this. It understands the 
format of the logs and should be used to look at the logs since it can do 
interpretation of the fields and glue individual records into events.

ausearch --start today -i | less

What each field means can be found in the audit parsing library specification:

http://people.redhat.com/sgrubb/audit/audit-parse.txt

It gives an overview of the records in the top portion before it gets to the 
functions in the library.

> I had initially expected some form of date/time stamp, but looking at the
> first set of decimal-separated digits couldn't help me decipher a
> date/time.

ausearch is intended to be the audit log display tool.

-Steve

  reply	other threads:[~2007-09-25 14:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25 13:21 How to read audit log? Scott Ehrlich
2007-09-25 14:33 ` Steve Grubb [this message]
2007-09-25 14:34 ` John Dennis
2007-09-25 14:50   ` Wieprecht, Karen M.
2007-09-25 15:02     ` Steve Grubb
2007-09-25 16:43       ` James Antill
2007-09-25 17:02         ` Steve Grubb
2007-09-25 17:47           ` Todd, Charles

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=200709251033.24433.sgrubb@redhat.com \
    --to=sgrubb@redhat.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