All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Smith <jsmith@mcs.drexel.edu>
To: selinux@tycho.nsa.gov
Subject: Re: [patch] Re: auditdeny is painful
Date: 05 Jun 2002 07:00:49 -0400	[thread overview]
Message-ID: <1023274849.2139.17.camel@jsmith.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0206041520480.3949-200000@raven>

I'll jump into the thread and add my $.02:

The permission denied messages can be an excellent intrusion detection
system (like tripwire). If one eliminates denials that are innocent
(programs accessing files they don't need to), the remaining ones can
give a pretty good picture of what is going on in one's system. And this
approach is much more refined than tripwire: it doesn't scan huge chunks
of file systems to see what changes. Instead, it intercepts  system
calls that attempt to make the changes.

On several occasions, I've noticed illicit attempts to access my student
records database. Although (I think) these attempts would have failed
without SELinux (because of standard unix permissions), I also wouldn't
have gotten such clear indications of it.
-- 


--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2002-06-05 11:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03 22:30 auditdeny is painful Russell Coker
2002-06-04  0:50 ` Mini-cd's Ed Street
2002-06-04  7:26   ` Mini-cd's Russell Coker
2002-06-04 13:28 ` auditdeny is painful Stephen Smalley
2002-06-04 14:18   ` Russell Coker
2002-06-04 19:24   ` [patch] " Stephen Smalley
2002-06-05 11:00     ` Justin Smith [this message]
2002-06-05 11:19     ` Russell Coker
2002-06-06 14:14       ` Stephen Smalley

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=1023274849.2139.17.camel@jsmith.org \
    --to=jsmith@mcs.drexel.edu \
    --cc=selinux@tycho.nsa.gov \
    /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.