From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Filesystem filling up ...
Date: Tue, 3 Jul 2007 17:13:12 -0400 [thread overview]
Message-ID: <200707031713.12553.sgrubb@redhat.com> (raw)
In-Reply-To: <39d2723b0706271042y2885144dj29e7da8adc90e630@mail.gmail.com>
On Wednesday 27 June 2007 01:42:39 pm Aaron Lippold wrote:
> I was hoping some smarter audit folks than I could look at this small
> set of rules and let me know if anythings seem: 1) way too broad 2)
> would fill up a file system fast 3) could use improvement
> # Audit Failed opens
> -a exit,always -S open -F success!=0
Maybe:
-a exit,always -S open -F exit=-13
-a exit,always -S open -F exit=-1
> #
> # Audit success and failure of delete
> -a exit,always -S unlink -S rmdir
> #
> # Audit success and failure of admin actions
> #-a task,always -F uid=0
> -w /var/log/audit/ -k ADMIN
> -w /etc/auditd.conf -k ADMIN
> -w /etc/audit.rules -k ADMIN
> -a exit,always -S stime -S acct -S reboot -S swapon -S settimeofday -S
> setrlimit -a exit,always -S setdomainname -S sched_setparam -S
> sched_setscheduler EOF
Some of these may be broad. setrlimit for example.
> Some of my end users are saying their logging a lot of audits. We are
> using the same kickstart file but my test systems are not filling up.
You might be able to do some work with aureport to find out what is filling
your logs. Something like:
aureport --start this-week --summary -i --event
aureport --start this-week --summary -i --syscall
-Steve
next prev parent reply other threads:[~2007-07-03 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 17:42 Filesystem filling up Aaron Lippold
2007-06-27 18:17 ` Stephen John Smoogen
2007-06-29 15:39 ` Valdis.Kletnieks
2007-07-03 21:13 ` Steve Grubb [this message]
2007-07-07 20:42 ` Aaron Lippold
2007-07-08 20:17 ` 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=200707031713.12553.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