{"id":11008,"date":"2014-03-18T22:41:35","date_gmt":"2014-03-19T02:41:35","guid":{"rendered":"http:\/\/www.opensource.im\/?p=11008"},"modified":"2014-03-18T22:41:35","modified_gmt":"2014-03-19T02:41:35","slug":"keys-to-the-castle-encryption-in-the-cloud","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/keys-to-the-castle-encryption-in-the-cloud.php","title":{"rendered":"Keys to the castle: Encryption in the cloud"},"content":{"rendered":"<p><p>      ''We need to be cautious that, similar to the promises      of PKI several years ago, the market is ready and the      technology robust enough to service client demands'    <\/p>\n<\/p>\n<p>    In a bid to reassure customers following revelations of    government intelligence agency snooping in 2013, cloud service    providers including Google and    Amazon    have rushed out free automatic server-side encryption on their    cloud services - and not before time.  <\/p>\n<p>    The move has been seen by many as a positive one for companies    that are mandated to protect customer data when running a    business application on Google, but it could equally be argued    that encouraging them to leave encryption in the hands of the    cloud provider is a step in the wrong direction.  <\/p>\n<p>    While it's obvious that Google and others are covering their    own backs and jumping on the marketing opportunity of    NSA-related paranoia by having these security processes in    place, it's not exactly clear just how adequate their    server-side measures are.  <\/p>\n<p>    After announcing in August last year that it would be    automatically encrypting all data on its cloud storage platform    before it is written to disk, Google added that it would still    advise data to be encrypted at the user end for those who    prefer to manage their own encryption keys, emphasising that    the responsibility for risk management still legally lies with    the customer.  <\/p>\n<p>    Jamal Elmellas, technical director at data security specialist    Auriga, strongly    advises that organisations should be wary from the outset of    cloud providers with proprietary encryption software and    mechanisms, especially those that retro-fit encryption to their    already established solutions.  <\/p>\n<p>    Encryption should be intrinsic to the solution, says    Elmellas. It should be considered from the outset by the    provider, and this enables them to offer a solution which    applies the most appropriate type of encryption to the right    parts of the infrastructure.  <\/p>\n<p>    Processes, logging, auditing and total involvement by the    customer are a few of the ways that risks can be minimised when    outsourcing encryption, but for companies handling sensitive    data, encrypting everything themselves may seem like the safest    bet.  <\/p>\n<p>    However, as Elmallas explains, this option opens up a whole new    complex set of considerations.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Read this article:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.information-age.com\/technology\/security\/123457820\/keys-castle-encryption-cloud\/RS=^ADAZsgrqd0lHI37XPnt84dCleT9Qjo-\" title=\"Keys to the castle: Encryption in the cloud\">Keys to the castle: Encryption in the cloud<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> ''We need to be cautious that, similar to the promises of PKI several years ago, the market is ready and the technology robust enough to service client demands' In a bid to reassure customers following revelations of government intelligence agency snooping in 2013, cloud service providers including Google and Amazon have rushed out free automatic server-side encryption on their cloud services - and not before time. The move has been seen by many as a positive one for companies that are mandated to protect customer data when running a business application on Google, but it could equally be argued that encouraging them to leave encryption in the hands of the cloud provider is a step in the wrong direction. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-11008","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/11008"}],"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=11008"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/11008\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=11008"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=11008"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=11008"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}