public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Linda Knippers <linda.knippers@hp.com>
To: Michael W Folsom <mwfolso@sandia.gov>
Cc: Linux Audit List <linux-audit@redhat.com>
Subject: Re: Current capabilities
Date: Wed, 13 Dec 2006 18:39:40 -0500	[thread overview]
Message-ID: <45808F3C.3020503@hp.com> (raw)
In-Reply-To: <1166051787.6399.23.camel@cisco.sandia.gov>

Michael W Folsom wrote:
> I've been lurking on this list for a while now and am a bit confused at
> the current state of audit's capabilities.  I've looked at: 
> 	http://people.redhat.com/sgrubb/audit/
> and still aren't sure if it is capable of doing what I need.  To get to
> the point the events I need to record in an audit log are -

If you're interested in RHEL4 then I suggest you look at the updates.
HP and IBM have both completed CAPP evaluations of RHEL4 and
when properly configured the system and audit framework supports what you want.

For details, check out HP's documentation at:
http://h71028.www7.hp.com/enterprise/downloads/RHEL-CAPP-EAL3-HP-Configuration-Guide.pdf
or IBM's at:
ftp://www6.software.ibm.com/software/developer/library/os-ltc-security/RHEL-CAPP-EAL4-IBM-Configuration-Guide-v1.14.pdf

> 1) If someone tries to access an object (file, directory, program) that
> they don't have rights to the event needs to be recorded

You can configure the audit system to audit specific system calls that fail.
> 
> 2) if someone logs into a system and su's to another user or series of
> users their actions need to be traceable to the original login user's
> id 

The audit system keeps track of the login uid as well as the current uid,
so I believe it does what you want.
> 
> Can this be done with the current audit system in RHEL4 or will this not
> be supported until RHEL5 is released?  Are there any other Linux
> distro's that can do this?  

SLES8 as of SP3 can do the same thing, only with a different audit
framework.

> If either of these are true where would I
> look for information how to get this to work.

-- ljk
> 
> 
> Thanks!
> 
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2006-12-13 23:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13 23:16 Current capabilities Michael W Folsom
2006-12-13 23:39 ` Linda Knippers [this message]
2006-12-14 12:43   ` Boyce, Kevin P. (Melbourne, FL)
2006-12-14 13:33     ` Steve Grubb
2006-12-13 23:41 ` Steve Grubb

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=45808F3C.3020503@hp.com \
    --to=linda.knippers@hp.com \
    --cc=linux-audit@redhat.com \
    --cc=mwfolso@sandia.gov \
    /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