{"id":1495,"date":"2006-06-12T00:00:00","date_gmt":"2006-06-12T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/06\/12\/microsoft-makes-security-the-forefront\/"},"modified":"2021-12-30T11:39:29","modified_gmt":"2021-12-30T11:39:29","slug":"microsoft-makes-security-the-forefront","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/06\/12\/microsoft-makes-security-the-forefront\/","title":{"rendered":"Microsoft Makes Security The &#8216;ForeFront&#8217;"},"content":{"rendered":"<p>Microsoft officials introduced a new brand of security software, called ForeFront, at the company&#8217;s Tech Ed 2006 event.  Bob Muglia, senior vice president of the server and tools business at Microsoft, said ForeFront will include Forefront Client Security, and enhanced version of the company&#8217;s Microsoft Client Protection software for protecting desktops, laptops and server operating systems from viruses and other threats.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Muglia, who indicated the software is an attempt to modernize the product and make it more proactive for protecting computers, said an early beta version has been made available to some customers, with a public beta planned for the fourth quarter.<\/p>\n<p>ForeFront was the most notable unveiling to underscore the company&#8217;s new &#8220;People Ready Business&#8221; plan for empowering developers and IT professionals through new software.<\/p>\n<p>Muglia said Microsoft plans to prepare for this wave with the &#8216;People Ready Business&#8217; plan to helping developers manage complexity and achieve agility; protect information, control access; advance the business with IT solutions; and amplify the impact of people.  <\/p>\n<p>http:\/\/www.internetnews.com\/dev-news\/article.php\/3612626<\/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-1495","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\/1495","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=1495"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1495\/revisions"}],"predecessor-version":[{"id":3982,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1495\/revisions\/3982"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1495"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1495"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1495"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}