From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: auditd rule error
Date: Mon, 11 Jun 2018 10:27:32 -0400 [thread overview]
Message-ID: <1545206.YeD5i4ib4z@x2> (raw)
In-Reply-To: <SN1P100MB007720E9DB4F79F781DC29E7F2780@SN1P100MB0077.NAMP100.PROD.OUTLOOK.COM>
On Monday, June 11, 2018 8:39:26 AM EDT Joshua Ammons wrote:
> On a server running RHEL 7.2 the audit rules fail to load due to an error
> on this rule:
>
> -a always,exit -F arch=b64 -S setuid -F a0=0 -F exe=/usr/bin/su -F
> key=10.2.5.b-elevated-privs-session
>
> From what I have found it seems "exe" may not be a valid field on this
> specific O.S. - is this correct?
That might have been targeted for the 7.4 kernel.
> Does anyone have any recommendations on how to track elevated privileges
> for all RHEL 6/7 systems?
The exe field is used for what we call audit by executable. This is for when
you want to zero in on a particular program performing some action like
calling accept. If you simply want notification that an application was
invoked, the you would just setup a watch for execute.
-a always,exit -F path=/usr/bin/su -F perm=x -F key=10.2.5.b-elevated-privs-
session
That should work across RHEL 6 & 7. Also, you will get events from pam as the
user authenticates and starts the session. So, you should be able to find
those with this search:
ausearch --start today -x /usr/bin/su -m USER_START -w -i
-Steve
next prev parent reply other threads:[~2018-06-11 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 12:39 auditd rule error Joshua Ammons
2018-06-11 14:27 ` Steve Grubb [this message]
2018-06-11 14:49 ` Joshua Ammons
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=1545206.YeD5i4ib4z@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