{"id":1454,"date":"2005-11-17T00:00:00","date_gmt":"2005-11-17T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/11\/17\/windows-with-anti-rootkit\/"},"modified":"2021-12-30T11:39:25","modified_gmt":"2021-12-30T11:39:25","slug":"windows-with-anti-rootkit","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/11\/17\/windows-with-anti-rootkit\/","title":{"rendered":"Windows with anti-rootkit"},"content":{"rendered":"<p>Microsoft Company is developing plans to secure 64-bit versions of Windows from dangerous malware such as rootkits.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>According to Bob Muglia, high ranked in Windows server group, Microsoft had put in place a &#8216;patch guard&#8217; on the Windows kernel, which would make it impossible to append code to the core of the OS while it was running.<\/p>\n<p>Such a design would stop software such as rootkits from hitching into kernel software processes as a means to make themselves appear legitimate.<\/p>\n<p>Microsoft&#8217;s 64-bit Longhorn Server is expected to ship in 2007, with the 64-bit only Release 2 two years later.<\/p>\n<p>http:\/\/www.xatrix.org\/article4189.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-1454","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\/1454","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=1454"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1454\/revisions"}],"predecessor-version":[{"id":3941,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1454\/revisions\/3941"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1454"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1454"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1454"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}