From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: How to monitor audit/audispd killed
Date: Mon, 04 Jan 2016 09:32:47 -0500 [thread overview]
Message-ID: <4152899.8YOsTRPv25@x2> (raw)
In-Reply-To: <CAH8ERfatWjaVOyawRPT9Zb8cBE=3cYWoxd4Y5YYU_E7c8rozaQ@mail.gmail.com>
On Monday, January 04, 2016 08:10:29 PM Matthew Chao wrote:
> Hi,
>
> I added the following rules in audit.rules for monitoring auditd/audispd be
> killed(audit ver: 1.8),
> =============
> -a exit,always -F perm=wa -F path=/var/run/auditd.pid -k cfg
>
> -a exit,always -F perm=wa -F path=/var/run/audispd_events -k cfg
>
> Or
> -a exit,always -S kill -F path=/var/run/auditd.pid -k cfg
>
> -a exit,always -S kill -F path=/var/run/audispd_events -k cfg
> =============
>
> However, these rules don't work:
You have a race condition where auditd gets a signal to shutdown and an event
indicating that shutdown is occurring. On shutdown, the audit daemon does not
alter the rules or whether auditing is enabled. (This was to get shutdown AVCs
for selinux.) There is a chance that your event is in syslog's files.
> even the processes (auditd/audispd) are killed, I can't get any related
> messages except DAEMON_END.
The daemon end event should give you 2 things, who issued the shutdown (auid)
and the sending pid. That should let you track it down.
-Steve
next prev parent reply other threads:[~2016-01-04 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 12:10 How to monitor audit/audispd killed Matthew Chao
2016-01-04 14:12 ` Richard Guy Briggs
2016-01-04 19:49 ` Matthew Chao
2016-01-04 14:32 ` Steve Grubb [this message]
2016-01-04 19:29 ` Matthew Chao
2016-01-04 19:43 ` Steve Grubb
2016-01-04 19:51 ` Matthew Chao
2016-01-05 10:08 ` Matthew Chao
2016-01-05 14:10 ` Steve Grubb
2016-01-05 16:12 ` Matthew Chao
2016-01-05 17:48 ` Steve Grubb
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=4152899.8YOsTRPv25@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