{"id":1561,"date":"2008-06-21T00:00:00","date_gmt":"2008-06-21T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/06\/21\/desktop-virtualization-gets-military-grade-security\/"},"modified":"2021-12-30T11:39:36","modified_gmt":"2021-12-30T11:39:36","slug":"desktop-virtualization-gets-military-grade-security","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/06\/21\/desktop-virtualization-gets-military-grade-security\/","title":{"rendered":"Desktop Virtualization Gets Military-Grade Security"},"content":{"rendered":"<p>Tresys Technology has released a desktop virtualization platform with a difference &#8211; it is designed from the ground up for organizations needing tight security, including military bodies.  Tresys, which has a track record of providing military systems, said its VM Fortress can cut costs for organizations which would like to implement the consolidation programs offered by desktop virtualization, but haven&#8217;t taken the leap because of security concerns.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>VM Fortress includes features from Security Enhanced Linux (SE Linux), such as flexible mandatory access control (MAC) features, which the company said can limit damage caused by vulnerabilities in virtual machines (VMs).<\/p>\n<p>Users can manipulate some configuration features, such as sound card volume, mouse configuration and user password, with the rest controlled by the administrator, the company said.<\/p>\n<p>VM Fortress supports Red Hat Enterprise Linux version 5, 32-bit and 64-bit, on x86 hardware, along with VMware Workstation version 6 and VMware Player version 2.<\/p>\n<p>http:\/\/www.pcworld.com\/businesscenter\/article\/147343\/desktop_virtualization_gets_militarygrade_security.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-1561","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\/1561","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=1561"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1561\/revisions"}],"predecessor-version":[{"id":4048,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1561\/revisions\/4048"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1561"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1561"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1561"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}