All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: STIG issue with auditctl -l
Date: Thu, 20 Nov 2014 12:08:51 -0500	[thread overview]
Message-ID: <32197423.hiQ8eKy0QW@x2> (raw)
In-Reply-To: <CACv9p5oAE5eQkFTgChTV+0KecHaiSyq+Dm2E8pLSyv_zKSwLwA@mail.gmail.com>

On Thursday, November 20, 2014 11:56:50 AM leam hall wrote:
> Steve, as always I appreciate your fast response and awesome help! I'm
> collating stuff to send up the chain.

I discussed this a couple weeks back on the SCAP Security Guide mail list:

https://lists.fedorahosted.org/pipermail/scap-security-guide/2014-October/006251.html

You might want to review that thread because I pointed out a couple more
mistakes that its making. Not to mention, if you have to STIG a box, wouldn't
you want to have a scanner to tell you that you are in compliance? SSG + 
openscap solves this problem in an open source way.

-Steve

      reply	other threads:[~2014-11-20 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 15:42 STIG issue with auditctl -l leam hall
2014-11-20 15:52 ` LC Bruzenak
2014-11-20 16:03   ` leam hall
2014-11-20 16:10 ` Steve Grubb
2014-11-20 16:56   ` leam hall
2014-11-20 17:08     ` 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=32197423.hiQ8eKy0QW@x2 \
    --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 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.