From: John Jasen <jjasen@gmail.com>
To: linux-audit@redhat.com
Subject: Re: CIS and audit rules
Date: Wed, 2 Sep 2015 19:01:50 -0400 [thread overview]
Message-ID: <55E77FDE.6020803@gmail.com> (raw)
In-Reply-To: <23396023F719ED41888885C3B22D602F03714E@WPEXCH2010MR11.bur.hydro.qc.ca>
[-- Attachment #1.1: Type: text/plain, Size: 844 bytes --]
I've been testing a variant of the CIS benchmarks, supplemented (for
compliance reasons) by the NIST USGCB baselines.
I've also been testing auditd with setuid/setgid binaries.
Also as a potential replacement for aide (again, mostly compliance reasons).
Your use of auditd rules depends a lot on your drivers for doing so, and
your desired results.
On 08/28/2015 04:12 PM, Alarie, Maxime wrote:
>
>
>
> Anyone ever implemented auditd by following the CIS standards
> described here?
> https://benchmarks.cisecurity.org/downloads/show-single/?file=suse11.110
>
>
>
> Is it too restrictive? Not enough? Too much ressources consuming? I
> would like some comments/opinions if possible.
>
>
>
>
>
> Many thanks.
>
>
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
[-- Attachment #1.2: Type: text/html, Size: 3639 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-09-02 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 20:12 CIS and audit rules Alarie, Maxime
2015-09-02 23:01 ` John Jasen [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=55E77FDE.6020803@gmail.com \
--to=jjasen@gmail.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.