From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Grubb <sgrubb@redhat.com>
Subject: Re: Current capabilities
Date: Wed, 13 Dec 2006 18:41:16 -0500
Message-ID: <200612131841.16385.sgrubb@redhat.com>
References: <1166051787.6399.23.camel@cisco.sandia.gov>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Return-path: <linux-audit-bounces@redhat.com>
In-Reply-To: <1166051787.6399.23.camel@cisco.sandia.gov>
Content-Disposition: inline
List-Unsubscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: linux-audit@redhat.com
List-Id: linux-audit@redhat.com

On Wednesday 13 December 2006 18:16, Michael W Folsom wrote:
> 1) If someone tries to access an object (file, directory, program) that
> they don't have rights to the event needs to be recorded

-a always,exit -S open,opendir,execve -F exit=-13

This does it for 3 common syscalls. You can do it for any syscall you want. 
You can use strace to figure out the syscalls you want.

> 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

It does this. There is a process attribute, loginuid, that keeps track of 
this. The audit events have it as the auid field. We've already preconfigured 
RHEL4/5 and FC4->rawhide to handle this.

-Steve