From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: Frank Mayer <mayerf@tresys.com>
Cc: NSA Selinux Mailinglist <selinux@tycho.nsa.gov>,
"'Juan Espino'" <jp_espino@hotmail.com>
Subject: RE: Bell & Lapadula Model
Date: Fri, 18 Feb 2005 00:25:26 +0100 [thread overview]
Message-ID: <1108682726.4100.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20050217222122.HGPG7908.mm-ismta4.bizmailsrvcs.net@FLM800>
[-- Attachment #1: Type: text/plain, Size: 2149 bytes --]
El jue, 17-02-2005 a las 17:21 -0500, Frank Mayer escribió:
> > > SELinux enforces a Mandatory Access Control (MAC) Policy based on Bell
> > > and Lapadula Model. I understand the read control property (no read
> > > up) and the write control (no write down), but in this model there are
> > > another property called tranquility property, I don't know very well
> > > how SELinux enforces this property,
> >
> > SELinux includes an experimental MLS implementation based on BLP. This
> feature is
> > not currently enabled in Fedora.
> >
> > Thus, it may be better to discuss the MLS component on the NSA list:
> > http://www.nsa.gov/selinux/info/list.cfm?MenuID=41.1.1.9
>
> To be clear, SELinux as most people think about it implements type
> enforcement as its MAC, and *not* BLP (i.e., MLS) as you seem to assert. As
> James notes the current MLS feature is experimental though there is work to
> make it more integral for future release.
Concretely, SELinux arguments the Type Enforcement model with the
addition of the standard Role-Based Access Control.
Instead of doing association between user and types, it lets RBAC to
associate users with at least one role and associates at least one type
with each of those roles.
Permission checks and such are handled by TE, RBAC is more an
user-complaining and policy-enhancing "layer".
"Bell-LaPadula MAC model describes access by active entities, called
subjects, to passive entities, called objects. An entity can, depending
on type of access, be in both roles.
From rom the distinction between read and write access four modes of access
can be distinguished: neither read nor write (execute, e), read only
(read, r), write only (append, a) and read-write (write, w). The set of
all access types is named A."
(http://rsbac.org/documentation/models.php#mac)
The access control matrix is slightly different then :)
Your description is accurate for RSBAC, not for SELinux as I explained
above, among Frank's comments.
Cheers,
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org>
[1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-17 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Xine.LNX.4.44.0502171518030.7638-100000@thoron.boston.redhat.com>
2005-02-17 22:21 ` Bell & Lapadula Model Frank Mayer
2005-02-17 23:25 ` Lorenzo Hernández García-Hierro [this message]
[not found] <BAY19-F67BE31277B62F3C14864B846F0@phx.gbl>
2005-02-20 19:11 ` Lorenzo Hernández García-Hierro
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=1108682726.4100.14.camel@localhost.localdomain \
--to=lorenzo@gnu.org \
--cc=jp_espino@hotmail.com \
--cc=mayerf@tresys.com \
--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.