public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: auditd questions
Date: Thu, 8 Sep 2011 09:14:47 -0400	[thread overview]
Message-ID: <201109080914.47615.sgrubb@redhat.com> (raw)
In-Reply-To: <CAN-7Vp=+BEGWeSw1MSHsb5ByRpTNRAv-0UGM9Er2zvJkc+7x_w@mail.gmail.com>

On Thursday, September 08, 2011 02:38:03 AM Vipin Rathor wrote:
> My auditd server is getting overwhelm by the logs that it is getting.

This is almost always means the rules are not properly tuned.

> I've configured a remote audit logging via audisp-plugin. Earlier I
> tried to reduce the amount of logs by optimizing the audit rules. But
> we want to reduce it further.
> Here's the list of things that I can think to reduce the overwhelming
> of logs further:
> 1. Increase kernel buffer for auditd from 20480 (current) to 99999.
> 2. Increase the priority of auditd process. Currently 'priority_boost
> = 10'. Default is 4. I don't know the maximum value (though I've seen
> someone using 12). Can anyone tell me what's the maximum priority I
> can give?

Probably 19. This is dictated by the kernel. See the nice(1) command.


> 3. Optimize the audit messages further:
>   a. Exclude single file (like /etc/sysconfig/bash-prompt-xterm ) from
> being audited. This can be done with following rule (Thanks to
> Steve!):
> -a exit,never -F path=/etc/sysconfig/bash-prompt-xterm
>   b. Exclude specific processes by their PIDs. This will be tricky as
> we will need to keep track of PIDs incase of process
> start/stop/restart etc.

Yes, but you may be able to use the SE Linux label to prevent auditing of the process.

-Steve

  reply	other threads:[~2011-09-08 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08  6:38 auditd questions Vipin Rathor
2011-09-08 13:14 ` Steve Grubb [this message]
2011-09-09  4:55   ` Vipin Rathor

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=201109080914.47615.sgrubb@redhat.com \
    --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