All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Significant performance hit auditing system account actions?
Date: Thu, 14 May 2015 16:04:41 -0400	[thread overview]
Message-ID: <2777231.gv2IbXrrAx@x2> (raw)
In-Reply-To: <CACv9p5przx6owrT+4Do-eo_4tKpKf-rxLz4D7XO7LzjYm1eViw@mail.gmail.com>

On Thursday, May 14, 2015 03:24:16 PM leam hall wrote:
> Some security requirements include auditing events by users and root. So
> the line might include something like:
> 
>   -F auid=0 -F auid>=500 -F auid!=4294967295

The fields will be "anded". You cannot simultaneously have auid of 0 and >=500. 
So, you won't get any events.

> My question is, if you don't include that phrase will the audit system
> still get everything and not incur a serious performance hit. Effectively
> it will audit everything for users 1-499, the usual system accounts.

Typically the requirements read as audit root user actions - which is covered 
by TTY auditing. Everything else is covered by the other rules.

-Steve

      reply	other threads:[~2015-05-14 20:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 19:24 Significant performance hit auditing system account actions? leam hall
2015-05-14 20:04 ` 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=2777231.gv2IbXrrAx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.