From: Steve Grubb <sgrubb@redhat.com>
To: Linda Knippers <linda.knippers@hp.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: [RFC] programmatic IDS routing
Date: Wed, 19 Mar 2008 13:40:21 -0400 [thread overview]
Message-ID: <200803191340.22092.sgrubb@redhat.com> (raw)
In-Reply-To: <47E14976.9050308@hp.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
next prev parent reply other threads:[~2008-03-19 17:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 17:02 [RFC] programmatic IDS routing Steve Grubb
2008-03-19 17:12 ` Linda Knippers
2008-03-19 17:40 ` Steve Grubb [this message]
2008-03-19 17:55 ` Steve Grubb
2008-03-19 18:18 ` Valdis.Kletnieks
2008-03-19 18:54 ` Steve Grubb
2008-03-19 20:09 ` Valdis.Kletnieks
2008-03-19 18:05 ` Valdis.Kletnieks
2008-03-19 18:40 ` Steve Grubb
2008-03-19 19:04 ` Linda Knippers
2008-03-19 19:28 ` Steve Grubb
2008-03-19 19:48 ` Eric Paris
2008-03-19 20:48 ` Steve Grubb
2008-03-19 19:55 ` Linda Knippers
2008-03-19 21:01 ` Steve Grubb
2008-03-19 21:31 ` Linda Knippers
2008-03-19 21:41 ` Eric Paris
2008-03-19 22:42 ` Steve Grubb
2008-03-19 23:00 ` Linda Knippers
2008-03-19 23:44 ` Steve Grubb
2008-03-20 13:32 ` Linda Knippers
2008-03-20 13:53 ` Steve Grubb
2008-03-21 10:28 ` Klaus Heinrich Kiwi
2008-03-21 12:50 ` Steve Grubb
2008-03-21 14:14 ` LC Bruzenak
2008-03-21 15:01 ` Steve Grubb
2008-03-21 16:32 ` LC Bruzenak
2008-03-24 13:13 ` Klaus Heinrich Kiwi
2008-03-20 12:19 ` 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=200803191340.22092.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linda.knippers@hp.com \
--cc=linux-audit@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.