public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: David Flatley <dflatley@us.ibm.com>
Cc: linux-audit@redhat.com
Subject: Re: question
Date: Mon, 3 Nov 2008 09:15:45 -0500	[thread overview]
Message-ID: <200811030915.45658.sgrubb@redhat.com> (raw)
In-Reply-To: <OFC0349C66.65A15027-ON852574F6.000CB0A0-852574F6.000EE991@us.ibm.com>

On Sunday 02 November 2008 21:42:47 David Flatley wrote:
> Presently I am using the S.T.I.G. recommendations but I may
> have to use more extensive rules which I am in the process of testing.

Are you using the stig.rules from the audit package or something else? If I 
were you, I'd spend some time making sure your rules are tuned. Assuming that 
you have keys on you rules, you can run a key report to see what is causing 
you the most events: aureport --start this-week --key --summary. 

Then you'd want to dig into some of those records and see what kinds of things 
are happening. Assuming you have a key of delete and you wanted to see what 
syscalls are the most often logged:

ausearch --start this-week -k delete --raw | aureport --syscall --summary -i

Assuming that shows unlinkat the most prevalent syscall:

ausearch --start this-week -k delete -sc unlinkat --raw | 
aureport --user --summary -i

And so on until you see what is causing so much logging. This doesn't help 
with the archiving, but could help you get the right audit data recorded.

-Steve

  reply	other threads:[~2008-11-03 14:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 18:21 question David Flatley
2008-10-31 19:50 ` question Steve Grubb
2008-11-02 17:24   ` question David Flatley
2008-11-03  2:42     ` question David Flatley
2008-11-03 14:15       ` Steve Grubb [this message]
2008-11-03 17:21         ` question David Flatley
2008-11-03 17:57           ` question Steve Grubb
2008-11-02 18:25   ` question LC Bruzenak
2008-11-03  3:54     ` question David Flatley

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=200811030915.45658.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=dflatley@us.ibm.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