From: "Christian, Mark" <mark.christian@intel.com>
To: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: Security Auditd Config for Enterprises
Date: Fri, 4 Sep 2020 15:27:48 +0000 [thread overview]
Message-ID: <50bd1306d7e3aff619a83f83e6c7a46e614ceb29.camel@intel.com> (raw)
In-Reply-To: <CAHvE9BK5+oRZrUCOkJ+Ong8z-R2ZVOmi-CZfddXJboRqWOGRkA@mail.gmail.com>
On Fri, 2020-09-04 at 19:08 +0530, Rohit Nambiar wrote:
> Hi all!
>
> Apologies if this topic has already been discussed before, I couldn't
> find an easy way to sift through older archives.
>
> Is there an auditd rule set which offers a reasonable level of
> security visibility and has been tested on enterprise production
> systems? And if such a rule set can be shared here?
>
> I'm looking for a base document to deploy/modify for use within my
> organization. Many thanks in advance.
consider:
https://github.com/linux-audit/audit-userspace/tree/master/rules
Depending on the age of your auditd, these examples may not work for
you, so test and verify.
Mark
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2020-09-04 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 13:38 Security Auditd Config for Enterprises Rohit Nambiar
2020-09-04 15:27 ` Christian, Mark [this message]
2020-09-04 15:41 ` 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=50bd1306d7e3aff619a83f83e6c7a46e614ceb29.camel@intel.com \
--to=mark.christian@intel.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;
as well as URLs for NNTP newsgroup(s).