From: Brian LaMere <brianl@clinicomp.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: no logging of successful events?
Date: Mon, 18 Aug 2008 15:13:58 -0700 [thread overview]
Message-ID: <1219097638.6522.74.camel@orpheus.clinicomp.com> (raw)
In-Reply-To: <200808181652.24871.sgrubb@redhat.com>
> possible with a real life security target people have to meet. I don't have
> any feedback from disa as to whether or not they like it. :)
I have an "official" position (SYSIAO) that requires I interact with
those darn things constantly. Plus, the errors in the guides actually
cause me significant problems during scanning, with false positives and
such (because they exist in the automated scan tools too).
So, I've begun looking into getting feedback to/from the drafters of the
UNIX Checklist; I'll let you know if anything comes of it.
Brian
prev parent reply other threads:[~2008-08-18 22:13 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
2008-08-18 20:43 ` Brian LaMere
2008-08-18 20:52 ` Steve Grubb
2008-08-18 22:13 ` Brian LaMere [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=1219097638.6522.74.camel@orpheus.clinicomp.com \
--to=brianl@clinicomp.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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