From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: STIG issue with auditctl -l
Date: Thu, 20 Nov 2014 11:10:55 -0500 [thread overview]
Message-ID: <2556417.QbYXNFcFXW@x2> (raw)
In-Reply-To: <CACv9p5r8kRxZxduZVCv7dzS2YKMJWcN1siMT8KQ1QNvVgXdYTA@mail.gmail.com>
On Thursday, November 20, 2014 10:42:04 AM leam hall wrote:
> The RHEL 6 STIG says:
>
> auditctl -l | grep syscall | grep chmod
This is a forensics check of the system. A configuration scan should do
cat /etc/audit/audit.rules
> Should return lines referring to chmod. Those lines are in my
> audit.rules. Just doing an:
>
> auditctl -l | grep syscall
The format of the output changed. But the STIG is not right for mixing a
forensics check with a configuration checks. If you really needed to do a check
using auditctl, then use this:
auditctl -l | grep chmod
Just grep on the syscall and leave system out of it. You should have never
needed it unless
-Steve
next prev parent reply other threads:[~2014-11-20 16:10 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 [this message]
2014-11-20 16:56 ` leam hall
2014-11-20 17:08 ` 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=2556417.QbYXNFcFXW@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox