{"id":21353,"date":"2014-05-14T09:52:40","date_gmt":"2014-05-14T13:52:40","guid":{"rendered":"http:\/\/www.opensource.im\/?p=21353"},"modified":"2014-05-14T09:52:40","modified_gmt":"2014-05-14T13:52:40","slug":"protecting-against-heartbleed-attacks","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/protecting-against-heartbleed-attacks.php","title":{"rendered":"Protecting against Heartbleed attacks"},"content":{"rendered":"<p><p>    May 13, 2014 \/\/ Nick Flaherty  <\/p>\n<p>    Microsemi is seeing the Heartbleed SSL vulnerability as an    opportunity for its cryptography key management plugin and    drop-in replacement for OpenSSL.  <\/p>\n<p>    Page 1 of 2  <\/p>\n<p>    The Heartbleed vulnerability in OpenSSL is one of the most    devastating hosted server-side vulnerabilities of all time,    said Michael Mehlberg, vice president of security products    management at Microsemi. Though a patch was quickly released,    there is no guarantee server keys will not be compromised    through similar vulnerabilities discovered in the future.    Microsemis WhiteboxSSL product is more than a patch; it is a    fundamental solution to the security problems related to    generating, storing, and transferring crypto keys through    networked systems. With WhiteboxSSL, server keys are    substantially better protected against memory attacks.  <\/p>\n<p>    WhiteboxSSL provides security for server keys in memory and at    rest. Designed for IT administrators who are responsible for    maintaining the IT security infrastructure, the white box    cryptography key protection techniques enable them to protect    the keys generated and managed by servers running the popular    OpenSSL software.<\/p>\n<p>    WhiteboxSSL replaces vulnerable key libraries found in OpenSSL,    and is packaged as a complete OpenSSL implementation or plugin,    and is also packaged with MicroSemis FPGA technology for    embedded designs. It uses typical OpenSSL cryptography    algorithms such as AES, ECC, SHA, and RSA; each is uniquely    obfuscated to an individual server. That is, every user of    WhiteboxSSL has a uniquely constructed key algorithm preventing    an attacker from creating a break-once-run-everywhere attack.  <\/p>\n<p>    According to Netcraft, OpenSSL is used on 66% of the active    websites on the Internet today, and approximately 17% of those    sites were exposed to the Heartbleed bug. A typical server    running OpenSSL will generate thousands of keys in its    lifetime. These keys are critical to securing the data stored    and transferred through that system. Compromising these keys    can lead to major breaches in privacy, exposure to sensitive    user data, and even loss of company IP. Microsemis WhiteboxSSL    enhances and complements its field-tested WhiteboxCRYPTO    providing the capability to protect OpenSSL-generated keys with    complex crypto-algorithm obfuscations and key transformations    rendering attempts to capture network keys impractical given    the tools available to a network-based attacker.  <\/p>\n<p>    Authentication & Encryption,Embedded tools  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>See the article here:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.electronics-eetimes.com\/en\/protecting-against-heartbleed-attacks.html?news_id=222921098&cmp_id=7\/RK=0\/RS=NkQTRw3mjQQg4SBKav_xxVgX8to-\" title=\"Protecting against Heartbleed attacks\">Protecting against Heartbleed attacks<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> May 13, 2014 \/\/ Nick Flaherty Microsemi is seeing the Heartbleed SSL vulnerability as an opportunity for its cryptography key management plugin and drop-in replacement for OpenSSL. Page 1 of 2 The Heartbleed vulnerability in OpenSSL is one of the most devastating hosted server-side vulnerabilities of all time, said Michael Mehlberg, vice president of security products management at Microsemi. Though a patch was quickly released, there is no guarantee server keys will not be compromised through similar vulnerabilities discovered in the future. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1600],"tags":[],"class_list":["post-21353","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/21353"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=21353"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/21353\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=21353"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=21353"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=21353"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}