From: "David Eaves" <deaves@plansys.com>
To: <selinux@tycho.nsa.gov>
Subject: Fw: [ISN] IBM earns Linux certification
Date: Thu, 7 Aug 2003 11:29:08 -0700 [thread overview]
Message-ID: <01d001c35d11$ca9deb00$6418a8c0@PSIMONT2> (raw)
As someone said yesterday, this has to do with assurance, not strength of
security as such (I'm paraphrasing).
Yes it's true the the door got a little wider for Linux. But first of all,
EAL2, and EAL3 are barely adequate for e-commerce in general, and not for a
level of threat posed to military systems in time of war, by a highly
capable adversary, with all the resources of a wealthy nation-state, and
willing to take extreme risks, as the CC conga-line dance goes. US military
C4I orgs will not be likely to find this useful, press agents
notwithstanding.
EAL4 is required even for relatively ordinary protection between information
enclaves. The CC system goes up to EAL7, which requires formal proofs of
linkage between security targets, protection profiles, and the design and
implementation of the products in question. The outlook even for SE-linux is
doubtful above EAL4, ever. And EAL2 is pretty much kids playing in a sandbox
by comparison, so IBM/Suse is no competitor with SE at this point.
More to the point though, CAPP, controlled access protection profile,
assures only what it says, controlled access. As long as it's never hooked
up to a network or has an IP stack running, assurances are reasonably strong
that nobody will be able to access it who is not supposed to. The Windows
product lines already have EAL4+ (what the plus means I don't know) versus
CAPP, which as a protection profile is next to worthless from my pov.
Solutions I need will have to address the MDSPP and MNISPP profiles, which
are much wider in scope and more difficult to assure.
Bottom line is that this is a lot of noise from IBM, cost a total of about
3/4 of a million, cheap marketing for them, half a mil for the cert lab, the
rest for schmoozing reporters, big noise and flashy lights. Good for Linux
vis a vis Windows, but it's pretty much irrelevent in real life, or to
people who work with SE-linux. And way overdue.
Dave Eaves
Principal Information Assurance Software Engineer
Planning Systems, Inc
----- Original Message -----
From: "Russell Coker" <russell@coker.com.au>
To: "SE Linux" <selinux@tycho.nsa.gov>
Sent: Thursday, August 07, 2003 8:54 AM
Subject: Fwd: [ISN] IBM earns Linux certification
>
>
> ---------- Forwarded Message ----------
>
> Subject: [ISN] IBM earns Linux certification
> Date: Thu, 7 Aug 2003 17:34
> From: InfoSec News <isn@c4i.org>
> To: isn@attrition.org
>
> Forwarded from: William Knowles <wk@c4i.org>
>
> http://www.fcw.com/fcw/articles/2003/0804/web-linx-08-06-03.asp
>
> By Rutrell Yasin
> Aug. 6, 2003
>
> The door just got a little bit wider for Linux to be used by
> government agencies for mission-critical systems now that IBM Corp.
> has earned security certification for the open-source operating
> system.
>
> IBM and SuSE Inc. Linux have achieved Common Criteria security
> certification for SuSE Linux Enterprise Server 8 running on IBM
> eServer xSeries. The Common Criteria are internationally recognized
> standards used by the federal government and other organizations to
> assess the security of technology products.
>
--
This message was distributed to subscribers of the selinux mailing 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.
next reply other threads:[~2003-08-07 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 18:29 David Eaves [this message]
2003-08-07 20:45 ` Fw: [ISN] IBM earns Linux certification Florian Weimer
2003-08-08 9:01 ` Tom
-- strict thread matches above, loose matches on Subject: below --
2003-08-07 21:19 David Eaves
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='01d001c35d11$ca9deb00$6418a8c0@PSIMONT2' \
--to=deaves@plansys.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.