public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Brian LaMere <brianl@clinicomp.com>
Subject: Re: no logging of successful events?
Date: Mon, 18 Aug 2008 16:07:55 -0400	[thread overview]
Message-ID: <200808181607.55239.sgrubb@redhat.com> (raw)
In-Reply-To: <1219088341.6522.24.camel@orpheus.clinicomp.com>

On Monday 18 August 2008 15:39:01 Brian LaMere wrote:
> (boo for me not hitting reply-all before)
>
> Fair enough, was just basing from the man page which says:
>
> "       To see unsuccessful open call's:
>
>        auditctl -a exit,always -S open -F success!=0"

I think that was patched at some point. The current man page in svn is right. 
But I think I should touch it up a bit.


> Note that I actually got the line from the DoD requirements, which give
> that line - if that line isn't present, then they determine that "the
> audit system is not configured to audit failed attempts to access files
> and programs."

The recent versions of the audit system ships with a stig.rules file that give 
what I believe to be a correct rule set. What the official docs say to do is 
another thing. :)  Take a look at that file and see how I do the unauthorized 
file access.

HTH

-Steve

  reply	other threads:[~2008-08-18 20:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 19:09 no logging of successful events? Brian LaMere
2008-08-18 19:18 ` Steve Grubb
2008-08-18 19:25   ` Eric Paris
2008-08-18 19:49     ` Brian LaMere
2008-08-18 19:51       ` Eric Paris
2008-08-18 19:39   ` Brian LaMere
2008-08-18 20:07     ` Steve Grubb [this message]
2008-08-18 20:43       ` Brian LaMere
2008-08-18 20:52         ` Steve Grubb
2008-08-18 22:13           ` Brian LaMere

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=200808181607.55239.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=brianl@clinicomp.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