From: Steve Grubb <sgrubb@redhat.com>
To: "Wyatt, Curtis" <Curtis.Wyatt@gd-ms.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: Why exclude unset auid in STIG rules
Date: Wed, 11 May 2016 14:34:51 -0400 [thread overview]
Message-ID: <6776565.2lPe2APqfW@x2> (raw)
In-Reply-To: <A08CED02BC8EFC4B89CE0E0B16F995C4389B9DF6@azrc4sazmsg10.rc4s.com>
On Wednesday, May 11, 2016 06:28:11 PM Wyatt, Curtis wrote:
> I don't understand why the STIG audit rules have -F auid!=4294967295 in it.
> If auid is unset, why wouldn't you still want to see the events in the
> logs?
When a user logs in, the auid gets set to the uid that they used to login
with. Daemons are not user sessions and have the loginuid set to -1. The auid
representation is an unsigned 32 bit integer. So, -1 becomes 4294967295. The
rules use a directive like this: -F auid>=1000 to trigger on user activity. It
turns out that would trigger on daemons doing something because 4294967295 is
greater than 1000. So, we exclude daemons because user activity is the prime
target.
-Steve
next parent reply other threads:[~2016-05-11 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A08CED02BC8EFC4B89CE0E0B16F995C4389B9DF6@azrc4sazmsg10.rc4s.com>
2016-05-11 18:34 ` Steve Grubb [this message]
2016-05-11 18:40 ` Why exclude unset auid in STIG rules Wyatt, Curtis
2016-05-11 19:10 ` Steve Grubb
2016-05-11 20:16 ` Wyatt, Curtis
2016-05-11 20:43 ` Warron S French
2016-05-11 18:32 Wyatt, Curtis
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=6776565.2lPe2APqfW@x2 \
--to=sgrubb@redhat.com \
--cc=Curtis.Wyatt@gd-ms.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