{"id":1487,"date":"2006-05-31T00:00:00","date_gmt":"2006-05-31T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/05\/31\/microsoft-officially-launches-paid-security-product\/"},"modified":"2021-12-30T11:39:28","modified_gmt":"2021-12-30T11:39:28","slug":"microsoft-officially-launches-paid-security-product","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/05\/31\/microsoft-officially-launches-paid-security-product\/","title":{"rendered":"Microsoft officially launches paid security product"},"content":{"rendered":"<p>Microsoft will announce that it is releasing software that aims to better protect people who use its Windows operating system from Internet attacks.  Windows Live OneCare, which will protect up to three computers for $49.95 per year, marks the latest step in Microsoft&#8217;s effort over the years to make its operating system less vulnerable to crippling Internet attacks.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Redmond-based Microsoft has previously said that its main focus for OneCare was the 70% of computer users who, according to Microsoft estimates, have no additional protection at all.  But in an interview last week, Ryan Hamlin, general manager for the OneCare product, said the company also hopes to snag existing Symantec and McAfee customers.<\/p>\n<p>&#8220;We&#8217;d love for those customers to use our product, and encourage them to, but there&#8217;s also 70% that don&#8217;t use anybody,&#8221; he said.<\/p>\n<p>http:\/\/www.usatoday.com\/tech\/news\/computersecurity\/2006-05-31-microsoft-security_x.htm<\/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-1487","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\/1487","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=1487"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1487\/revisions"}],"predecessor-version":[{"id":3974,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1487\/revisions\/3974"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1487"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1487"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1487"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}