public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
* Auditd syslog plugin
@ 2018-06-04 13:02 Boyce, Kevin P [US] (AS)
  2018-06-04 22:11 ` Steve Grubb
  0 siblings, 1 reply; 3+ messages in thread
From: Boyce, Kevin P [US] (AS) @ 2018-06-04 13:02 UTC (permalink / raw)
  To: linux-audit@redhat.com


[-- Attachment #1.1: Type: text/plain, Size: 360 bytes --]

All,

After enabling the syslog plugin for audispd and sending logs to a remote server I am seeing every event being written to /var/log/messages locally which is filling up /var.

This is all redundant since local audit logs are kept in /var/log/audit.  Is there a way to prevent auditd syslog plugin from writing to /var/log/messages?

Thanks,
Kevin

[-- Attachment #1.2: Type: text/html, Size: 2293 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Auditd syslog plugin
  2018-06-04 13:02 Auditd syslog plugin Boyce, Kevin P [US] (AS)
@ 2018-06-04 22:11 ` Steve Grubb
  2018-06-04 23:32   ` John Jasen
  0 siblings, 1 reply; 3+ messages in thread
From: Steve Grubb @ 2018-06-04 22:11 UTC (permalink / raw)
  To: linux-audit

On Monday, June 4, 2018 9:02:04 AM EDT Boyce, Kevin P [US] (AS) wrote:
> All,
> 
> After enabling the syslog plugin for audispd and sending logs to a remote
> server I am seeing every event being written to /var/log/messages locally
> which is filling up /var.
> 
> This is all redundant since local audit logs are kept in /var/log/audit. 
> Is there a way to prevent auditd syslog plugin from writing to
> /var/log/messages?

That is pretty much what the plugin does. It writes all events to syslog 
which based on rules in /etc/rsyslog.conf decides what to do with the text. 
Typically it is to write everything to /var/log/messages.

However, you can assign a specific facility to the audit events in the /etc/
audisp/plugins.d/syslog.conf file and then in rsyslog.conf exclude the 
facility by putting <facility>.none on the /var/log/messages line.

-Steve

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Auditd syslog plugin
  2018-06-04 22:11 ` Steve Grubb
@ 2018-06-04 23:32   ` John Jasen
  0 siblings, 0 replies; 3+ messages in thread
From: John Jasen @ 2018-06-04 23:32 UTC (permalink / raw)
  To: linux-audit

If you're on a system using rsyslog, you can also leverage imfile and
send it directly to a remote logserver.

rsyslog event queuing also handles interruptions in remote logging more
gracefully than audispd syslog.



On 06/04/2018 06:11 PM, Steve Grubb wrote:
> On Monday, June 4, 2018 9:02:04 AM EDT Boyce, Kevin P [US] (AS) wrote:
>> All,
>>
>> After enabling the syslog plugin for audispd and sending logs to a remote
>> server I am seeing every event being written to /var/log/messages locally
>> which is filling up /var.
>>
>> This is all redundant since local audit logs are kept in /var/log/audit. 
>> Is there a way to prevent auditd syslog plugin from writing to
>> /var/log/messages?
> That is pretty much what the plugin does. It writes all events to syslog 
> which based on rules in /etc/rsyslog.conf decides what to do with the text. 
> Typically it is to write everything to /var/log/messages.
>
> However, you can assign a specific facility to the audit events in the /etc/
> audisp/plugins.d/syslog.conf file and then in rsyslog.conf exclude the 
> facility by putting <facility>.none on the /var/log/messages line.
>
> -Steve
>
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2018-06-04 23:33 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-06-04 13:02 Auditd syslog plugin Boyce, Kevin P [US] (AS)
2018-06-04 22:11 ` Steve Grubb
2018-06-04 23:32   ` John Jasen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox