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: NISPOM Auditing
Date: Wed, 21 May 2008 13:14:32 -0400	[thread overview]
Message-ID: <200805211314.32834.sgrubb@redhat.com> (raw)
In-Reply-To: <673954B3D6E9A14199B78659C4AD37EE0422D137@emss04m05.us.lmco.com>

On Wednesday 21 May 2008 12:01:52 Mathis, Jim wrote:
> Is there a way to setup a watch log to report if a user attempted to
> "cd" to a directory that they didn't have permission to access.

No, a watch applies to file ops and not the chdir syscall. However, you can 
create a syscall audit rule that works sometimes:

-a always,exit -S chdir -F path=/dir/dir1/dir2 -k evil-cd

This will catch the case where they have permission to cd into that directory. 
But if they don't have permission to go beyond dir in the above example, then 
you have to resort to something more like:

-a always,exit -S chdir -F exit=-EACCES -k evil-cd

Which gets it and every other cd that fails due to permissions. This is 
because the path lookup inside the kernel never completes due to permissions, 
so the audit system has no full path to check against. You can cut down the 
false positives by adding -F auid>=500. And also use the -F arch=b32   and 
b64 for biarch systems.

-Steve

  reply	other threads:[~2008-05-21 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 16:01 NISPOM Auditing Mathis, Jim
2008-05-21 17:14 ` Steve Grubb [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-22 20:28 Mathis, Jim
2008-05-22 21:19 ` Steve Grubb
2008-05-27 14:00   ` corbin
2008-05-27 14:19     ` 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=200805211314.32834.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