All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Todd Heberlein <todd_heberlein@mac.com>
Cc: linux-audit@redhat.com
Subject: Re: Too many failed open syscalls
Date: Wed, 9 Feb 2011 17:20:44 -0500	[thread overview]
Message-ID: <201102091720.44267.sgrubb@redhat.com> (raw)
In-Reply-To: <23B4A3CF-E4F7-434C-8796-0472ADD146C4@mac.com>

On Wednesday, February 09, 2011 05:05:52 pm Todd Heberlein wrote:
> On Feb 9, 2011, at 10:17 AM, Steve Grubb wrote:
> > They go on with a table which essentially means you need to audit almost
> > everything. But you only need to worry about the failed access.
> 
> Translation: You only need to worry about failed attack. Ignore the
> successful attacks.

There are certain system objects where you have to audit both success and failure, 
e.g. /etc/shadow. However, if a file's permissions are 0644, do you really need to 
audit that the file was accessed, e.g. /etc/localtime?

-Steve

      parent reply	other threads:[~2011-02-09 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 17:09 Too many failed open syscalls Steve M. Zak
2011-02-09 18:17 ` Steve Grubb
     [not found]   ` <23B4A3CF-E4F7-434C-8796-0472ADD146C4@mac.com>
2011-02-09 22:20     ` Steve Grubb [this message]

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=201102091720.44267.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=todd_heberlein@mac.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.