From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Richard Guy Briggs <rgb@redhat.com>,
"Kadirvadivelu,
Vezhavendan 1. (EXT - IN/Chennai)"
<vezhavendan.1.kadirvadivelu.ext@nokia.com>
Subject: Re: Security audit rules
Date: Fri, 22 Nov 2019 12:08:31 -0500 [thread overview]
Message-ID: <2526162.J9WsBpnIYZ@x2> (raw)
In-Reply-To: <AM0PR07MB4148C22E0204056F7EB36DC7B24F0@AM0PR07MB4148.eurprd07.prod.outlook.com>
On Tuesday, November 19, 2019 11:36:38 PM EST Kadirvadivelu, Vezhavendan 1.
(EXT - IN/Chennai) wrote:
> I am using RHEL7.6 version (Red Hat Enterprise Linux 7 (Maipo)).
This distribution wants rules placed in /etc/audit/rules.d/
The audit package should have a file named README-rules that explains what is
expected.
-Steve
> -----Original Message-----
> From: Richard Guy Briggs <rgb@redhat.com>
> Sent: Wednesday, November 20, 2019 4:03 AM
> To: Kadirvadivelu, Vezhavendan 1. (EXT - IN/Chennai)
> <vezhavendan.1.kadirvadivelu.ext@nokia.com> Cc: linux-audit@redhat.com
> Subject: Re: Security audit rules
>
> On 2019-11-08 12:52, Kadirvadivelu, Vezhavendan 1. (EXT - IN/Chennai)
wrote:
> > Hi,
> >
> > In one of the VM I find audit.rules defined under /etc/audit as well as
> > /etc/audit/rules.d.
> >
> > What is the significance as well as difference between the files found in
> > 2 places.
> You haven't said what distro you are using. In more recent distros, the
> rules in rules.d are used by augenrules to populate audit.rules,
> overwriting them.
> > Also please let me know what is the correct location where audit.rules
> > need to be places.
> Depends on your distro.
>
> > Vezhavendan K
>
> - RGB
>
> --
> Richard Guy Briggs <rgb@redhat.com>
> Sr. S/W Engineer, Kernel Security, Base Operating Systems Remote, Ottawa,
> Red Hat Canada IRC: rgb, SunRaycer
> Voice: +1.647.777.2635, Internal: (81) 32635
>
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2019-11-22 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 12:52 Security audit rules Kadirvadivelu, Vezhavendan 1. (EXT - IN/Chennai)
2019-11-19 22:32 ` Richard Guy Briggs
2019-11-20 4:36 ` Kadirvadivelu, Vezhavendan 1. (EXT - IN/Chennai)
2019-11-22 17:08 ` Steve Grubb [this message]
2019-11-24 6:44 ` Kadirvadivelu, Vezhavendan 1. (EXT - IN/Chennai)
2019-11-25 13:37 ` Steve Grubb
2019-11-26 5:23 ` Kadirvadivelu, Vezhavendan 1. (EXT - IN/Chennai)
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=2526162.J9WsBpnIYZ@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=rgb@redhat.com \
--cc=vezhavendan.1.kadirvadivelu.ext@nokia.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