From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: "MAUPERTUIS, PHILIPPE" <philippe.maupertuis@equensworldline.com>
Subject: Re: Config_change events
Date: Sat, 04 Jan 2020 16:07:02 -0500 [thread overview]
Message-ID: <6165760.8hHFWGXKb8@x2> (raw)
In-Reply-To: <5F4EE10832231F4F921A255C1D954298251E24@DEERLM99EX7MSX.ww931.my-it-solutions.net>
On Monday, December 30, 2019 12:21:15 PM EST MAUPERTUIS, PHILIPPE wrote:
> When I issue a service auditd restart, I get the following events :
> [root@xxxxxxxx ~]# ausearch -k 10.5.5-modification-audit -ts recent
> --format raw node=xxxxxxxx type=CONFIG_CHANGE
> msg=audit(1577725960.912:8745): auid=4294967295 ses=4294967295
> op=remove_rule key="10.5.5-modification-audit" list=4 res=1AUID="unset"
> node=xxxxxxxx type=CONFIG_CHANGE msg=audit(1577725960.947:8777):
> auid=4294967295 ses=4294967295 op=add_rule key="10.5.5-modification-audit"
> list=4 res=1AUID="unset"
>
> How can I link this event to the daemon_start daemon_end events ?
The best way is by a time window. Did it occur within a second of the audit
daemon starting or stopping?
> How can I trace the CONFIG_CHANGE events to a user action ?
You would have to place a watch on auditctl. In this particular case, auid
and session are -1, which means a daemon did it.
> Are the Daemon_start and daemon_end events specifically linked to auditd ?
Yes.
-Steve
prev parent reply other threads:[~2020-01-04 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 17:21 Config_change events MAUPERTUIS, PHILIPPE
2020-01-04 21:07 ` 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=6165760.8hHFWGXKb8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.