{"id":1567,"date":"2008-09-22T00:00:00","date_gmt":"2008-09-22T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/09\/22\/mcafee-to-pay-465-million-for-secure-computing\/"},"modified":"2021-12-30T11:39:37","modified_gmt":"2021-12-30T11:39:37","slug":"mcafee-to-pay-465-million-for-secure-computing","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/09\/22\/mcafee-to-pay-465-million-for-secure-computing\/","title":{"rendered":"McAfee to pay $465 million for Secure Computing"},"content":{"rendered":"<p>Computer security company McAfee Inc (MFE.N) plans to buy Secure Computing Corp (SCUR.O) for $465 million, adding specialized equipment that keeps hackers from breaking into computer networks.  The move, McAfee&#8217;s biggest acquisition to date, helps the No. 2 computer security company expand the bundle of products it can sell to businesses.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Santa Clara, California-based company said on Monday it will pay $5.75 per share of Secure Computing&#8217;s common stock, representing a 27 percent premium to the San Jose, California, company&#8217;s closing price of $4.52 on Friday.<\/p>\n<p>Secure Computing shares rose 23 percent to $5.56 on Nasdaq, while McAfee shares fell 1.7 percent to $36.68 in morning trading on the New York Stock Exchange.<\/p>\n<p>McAfee Chief Executive Dave DeWalt said the purchase will help round out McAfee&#8217;s line of products that help protect business networks.  The Secure Computing purchase will add 22,000 more customers in that area, he said.<\/p>\n<p>Jefferies &#038; Co. analyst Katherine Egbert said that while Secure Computing has great technology for protecting computer networks from hackers, it has a reputation for being difficult to use.  Ives called the McAfee deal &#8220;a better choice (for Secure Computer) than continuing to embark down a bumpy road in a tough macro environment.&#8221;<\/p>\n<p>http:\/\/news.yahoo.com\/story\/\/\/nm\/20080922\/tc_nm\/securecomputing_mcafee_dc<\/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-1567","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\/1567","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=1567"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1567\/revisions"}],"predecessor-version":[{"id":4054,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1567\/revisions\/4054"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1567"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1567"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1567"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}