From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Maupertuis Philippe <philippe.maupertuis@equensworldline.com>
Subject: Re: how to audit auditd itself ?
Date: Fri, 01 Sep 2017 11:11:00 -0400 [thread overview]
Message-ID: <1735740.xhVOEyZN6B@x2> (raw)
In-Reply-To: <3D2AB1326AB2974190FCE3F69401F7900102F2B4BC5F@FRVDX103.fr01.awl.atosorigin.net>
On Friday, September 1, 2017 8:58:47 AM EDT Maupertuis Philippe wrote:
> The 30-pci-dss-v31.rules in the doc directory contains the following
> statement : ## 10.2.6 Verify the following are logged:
> ## Initialization of audit logs
> ## Stopping or pausing of audit logs.
> ## These are handled implicitly by auditd
>
> This very good since nothing need to be done, but how can I actually find
> when these events occur ?
DAEMON_START
DAEMON_END
> I am not sure what means "pausing of audit logs",
> can we really "pause" auditd ?
In a sense you can by stopping the service.
-Steve
prev parent reply other threads:[~2017-09-01 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 12:58 how to audit auditd itself ? Maupertuis Philippe
2017-09-01 15:11 ` 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=1735740.xhVOEyZN6B@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