From: Chris Wright <chrisw@osdl.org>
To: Zan Lynx <zlynx@acm.org>
Cc: Valdis.Kletnieks@vt.edu, breno@kalangolinux.org,
linux-kernel@vger.kernel.org
Subject: Re: security patch
Date: Thu, 22 Sep 2005 13:46:10 -0700 [thread overview]
Message-ID: <20050922204610.GK7991@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1127420688.10462.9.camel@localhost>
* Zan Lynx (zlynx@acm.org) wrote:
> An interesting thing that I don't think has been done before is to
> create a map linking stack call chains to syscalls. If the call stack
> doesn't match then it isn't a valid call.
There's been a fair amount of research in anomaly detection. It's not
as effective as you might hope. Can be slow, and since it's typically
based on statistics, needs to be properly trained (can be difficult) and
may be ineffective if you stay below anomaly threshold.
thanks,
-chris
next prev parent reply other threads:[~2005-09-22 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 19:44 breno
2005-09-22 20:03 ` Valdis.Kletnieks
2005-09-22 20:24 ` Zan Lynx
2005-09-22 20:32 ` Valdis.Kletnieks
2005-09-22 20:46 ` Chris Wright [this message]
2005-09-22 20:12 ` linux-os (Dick Johnson)
2005-09-22 20:47 ` Hagen Paul Pfeifer
2005-09-22 20:52 ` Chris Wright
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=20050922204610.GK7991@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=breno@kalangolinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zlynx@acm.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®