Sun Microsystems said its Solaris 10 operating system will be ready for general release by year’s end, complete with a sharper set of security teeth.<\/p>\n","protected":false},"excerpt":{"rendered":"
Paul Sangster, senior Solaris security architect for the Santa Clara, Calif.-based company, touted Solaris 10’s security improvements during a roundtable discussion at Sun’s Burlington, Mass., offices Monday, saying, “Security touches everything we do, and in designing Solaris 10 we made the assumption that the Web server is sloppy” and in need of extra layers of protection. I expect IT administrators will greatly appreciate the N1 grid container zone feature and the user rights management privilege feature,” Sangster said. “These features enable (them) to much more tightly protect their services, even in the face of an attacker exploiting a known hole in some third-party software that was deployed but not yet patched.<\/p>\n
He said the N1 grid container technology will allow users to create up to 4,000 secure, fault-isolated software partitions, each with its own IP address, memory space, file area, host name and root password.<\/p>\n
Solaris 10 has been in development for two and a half years, and has slowly been made available to customers in recent months.<\/p>\n
He added that Linux applications can run unmodified on Solaris.<\/p>\n
Weinberg added that the capabilities in Trusted Solaris have been folded into Solaris 10. “Trusted Solaris has been used in government but has been separate from the standard Solaris,” he said. “We started this integration with Solaris 8, and Solaris 10 completes the move.”<\/p>\n
James Dobson, system architect for Dartmouth College in Hanover, N.H., talked about the success the institution’s psychology department has had in using a version of Solaris 10. Pointing to the operating system’s improved interoperability, Dobson said, “We use multiple applications and platforms and Solaris 10 is working smoothly with all of these.<\/p>\n
http:\/\/searchsecurity.techtarget.com\/originalContent\/0,289142,sid14_gci1005868,00.html<\/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-1328","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\/1328","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=1328"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1328\/revisions"}],"predecessor-version":[{"id":3815,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1328\/revisions\/3815"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1328"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1328"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1328"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}