{"id":1512,"date":"2006-10-04T00:00:00","date_gmt":"2006-10-04T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/10\/04\/symantec-intel-team-on-new-security-method\/"},"modified":"2021-12-30T11:39:31","modified_gmt":"2021-12-30T11:39:31","slug":"symantec-intel-team-on-new-security-method","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/10\/04\/symantec-intel-team-on-new-security-method\/","title":{"rendered":"Symantec, Intel Team On New Security Method"},"content":{"rendered":"<p>Amid growing concern for misconfigured security and smarter malware (define), Symantec and Intel are teaming up to provide a security layer that runs between the hardware and operating system.  In a survey of IT managers, published today, the two firms found the biggest concerns for IT managers were security systems that were disabled by really smart malware, disabled by employees or not installed properly.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;We want to get away from the Windows operating system, which has quite a few vulnerabilities within the OS itself, plus any vulnerabilities in apps installed next to us on the OS,&#8221; Gary Sabala, product manager for the Symantec virtual security appliance, told internetnews.com.  &#8220;What we&#8217;re trying to do is create this isolated silo of an execution environment that we think is much more tamper resistant to threats on the main Windows OS, but is also an isolated environment where the IT manager can have a high degree of control,&#8221; .<\/p>\n<p>http:\/\/www.internetnews.com\/security\/article.php\/3635806<\/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-1512","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\/1512","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=1512"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1512\/revisions"}],"predecessor-version":[{"id":3999,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1512\/revisions\/3999"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1512"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1512"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1512"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}