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: looking for help in coming up to speed with auditd
Date: Wed, 9 Mar 2011 08:07:06 -0500	[thread overview]
Message-ID: <201103090807.06930.sgrubb@redhat.com> (raw)
In-Reply-To: <OF0B7F6D0C.409B8489-ON8825784E.003DCB0C-8625784E.003F7E03@usbank.com>

On Wednesday, March 09, 2011 06:33:30 am larry.erdahl@usbank.com wrote:
> I'm new to auditd, and have been assign to come up with a "best practice"
> standard for the deployment and audit settings for Linux servers using
> auditd,  Other then the man pages does anyone have any suggestions for
> "best practices", books or training courses that would help me get a
> better understanding of auditd and its syntax?

There is a audit.rules man page that discusses some ideas about how to conduct and 
investigation. Being able to do an investigation depends on the rules you give the 
audit system. If you don't have a watch on a document that you really care about, then 
you might get an event showing someone accessed it. 

The rules are essentially the same as auditctl without its name. So, you can look at 
its man page to get an idea of its syntax. I also would not start writing an 
audit.rules file from scratch. There are 3 or 4 sample rule files in the package. I 
would start with one of them and customize it to your needs. The stig.rules file is 
probably the best one to start with.

As for additional information I have a couple presentations here:
http://people.redhat.com/sgrubb/audit/
that might be useful. Also you can look at the NSA SNAC guide for RHEL5 which should 
have some discussion about the audit system.

-Steve

      reply	other threads:[~2011-03-09 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 11:33 looking for help in coming up to speed with auditd larry.erdahl
2011-03-09 13:07 ` 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=201103090807.06930.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