From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: how to audit auditd itself ? Date: Fri, 01 Sep 2017 11:11:00 -0400 Message-ID: <1735740.xhVOEyZN6B@x2> References: <3D2AB1326AB2974190FCE3F69401F7900102F2B4BC5F@FRVDX103.fr01.awl.atosorigin.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <3D2AB1326AB2974190FCE3F69401F7900102F2B4BC5F@FRVDX103.fr01.awl.atosorigin.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com Cc: Maupertuis Philippe List-Id: linux-audit@redhat.com 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