From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Too many failed open syscalls Date: Wed, 9 Feb 2011 17:20:44 -0500 Message-ID: <201102091720.44267.sgrubb@redhat.com> References: <201102091317.59640.sgrubb@redhat.com> <23B4A3CF-E4F7-434C-8796-0472ADD146C4@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <23B4A3CF-E4F7-434C-8796-0472ADD146C4@mac.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Todd Heberlein Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Wednesday, February 09, 2011 05:05:52 pm Todd Heberlein wrote: > On Feb 9, 2011, at 10:17 AM, Steve Grubb wrote: > > They go on with a table which essentially means you need to audit almost > > everything. But you only need to worry about the failed access. > > Translation: You only need to worry about failed attack. Ignore the > successful attacks. There are certain system objects where you have to audit both success and failure, e.g. /etc/shadow. However, if a file's permissions are 0644, do you really need to audit that the file was accessed, e.g. /etc/localtime? -Steve