From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: [RFC] programmatic IDS routing Date: Wed, 19 Mar 2008 13:40:21 -0400 Message-ID: <200803191340.22092.sgrubb@redhat.com> References: <200803191302.48434.sgrubb@redhat.com> <47E14976.9050308@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <47E14976.9050308@hp.com> 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: Linda Knippers Cc: Linux Audit List-Id: linux-audit@redhat.com On Wednesday 19 March 2008 13:12:22 Linda Knippers wrote: > Rather than using the key for two purposes and introducing special key > words, couldn't an admin just tell the IDS which he's are of interest? > And what the priority of each one is? The problem is that you can tell the IDS that you want any reads of /opt/my-secrets, but unless you have a matching audit rule you will not get any records. This allows you to make sure you have a watch paired with its meaning. -Steve