{"id":31527,"date":"2017-03-01T17:41:01","date_gmt":"2017-03-01T22:41:01","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/how-encryption-makes-your-sensitive-cloud-based-data-an-asset-not-a-liability-security-intelligence-blog.php"},"modified":"2017-03-01T17:41:01","modified_gmt":"2017-03-01T22:41:01","slug":"how-encryption-makes-your-sensitive-cloud-based-data-an-asset-not-a-liability-security-intelligence-blog","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/how-encryption-makes-your-sensitive-cloud-based-data-an-asset-not-a-liability-security-intelligence-blog.php","title":{"rendered":"How Encryption Makes Your Sensitive Cloud-Based Data an Asset, Not a Liability &#8211; Security Intelligence (blog)"},"content":{"rendered":"<p><p>    Organizations are adopting encryption at a rapid and    increasingly urgent pace. Why? Because encryption helps    organizations support dynamic industry regulations while also    protecting sensitive data thats placed in the cloud.  <\/p>\n<p>    The trend of adopting public cloud solutions continues to grow,    but protecting critical data in the cloud is still a major concern. Its critical to    protect data against external breaches and unauthorized access    by cloud service providers. Collectively, organizations are    diligently working with consultants and suppliers to implement    solutions to keep their data safe.  <\/p>\n<p>    In many specific instances, companies want to prevent their    data from being accessible to cloud service providers (CSPs).    However, organizations are now facing a new dilemma: What are    they supposed to do when they want to permanently delete their    data in the cloud?  <\/p>\n<p>    Regulatory compliance and cloud data protection are two driving    reasons for establishing encryption and encryption key    management strategies. Furthermore, in the new world of cloud    data security, the old concept of a castle has become    ineffective; the concept of a curated museum is much more    applicable to cloud data security. In this new world,    organizations want to share data appropriately with many users    and platforms without running the risk that it will be taken,    changed, hijacked, destroyed or accessed by unauthorized users.  <\/p>\n<p>    Learn    more about Multi-Cloud Data Encryption  <\/p>\n<p>    To complicate matters, the value of data can change quickly. As    we know, information such as quarterly financial data has high    value prior to its disclosure, but the necessity to keep it    private significantly declines once the announcement of    financial performance is released to the market. However, other    data, such as pharmaceutical trial data, HR information from    divested organizations and historical notes on litigation    proceedings, can quickly become a liability if it is    unintentionally disclosed to the wrong party after the    collective work on these efforts has been completed.  <\/p>\n<p>    When you combine the need for privacy, the desire to    collaborate using shared data and the trend of leveraging cloud    applications and storage, you can see the need to not only    protect cloud-based data, but also to manage it throughout its    entire life cycle, from creation to destruction. Furthermore,    in the case of cloud deployments, this process needs to be    managed and controlled in an environment that is not physically    under your control. This last requirement raises the following    questions:  <\/p>\n<p>    Encryption has historically been used to protect data against    unauthorized use. However, encryption can effectively erase    data as well. This is called cryptographic erasure.  <\/p>\n<p>    The National Institute of Science and Technology (NIST)    released Special Publication 800-88, Revision 1:    Guidelines for Media Sanitization, which detailed how    encryption is part of media and data sanitation.  <\/p>\n<p>    If strong cryptography is used, the publication stated,    sanitization of the target data is reduced to sanitization of    the encryption key(s) used to encrypt the target data. In    laymens terms, this means that if the data is encrypted and    you destroy the keys, the data is erased.  <\/p>\n<p>    Of course, there are some qualifiers to claiming sanitization    by cryptographic erasure. First, you must ensure that you have    encrypted the data from the moment it was originally stored.    Next, verify that you have exclusive access to all data    encryption keys and ensure that all keys are wrapped under one    or more wrapping keys. Finally, delete the wrapping keys to    render the data encryption keys and data itself unrecoverable.    Fortunately, these steps are not difficult to follow if you    have the right tools.  <\/p>\n<p>    For example, if you have a petabyte of data that has been    encrypted from the moment it was placed in the cloud and    control over the wrapping keys that protect the data encryption    keys, then when you delete the wrapping keys, you render data    encryption keys  and the petabyte of data  useless. This    happens regardless of where the data is stored or whether you    can even access the storage environment. In other words, you    can effectively erase a petabyte of data by deleting just a few    kilobytes of keys. Thats cryptographic erasure, and its    powerful.  <\/p>\n<p>    Naturally, you may want to recover the petabytes of bits    associated with your now-useless data. Why pay to store    petabytes of random bits? However, that is secondary to the    erasure of the data itself.  <\/p>\n<p>    The logistics of implementing cryptographic erasure    fundamentally requires the system that stores and encrypts the    data to be separate from that of encryption key management.    Leveraging key life cycle management software packages helps    maintain separation of these duties and functions.  <\/p>\n<p>    Keeping your encryption engine separate from the encryption    keys, as well as keeping the keys well-managed, is not just a    best practice, but also keeps you on the right side of    regulations and helps protect your most precious assets  your    encryption keys and encrypted data  from threat actors.    Remember that storage is inexpensive, but data is becoming    infinitely more valuable, both as an asset and a liability.    Control your data, protect it and ensure that it has a clear    life cycle that you control.  <\/p>\n<p>    The future architecture of data protection is clearly modular.    We need to:  <\/p>\n<p>    Following these practices ensures that your data, protected    through encryption, will provide value through its lifetime and    can be securely deleted when no longer valuable.  <\/p>\n<p>    To protect data in a multicloud environment, organizations    should still focus on implementing centralized policy    management as well as centralized key management.  <\/p>\n<p>    Guardium for Multi-Cloud Data Encryption offers the ability to    encrypt cloud data across multiple clouds. It also integrates    with IBM Security Key Lifecycle Manager. This    combination of local but highly redundant key management, and    the ability to concurrently manage tens of thousands of    encrypted file systems or volumes in multiple clouds, gives    organization the tools they need to protect and manage the    entire life cycle of data regardless of where it resides.  <\/p>\n<p>    Learn    more about Multi-Cloud Data Encryption  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Visit link:<br \/>\n<a target=\"_blank\" href=\"https:\/\/securityintelligence.com\/how-encryption-makes-your-sensitive-cloud-based-data-an-asset-not-a-liability\/\" title=\"How Encryption Makes Your Sensitive Cloud-Based Data an Asset, Not a Liability - Security Intelligence (blog)\">How Encryption Makes Your Sensitive Cloud-Based Data an Asset, Not a Liability - Security Intelligence (blog)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Organizations are adopting encryption at a rapid and increasingly urgent pace. Why<\/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-31527","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31527"}],"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=31527"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31527\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=31527"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=31527"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=31527"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}