{"id":1574,"date":"2008-11-18T00:00:00","date_gmt":"2008-11-18T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/11\/18\/secure-os-gets-highest-nsa-rating-goes-commercial\/"},"modified":"2021-12-30T11:39:38","modified_gmt":"2021-12-30T11:39:38","slug":"secure-os-gets-highest-nsa-rating-goes-commercial","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/11\/18\/secure-os-gets-highest-nsa-rating-goes-commercial\/","title":{"rendered":"Secure OS Gets Highest NSA Rating, Goes Commercial"},"content":{"rendered":"<p>Unlike existing commercial OSes, Integrity OS is designed and certified to defend against sophisticated attacks.  After receiving the highest security rating by a National Security Agency (NSA)-run certification program, Green Hills Software has announced that its Integrity-178B operating system was certified as EAL6+ and that the company had spun off a subsidiary to market the OS to the private sector as well as government agencies.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This means that the OS was designed and certified to defend against well-funded and sophisticated attackers,&#8221; says David Chandler, CEO of Integrity Global Security, the new Green Hills subsidiary.<\/p>\n<p>Integrity-178 B meets the rigorous Common Criteria Separation Kernel Protection Profile (SKPP) standard, which guarantees that malicious code can&#8217;t corrupt or harm any other application running on the system.<\/p>\n<p>&#8220;I&#8217;m delighted that they have accomplished this,&#8221; said Stephen Hanna, co-chair of the Trusted Computing group and distinguished engineer with Juniper Networks, during his keynote at the CSI 2008 conference in National Harbor, Md., Tuesday.<\/p>\n<p>http:\/\/www.darkreading.com\/security\/app-security\/showArticle.jhtml?articleID=212100421<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1574","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1574","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1574"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1574\/revisions"}],"predecessor-version":[{"id":4061,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1574\/revisions\/4061"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1574"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1574"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}