From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Maupertuis Philippe <philippe.maupertuis@equensworldline.com>
Subject: Re: ANOM_ROOT_TRANS
Date: Tue, 02 Oct 2018 12:56:17 -0400 [thread overview]
Message-ID: <1661515.JbW6Cf6bEd@x2> (raw)
In-Reply-To: <3D2AB1326AB2974190FCE3F69401F790010BAE330DC6@FRVDX103.fr01.awl.atosorigin.net>
On Tuesday, October 2, 2018 7:43:04 AM EDT Maupertuis Philippe wrote:
> According to the Redhat 7 security guide ANOM_ROOT_TRANS is triggered when
> a user becomes root. It seems that using sudo doesn't trigger this event.
> I would like to know how this event is triggered.
Looking at the blame view of libaudit.h on github, this was imported as far
back as 1.7.4 over 10 years ago. Back then, work was being done around
prelude IDS and feeding it with events for correlation and escalation. That
work was mothballed when prelude upstream became inactive. Prelude support
has also been removed from audit-3.0 when it gets released.
> There are also several ANOM_ types that I can't see generated.
> Is there a document describing from where these event would come.
The event types in libaudit.h are not 100% supported. Some were supported and
are now not in use. (Can't remove them since you really might run across the
event in a heterogenous network.) Many in the ANOM and RESP categories are
placeholders for future use. The description is accurate wrt the intended
use. At the moment nothing I know of is sending that event. But the roadmap
for audit 3.1 has a mention for a basic IDS capability. That might be when
ANOM and RESP categories get better supported. I wouldn't expect sudo or su
to send these.
-Steve
prev parent reply other threads:[~2018-10-02 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 11:43 ANOM_ROOT_TRANS Maupertuis Philippe
2018-10-02 16:56 ` Steve Grubb [this message]
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=1661515.JbW6Cf6bEd@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=philippe.maupertuis@equensworldline.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