From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: questions about auditing on a new RH 6 box
Date: Fri, 14 Jan 2011 14:57:23 -0500 [thread overview]
Message-ID: <201101141457.23256.sgrubb@redhat.com> (raw)
In-Reply-To: <BF796A1F2058044191F8440424A4212E01A64DD3@enid.usno.navy.mil>
On Friday, January 14, 2011 02:26:40 pm Tangren, Bill wrote:
> #Ensure that failed attempts at using the following system calls are
> audited
> -a exit,always -F arch=b64 -S mknod -S acct -S swapon -S sethostname -F
> success=1 -F exit!=-11
>
> Which says audit mknod calls that are successful and the exit code is not
> EAGAIN.
>
> Are you sure this is what you intended?
>
> ******************
> The comments above each line are excerpts from the regulations.
The last rule does not match the comment for starters. It would be something like
this:
-a exit,always -F arch=b64 -S mknod -S acct -S swapon -S sethostname -F
success=0
But this is overlapping the other rules right above it. Let's look:
#Ensure that the following system calls are audited for the current logged in
#user and for root
#Ensure that failed attempts at using the following system calls are audited
So the first is all use for anyone logged in except the system. The second one is all
failed use regardless of someone logged in or not, so that is just 2 rules (assuming
you don't want EAGAIN):
-a exit,always -F arch=b64 -S mknod -S acct -S swapon -S sethostname -F auid!=-1 -F
exit!=-11 -k user-root-syscalls
-a exit,always -F arch=b64 -S mknod -S acct -S swapon -S sethostname -F success=0 -F
exit!=-11 -k failed-syscalls
You may have other rules that do not match the requirements.
-Steve
next prev parent reply other threads:[~2011-01-14 19:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 16:21 questions about auditing on a new RH 6 box Tangren, Bill
2011-01-14 16:42 ` Eric Paris
2011-01-14 17:23 ` Tangren, Bill
2011-01-14 17:35 ` LC Bruzenak
2011-01-14 17:56 ` Tangren, Bill
2011-01-14 18:39 ` LC Bruzenak
2011-01-14 19:04 ` Tangren, Bill
2011-01-14 18:10 ` Tangren, Bill
2011-01-14 19:12 ` Steve Grubb
2011-01-14 19:26 ` Tangren, Bill
2011-01-14 19:57 ` Steve Grubb [this message]
2011-01-14 18:58 ` Steve Grubb
2011-01-14 19:07 ` Tangren, Bill
2011-01-14 19:24 ` LC Bruzenak
2011-01-14 19:27 ` Tangren, Bill
2011-01-14 19:39 ` 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=201101141457.23256.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