From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: NISPOM Auditing
Date: Thu, 22 May 2008 17:19:52 -0400 [thread overview]
Message-ID: <200805221719.53685.sgrubb@redhat.com> (raw)
In-Reply-To: <673954B3D6E9A14199B78659C4AD37EE0422D140@emss04m05.us.lmco.com>
On Thursday 22 May 2008 16:28:41 Mathis, Jim wrote:
> I need to log file edit attempts when a user doesn't have permission to
> edit a specific file. For example, a non-root user attempts to edit
> "/var/log/audit/audit'log" which has a permission setting of 640.
> Although the user won't be able to edit the file (permission denied) -
> I'd still like to log the attempt. Here's a snippet of my audit.rules
> file:
Have you looked at the latest nispom.rules file in the audit package? I have a
set of rules that should meet NISPOM requirements. If it doesn't I'd like to
know what is wrong with it so we can fix it. This set of rules looks similar
to it, but there are differences. The main difference is adding -F arch= to
each syscall rule to make sure the numbers are correct.
> ## unsuccessful creation
>
> -a exit,always -S creat -S mkdir -S mknod -S link -S symlink -F exit=-13
> -k creation
>
> -a exit,always -S mkdirat -S mknodat -S linkat -S symlinkat -F exit=-13
> -k creation
-a exit,always -F arch=b32 -S creat -S mkdir -S mknod -S link -S symlink -F
exit=-EACCES -k creation
-a exit,always -F arch=b64 -S creat -S mkdir -S mknod -S link -S symlink -F
exit=-EACCES -k creation
-a exit,always -F arch=b32 -S mkdirat -S mknodat -S linkat -S symlinkat -F
exit=-EACCES -k creation
-a exit,always -F arch=b64 -S mkdirat -S mknodat -S linkat -S symlinkat -F
exit=-EACCES -k creation
> ## unsuccessful open
>
> -a exit,always -S open -F exit=-13 -k open
-a exit,always -F arch=b32 -S open -F exit=-EACCES -k open
-a exit,always -F arch=b64 -S open -F exit=-EACCES -k open
-a exit,always -F arch=b32 -S open -F exit=-EPERM -k open
-a exit,always -F arch=b64 -S open -F exit=-EPERM -k open
> ## unsuccessful close
>
> -a exit,always -S close -F exit=-13 -k close
>
> ## unsuccessful modifications
>
> -a exit,always -S rename -S truncate -S ftruncate -F exit=-13 -k mods
>
> -a exit,always -S renameat -F exit=-13 -k mods
>
> ## unsuccessful deletion
>
> -a exit,always -S rmdir -S unlink -F exit=-13 -k delete
>
> -a exit,always -S unlinkat -F exit=-13 -k delete
>
> ## unauthorized change directory (cd)
>
> -a exit,always -S chdir -F path=/var/log/audit -k evil2-cd
:)
> ## Watch Files
>
> -w /var/log/audit/audit.log -p rwxa -k audit-log2
This rule only watches one file. There could be more. You might want a rule
like:
-w /var/log/audit -k audit-logs
-Steve
next prev parent reply other threads:[~2008-05-22 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 20:28 NISPOM Auditing Mathis, Jim
2008-05-22 21:19 ` Steve Grubb [this message]
2008-05-27 14:00 ` corbin
2008-05-27 14:19 ` Steve Grubb
-- strict thread matches above, loose matches on Subject: below --
2008-05-21 16:01 Mathis, Jim
2008-05-21 17:14 ` 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=200805221719.53685.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