Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

SUSE Awarded EAL4 Certification

Posted by timothy on Sun Feb 20, 2005 01:19 PM
from the lockup dept.
An anonymous reader writes "Following in the wake of its previous certifications, Novell's SUSE Linux Enterprise Server 9 has achieved EAL4 certification on 'an IBM eServer.' This puts SLES9 in the same league as Windows 2000 for sales in the government sector and is the first Linux distro to achieve an EAL4 certification."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Anonymous Coward on Sunday February 20 2005, @01:23PM (#11729467)
    .......oh fuck!
    • by man_of_mr_e (217855) on Sunday February 20 2005, @02:47PM (#11729936)
      Hmm.. What I don't understand is how ANY version of linux achieved EAL3 or better. One of the criteria is that the OS have strict design documentation and that the implementation meets that design documentation. My understanding of the Linux development is that it's very informal and has no real design documentation (other than what a given hacker may create for themselves).

      I'm not saying that Linux doesn't deserve it, just that I don't understand how they were able to meet that criteria.
      • by mindstrm (20013) on Sunday February 20 2005, @03:08PM (#11730036)
        Linux didn't achieve it.. a specific distribution by SUSE did. The documentation and implmenetation designs are by suse.

        The certification doesn't require documenting all the code.... it's more about overall system design,the security model, user authentication, etc.
      • by AstroDrabb (534369) on Sunday February 20 2005, @05:07PM (#11730694)
        Are you just trolling?

        MS Windows 2000 has this cert. Exactly where is _all_ this MS documentation available to the public? Oh, that is right, it is not. So exactly why would "Linux" need to have this public documentation? "Linux" wasn't certified. A specific implementation of Linux, SuSE Linux Enterprise Server 9, was awarded this certification level. Novell put in the effort needed to achieve this certification, including proper documentation.

        The Linux kernel is Open Source, as well as most/all of the GNU code base forming the complete OS. I can go out and build my own Linux distro (which I have done for personal use based on LFS). However, that doesn't mean that _my_ version of GNU/Linux is EAL4 certified. If you read the articles or even the simple summary, you should have clearly understood that currently, the only version of Linux to be EAL4 certified is, SuSE Linux Enterprise Server 9.

      • The requirement is actually that you document what your security model is and how your implementation achieves it, and then they verify that you're right.

        There are no restrictions on the development process. The point is that it gets validated as a finished item, so it doesn't matter how it got that way. It also doesn't matter who writes the documents, so long as they have the necessary information.

        It will be interesting to see when SuSE does with the documents which were part of the process. It would als
  • by OffTheLip (636691) on Sunday February 20 2005, @01:24PM (#11729470)
    It's really a matter of money and time.
    • by hal9000(jr) (316943) on Sunday February 20 2005, @01:28PM (#11729502)
      Kinda. Provided there is a well designed and realistic Protection Profile and the Security Target is realisticaly designed, there is some value to the CC certification.

      The biggest issue I have seen with CC is more in the understanding, or lack there of, of what is covered in a CC eval on both consumers and vendors. Vendors obviously promte the CC eval because it is expensive and has a certain cache. Users tend to glaze over reading the certification docs and most often don't make it very far before checking whatever check box they need.

    • by Alien54 (180860) on Sunday February 20 2005, @02:04PM (#11729696) Journal
      A certification some time ago that Windows was completely secure on a network, so long as you didn't actually connect it or plug it in to the network?

      I think the MS has improved on that with 2k, etc. , but I'm not sure.

      • by Anonymous Coward on Sunday February 20 2005, @02:12PM (#11729742)
        Yeah, its meanless except for a small class of government applications. Unfortunately, Microsoft drank their own koolaid and started marketing the certification as a general security feature.

        "Windows NT's Security Certification means that firewalls are optional" -- actual bullshit advice from a microsoft document in the mid-90s.
      • There was some rumors a few years ago about Windows NT getting a C2 "certification" only when you did things like disconecting the floppy drive.

        I actually think most of this was the old "poking fun at Microsoft", tho. I mean, if that was the case, I doubt it would get certified.

        On the other hand, I never had much respect for those rainbow certifications.
        • That is true (Score:3, Informative)

          Amongst the things required to make Windows NT 3.5 C2 compliant were disconnecting the removable media, removing the network connection and disabling the OS/2, POSIX and DOS subsystems. Amongst other things.

          After you were done doing this, of course, NT 3.5 was only useful as a kiosk. Most applications that would benefit from C2 certification in the past were 'stovepipes' that don't interact with other applications, so this was okay.

          This isn't poking fun at MS [microsoft.com]. This is how it got certified. Then, they
            • Still sounds like a heck of a good joke.
              No removable midia = no backup

              It depends on what you describe as a joke.

              It allows the marketing 'droids to say things like 'We took a C2 certified system, added a ZIP drive and 3COM ethernet card, and voila one of the most usable, secure systems you could hope for.' (then hold their breath and hope that the carefully balanced shoe doesn't drop).

              It's not fraud if you honestly (if misleadingly) document what you're doing.

      • That was Windows NT, and the setup also mandated that there be no removable media. However, that was for a secure non-networked workstation, which have their uses in some cases.
    • by soren42 (700305) * <j@[ ]-kay.com ['son' in gap]> on Sunday February 20 2005, @02:43PM (#11729919) Homepage Journal

      It's really a matter of money and time.

      That's exactly what it is... which is yet another facet of the differences between Novell and Red Hat. Novell has the money to apply their resources across a much broader spectrum than Red Hat - just by virtue of having more money. Also, they have much more staff on the payroll - and by extension, more time (read: manhours).

      Initially, there were a lot of concerns when Novell acquired SuSE around their committment to Free Software. But they have repeatedly (YaST, SuSE Linux Open Exchange, FreeSWAN, Hula, etc.) shown that they are committed to the philosophy of Free Software - not just buying the technology to close it up, and make money from selling something proprietary. So, those concerns have been put to bed, it makes Novell/SuSE a very attractive Linux option. They have the resources, relationships, and talent to work quickly and effectively - developing solid, certified, and feature-rich open software.

      Please don't mistake this comment as Red Hat bashing. I am simply pointing out that Novell has the resources to really make a difference in the US Linux market - and things like achieving EAL4 (so quickly) prove that.
    • by omnirealm (244599) on Sunday February 20 2005, @03:56PM (#11730316) Homepage

      Disclaimer: I work for the IBM Linux Technology Center; any comments I make are entirely my own.

      It's really a matter of money and time.

      And blood, sweat, and tears. You're talking to a guy who spent countless hours drafting hundreds of pages of low-level design documentation on the Linux kernel and set of trusted userspace applications in order to help satisfy the CAPP/EAL4 requirements. True, IBM paid me to do it, but the effort is far from trivial, and Linux's reputation gets a nice bolster when things like security certification happen.

      Back when my team achieved CAPP/EAL3 certification, the general attitude on Slashdot was, ``Great, but wake me up when we get EAL4.'' Well, now we've got EAL4. We have a secure protection profile ironed out, documented, and deployed, which helps immensely with setting up a locked down Linux box. We have engineers who have been given the job to review thousands of lines of source code and to write and run a battery of tests to verify that Linux kernels and applications really do, from a security standpoint, just what they claim to do, and they do it right. But I think, more than anything, that this is a strong indication of Linux's maturity. For the public sector, this satisfies a core requirement of many contracts. For the private sector, this is one more thing to impress the boss when advocating Linux solutions.

    • by eer (526805) on Sunday February 20 2005, @04:39PM (#11730544)
      Other posts are correct - IBM made this happen through manpower and expenses, to create the documentation needed for so many open source projects (lacking design documentation, for the most part), and for underwriting the evaluation labs effort.

      But Novell/SuSE also deserves credit for running a top-notch configuration management system (Autobuild), having controls and procedures for keeping track of where which patches that get incorporated come from, and for having a patch notification and publication process that enables customers to get timely notification of necessary patches.

      The business processes surrounding manufacturing the distribution and supporting customers on a global basis are valuable Novell/SuSE contributions.

      Disclaimer: I work for Novell and work with the folks at SuSE on a daily basis.

  • Certs/ (Score:4, Insightful)

    by cyberfunk2 (656339) on Sunday February 20 2005, @01:33PM (#11729545)
    While some of these certifications seem silly and almost obvious (as in "well of COURSE it can do that").

    We should remember, for non-technical people (i.e.: most of the government) this is all they have to judge tehcnical suitability for the job. And like the beauracrats they are, they adhere pretty strictly to these things.

    So yes, it is a big deal that a major distro's broken through some of the red tape.
  • Maybe I missed it in the article, but I am curious if it was on a pSeries or xSeries. SLES9 on a pSeries box is a damn good combination. On the xSeries, it's o.k. but you do not have the peace of mind you get with the pSeries hardware.

    I feel a little more confident in our military using that than MS windows on cheap beige boxes.
    • I am curious if it was on a pSeries or xSeries

      When the config earned EAL2+, it was on xSeries, but according to this [ibm.com], they earned EAL3+ on *all* platforms. I did a little digging but couldn't find if the same applies to this certification. I know it doesn't answer your question, but it may keep your hopes up to dig some more. As an IBM consultant doing Linux on x, p, and z.. I say "cool!"
  • It certifies SLES 9 as being in the same league as Windows 2000.
  • by CoolSilver (794518) * on Sunday February 20 2005, @01:38PM (#11729579)
    Wow, I guess Mr. Gates and company must be biting their nails. 2000 has that certification yet XP, the best product with "advanced security technologies" has nothing.

    Well I guess it means times have changed. Linux is a big player in the game now and Microsoft needs to realize this and stop denying. False statements hurt worse than the bitter truth of "your product isn't good enough". I rather trust a company and have something that works okay and secure than some company that hides facts and has a better product in some ways, just not security.

    It is funny how someone came out with a report saying windows is more secure, but is that based off the experimental code or source and which distribution. Novell and SuSE have always taken security as a priority and it shows.
    • by TheCabal (215908) on Sunday February 20 2005, @01:56PM (#11729662) Journal
      CC evaluation is not an automatic thing. The sponsoring company (in that case Microsoft) pays for the evaluation. A target is generated, which details hardware and software configurations. This can take months. Then the actual platform itself is evaluated, which can also take months, especially if deficiencies are found and corrected. Win2k was released in 2000, but didn't get CC evaluation until 2004. There's a hint.
    • Re: XP's non-cert status...

      People tend to like things that are tried and true and are known to run solid.. Or with small incremental changes, done carefully.

      The problem with XP is two-fold.. first.. it (the "jump" to XP) was just that, a jump, that wasnt all that carefully considered beforehand (MS just figured that most people would go with it, because after all, it IS the latest and greatest).

      Second, MS marketing actually shot them in the foot here. They marketed this as the "hot new thing", "new and
      • by ScrewMaster (602015) on Sunday February 20 2005, @03:04PM (#11730017)
        That, my friend, is probably the most succinct description of what is wrong with the world of personal computing that I've heard yet.

        The only thing I would add is that this applies all across the board. Home users and corporate office users are in the same boat: they often have no interesting in "upgrading" to get more whiz-bang because they don't need it and don't want the headaches. That's the essentially conservative attitude that the bulk of users have, because any significant change means they may have to spend time and money they don't have to learn something new, deal with problems that weren't there before, and may find their shiny new OS and apps interfering with getting their jobs done. Microsoft's feature-oriented marketing and forced upgrade cycles have probably caused more lost man-hours than the common cold.
    • Well, the EAL4 certification is only just a bunch of paperwork. It certifies that the company who got it, did a lot of paperwork describing what the product does to be secure and _no_ check, in whatever kind, is made by the goverment to certify that the claims are indeed true. Also, the claims that need to be made are really trivial and almost all s/w vendors can claim conformity. There is no point comparing security of win2k and linux based on that cert...
      • "There is no point comparing security of win2k and linux based on that cert... "

        Here's the obvious point: If you are trying to SELL it it matters. Discussing it on slashdot and what it really means or does is one thing, getting some org or agency or corporation to drop x-millions of dollars in your lap for your product is another. One of the main complaints about Linux that you read over and over is "how do you make money with open source software"? Well, here's one way to make that a reality. Jump through
        • "Then why is it that it took so long to certify Linux? Why did it take 4 years to certify Windows 2000? Why is'nt XP certified?"

          It's really a _lot_ of paperwork and I'm sure that MS got that cert everywhere it really matters. As for linux, seeing distros get that cert means that they have certain hopes to see linux in some places that require EAL4. Nothing more.

          "I'm sure Gates would have like to have been able to say , "Hey, XP's EAL4 certified by the US government" when asked about MS's

  • I put all my efforts and support in Suse about 2 years ago and all my eggs in the Linux basket (in general) about 4 years ago.

    I saw Redhat blink so I took the Suse path.
    No regrets...
    • I put all my efforts and support in Suse about 2 years ago and all my eggs in the Linux basket (in general) about 4 years ago.

      I did the same thing. There's been a few warts (configuring Samba, some graphics issues which weren't well documented) but it's generally been good. SuSE is pretty easy to work with, reasonably polished. They could do a better job keeping up with some of the big name open source software like Mozilla through the official update channels (they're usually a few versions behind) bu

      • I had problems with an Adaptec SCSI controller in a Dell system recently.

        The trouble is that Adaptec seems to think that doing RAID-1 in the device driver is somehow a good idea and worthy to be very secretive about. So they provide binary-only drivers for their card and it is 3 kernel versions behind.
        Of course we need no Adaptec software RAID-1 as Linux has it in the kernel. After some searching and asking I found a patch that allowed the Adaptec controller to operate as a plain SCSI controller and from
  • Netware is entrenched in goverment organisations. therefore Suse/Novell open server needs to be rubber stamped ASAP.
    • No piece of software running on a Federal interest network should be rubber stamped. It should be evalulated on its own merits by a formal DITSCAP process.

      For FWIW, all the Federal networks I've worked on, I've seend damn few Novell servers. A lot of them used to run Novell, then migrated to Windows. I don't recall NetWare being on the EPL for the command I work for, so it might have already gone the way of the dodo.
  • Don't they run US battleships on Windows NT? Is that the "C2" certification? Is there a Linux distro with that cert?
    • Re:Unsinkable (Score:5, Informative)

      by TheCabal (215908) on Sunday February 20 2005, @02:35PM (#11729881) Journal
      There aren't any battleships currently in commission in the US Navy, all have been either scrapped or mothballed. You're probably thinking of the prototype cruiser that made all the headlines. It was running NT, bluescreened and the ship was stuck. Not that the bluescreen was not an OS error, but an error due to a divide by zero from the application, and it wasn't written well enough to handle that error nicely, so the OS did what it was supposed to. The ship was rushed anyway, and supposed to have Unix backends for all the C^2 functions. NT is just for the user workstations.

      The US retired the Rainbow Series a while ago, but EAL4 is about a close approximation to C2.
      • Can you explain to me why the OS would bluescreen due to a divide by zero from the APPLICATION? Maybe I'm naive, but an application should not be able to crash the kernel.

      • Re:Unsinkable (Score:3, Insightful)

        so the OS did what it was supposed to.

        Can I get some of what you're smoking? Since when is an OS supposed to crash hard just because a single application couldn't handle a divide-by-zero?

  • by Quiberon (633716) on Sunday February 20 2005, @02:31PM (#11729859) Journal
    I've got one of these here SuSE 9.2 Live KDE for Windows [btconnect.com]. Torrent here [btconnect.com]. Lots of Linux-for-Windows torrents there, in fact.

    Have fun !

  • Linux going for EAL5 (Score:4, Interesting)

    by Anonymous Coward on Sunday February 20 2005, @03:27PM (#11730165)
    The French Ministry of Defense will put up 7 million over the next three years to fund an industrial consortium building a Linux-based operating system that can achieve EAL5 certification. The coalition includes Bertin Technologies, SURLOG, Jaluna, Mandrakesoft, and OPPIDA.

    BTW. There are Server and Embedded Linux version that has achieved Telecom Carrier Grade certification for reliablity. Microsoft won't try to get Telecom Carrier Grade certification for Windows because it is too unreliable.
    • Re:Is there hope? (Score:5, Informative)

      by TheCabal (215908) on Sunday February 20 2005, @01:53PM (#11729644) Journal
      Not likely to happen soon. Just because it's been EAL4 certified doesn't mean that is allowed to be operated on a Federal network. In the case of DoD network, it still needs a CTO (Certificate To Operate) before being allowed to be connected to the network. A CTO requires a whole DITSCAP session, formal documentation, evaluation and recommendation. For an operating system, it could literally be years before a CTO is produced. An interim CTO could be generated, but I don't think any major commands are willing to risk issuing one for such an unknown as this.
      • However, there's nothing saying that contract providers to the government can't run Linux (and have), such as, say, the Federal Reserve.
        • Re:Is there hope? (Score:4, Informative)

          by TheCabal (215908) on Sunday February 20 2005, @02:13PM (#11729753) Journal
          The EPL (Enterprise Product List) only lists software that is allowed to run on a Federal network. As long as the system isn't connected to a Federal network and meets the requirements of the contract in terms of reliability, security and auditability, there is nothing to say that a contractor couldn't use SuSE or even RHES (was evaluated EAL3) unless it was expressly forbidden in the contract.
    • by $ASANY (705279) on Sunday February 20 2005, @02:11PM (#11729731) Homepage
      This really only makes a difference in the federal sector here in the U.S., as commercial firms might be interested in CC, they understand that CC really doesn't mean a whole lot. For the federal sector, this is only one half of the whole ball of wax.

      Just about every DoD or other federal government RFP these days requires that every part of the solution be CC EAL 3 or greater because of DoDD 8200.1 and other mandates. Without CC, you can't be considered, no matter how much better your solution is than the relatively limited menu of certified options.

      The other half is FIPS 140-2, which covers data encryption. If you don't have FIPS 140-2 you can't play ball, and even then in some places like the U.S. Navy, there's another layer of certifications for NMCI and such. So however we might celebrate SLES EAL4 cert, it STILL doesn't get them in the game without adding on a (typically) expensive FIPS 140-2 certified SSL component. My understanding is that RedHat understood this and bundled a certified solution with RHEL.

      So will this announcement cause more enterprises to use SLES? Nope. They don't really care. Companies? Same boat. Governments? Only in those cases where SLES will exist entirely within a secure intranet or will piggyback on a generally closed-source 3rd party FIPS certified encryption system. SLES hasn't scored yet.

      The other barrier is that for most potential government installs, there has to be CC certified software to run on it, unless it's just a network appliance. MySQL, Apache and all the rest would have to be CC certified to actually get a pure open source solution in the door.

      The net effect is that this plays directly into the hands of the big software/hardware vendors and creates a barrier to entry for smaller players who would like to play in the federal space. Sure, SLES is certified, but with what? Oracle and IBM? Who's going to pay to get Apache2 certified for both Common Criteria and FIPS 140-2?? Or MySQL? Or PHP4? Look for more domination in the federal software market by the likes of Microsoft and Oracle, who will have even less incentive to create really good software because this somewhat meaningless certification process reduces competition and increases profitability for those who can invest in certifications.

      Look at NMCI if you are doubtful. It hasn't helped the Navy improve it's IT infrastructure one bit, and made EDS nearly the sole vendor for all IT for the Navy. It's the gatekeeper of the NTISSP certification process, and everything it decides to approve has to be purchased through and managed by EDS. Certifications like this are simple money grabs by major Systems Integrators and muscular software companies.

      Nothing to see here. Keep moving.
      • Throw out a few more permutations of the alphabet please. I enjoy reading cryptic bullshit.
      • I was working for the US Navy when they started rolling that out. Yeesh! Talk about a catastrophe! It took a year and a half to get stable e-mail. Yes, a YEAR AND A HALF! Eighteen months to do what most Linux geeks can get done in a couple of hours or less.

        Security? That thing has more holes than swiss cheese! All applications are run on a single box, with clients connecting via Citrix. That box is typically Windows. Windows doesn't have Orange Book B-grade compartmentalization. This means that if you wer