{"id":1539,"date":"2007-06-07T00:00:00","date_gmt":"2007-06-07T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/06\/07\/microsoft-sets-unified-security-strategy-with-stirling\/"},"modified":"2021-12-30T11:39:33","modified_gmt":"2021-12-30T11:39:33","slug":"microsoft-sets-unified-security-strategy-with-stirling","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/06\/07\/microsoft-sets-unified-security-strategy-with-stirling\/","title":{"rendered":"Microsoft Sets Unified Security Strategy with &#8216;Stirling&#8217;"},"content":{"rendered":"<p>Microsoft officials have outlined plans for a unified security product they say will allow users to centrally manage security across an entire IT infrastructure from a single console.  Code-named Stirling, the product is designed to enable IT managers to centrally set policy, configure, deploy and manage security within their IT environments.  When it is officially released&#8212;Microsoft officials have mentioned 2009 as a general release date, with the beta version to be available later in 2007&#8212;it will include the next-generation versions of the Forefront Client Security, Server Security, and Edge Security and Access solutions, plus a unified management console.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;What we consistently hear from customers is that they have a lot of pains &#8230; and a lot of problems that are not currently addressed by business security products that are out there on the market,&#8221; Brown said.<\/p>\n<p>http:\/\/www.eweek.com\/article2\/0,1895,2141902,00.asp?kc=EWWHNEMNL060707EOAD<\/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-1539","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\/1539","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=1539"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1539\/revisions"}],"predecessor-version":[{"id":4026,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1539\/revisions\/4026"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1539"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1539"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1539"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}