From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Recording user commands (from RE: Linux-audit Digest, Vol 31, Issue 12) Date: Fri, 27 Apr 2007 16:10:07 -0400 Message-ID: <200704271610.07849.sgrubb@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com Cc: Taylor_Tad@emc.com List-Id: linux-audit@redhat.com On Friday 27 April 2007 16:05, Taylor_Tad@emc.com wrote: > While a little more verbose than one might like, couldn't you audit > exec() system calls? Yes, you could certainly do that. But as you said, it would be more data than you would want. If you had a policy of no root logins, you could define a rule something like this: -a always,entry -S execve -F 'auid>=500' And that should cut it down to the commands run by real users and not daemons. >However, you might want to only audit successful exec()s. I don't think execve returns in the normal sense when successful. -Steve