public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: rshaw1@umbc.edu
To: Dan White <d_e_white@icloud.com>
Cc: linux-audit@redhat.com
Subject: Re: RHEL 6 audit.rules question
Date: Thu, 31 Jul 2014 09:58:35 -0400	[thread overview]
Message-ID: <144e83098c4a9de1d34cd5504f8ad8cb.squirrel@webmail.umbc.edu> (raw)
In-Reply-To: <9bbafff9-6c53-475f-acf0-d0bf8ad07931@me.com>

> On Jul 30, 2014, at 04:33 PM, Steve Grubb <sgrubb@redhat.com> wrote:
>
>> On Wednesday, July 30, 2014 08:21:45 PM Dan White wrote:
>>        > Does the system allow for the import/include of groups of rules
>> in other
>>        > files - like logrotate and /etc/logrotate.d/* ?
>>
>> No, but in 2.3 and later there is a /etc/audit/rules.d/ directory where
>> rules
>> can be dropped off. The augenrules utility will "compile" those into a
>> master
>> audit.rules file. You also have to enable augenrules by setting
>> USE_AUGENRULES="yes" in /etc/sysconfig/audit. that is about as close as
>> it
>> comes.
>>
>> -Steve
>
> Thanks for the quick answer.
> Any plans to release 2.3.x to RHEL 6 that can be shared ?

I was able to "backport" this functionality to RHEL6 (and RHEL5) by doing
the following:

- Steal the augenrules script from a Fedora or RHEL7 package
- Use my configuration management system to create and manage files in
/etc/audit/rules.d
- Schedule periodic runs of augenrules

I didn't have to set USE_AUGENRULES (maybe because the older audit system
doesn't know to care?).  It has been working very well for me as a way of
managing differences in audit rules on systems while still keeping things
centralized.

--Ray

  reply	other threads:[~2014-07-31 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 11:59 RHEL 6 audit.rules question Dan White
2014-07-31 13:58 ` rshaw1 [this message]
2014-08-01  1:46   ` Dan White
  -- strict thread matches above, loose matches on Subject: below --
2014-07-30 20:21 Dan White
2014-07-30 20:33 ` 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=144e83098c4a9de1d34cd5504f8ad8cb.squirrel@webmail.umbc.edu \
    --to=rshaw1@umbc.edu \
    --cc=d_e_white@icloud.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