{"id":32549,"date":"2017-07-16T10:41:08","date_gmt":"2017-07-16T14:41:08","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/encryption-is-it-enough-cioreview.php"},"modified":"2017-07-16T10:41:08","modified_gmt":"2017-07-16T14:41:08","slug":"encryption-is-it-enough-cioreview","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/encryption-is-it-enough-cioreview.php","title":{"rendered":"Encryption -Is it enough? &#8211; CIOReview"},"content":{"rendered":"<p><p>      Jerry Irvine, EVP, CIO, Prescient Solutions    <\/p>\n<p>    CIOs and their corporations are looking for the magic bullet to    protect their intellectual property and the personally    identifiable information of their clients, partners and    employees. Legacy security measures such as firewalls and    antivirus provide little protection from hackers and malicious    users breaching the enterprise environment and the    implementation of more strict access controls.Data loss    prevention (DLP) solutions are cumbersome and limit the    productivity of end users.  <\/p>\n<p>    With these technical and business constraints in place, CIOs    are turning to encryption of data across the entire data life    cycle to mitigate the risks of lost or stolen information. But    does todays encryption technology really provide the levels of    confidentiality required in this totally Internet connected    world?  <\/p>\n<p>    There are three primary phases in which data can be encrypted:    in transit, at rest, and in use. The highest level of data    protection currently exists in the data transmission phase. In    this phase, encryption occurs between specific communicating    devices. Protection provided by encryption in transit includes    confidentiality from eavesdropping and sniffing, or    man-in-the-middle attacks. Applications such as VPN clients and    browser based HTTPS provide strong encryption processes which    protect the confidentiality of data making it very difficult    for unauthorized users to intercept. It is common practice for    organizations to encrypt of data transmitted from remote    devices; however, data that is being transmitted on internal    networks typically goes unencrypted. There is a perception that    data transmitting the internal network, or even that being    transmitted to remote facilities, is secure and therefore does    not require encryption. Nevertheless, an organizations    internal network can be easily breached making data vulnerable    to the same risks of eavesdropping, sniffing and    man-in-the-middle attacks. Consultants, vendors and individuals    off the street not only have access to wireless networks but    often have access to network jacks in conference rooms,    cafeterias and other common areas. Also, devices that do not    require direct authentication (i.e. printers, scanners,    industrial controls, etc.) can be infected with malware that    can eavesdrop, sniff, or capture traffic and send out    information to the Internet. Past concerns of implementing    encryption to internal data transit included increased overhead    on servers, network devices and end user workstations. This    overhead could cause systems delays, loss of connectivity and    loss or corruption of data. Many of todays server and network    technologies have data encryption capabilities built in to    allow for easier configuration and implementation and minimize    the impact on utilizations. Implementing encryption of data in    transit from endpoint to endpoint, both remotely and internally    is mandatory in todays cyber risk environment.  <\/p>\n<p>    The highest level of data protection currently exists    in the data transmission phase with the at rest and in use    phases close behind  <\/p>\n<p>    Another phase of data encryption is the encryption of data at    rest. Implementing encryption of data at rest is the easiest of    all phases and, in fact, is built in on many devices such as    smartphones, tablets and PCs. There are really no reasons not    to encrypt all data on smartphones, tablets, PCs; however,    there are some major limitations of encrypting data at rest.    Users and applications must be able read data in order to use    it, consequently, when a user or application logs into the    system the data must appear decrypted. This is both necessary    and a major vulnerability because when a user or application    logs in all data, even that data at rest that they have access    to, becomes readable. So, if a users device or application is    infected with a virus, malware, etc. and they log in all data    on their system or systems they can access becomes available to    the hacker.  <\/p>\n<p>    The last phase of data encryption is encryption of data in use,    this is the weakest link. As defined in the previous encryption    of data at rest section, in order to make use of data, it must    be readable or decrypted. Many applications, database companies    and cloud service providers are claiming different levels and    characteristics of encrypted data in use; but, current    technology does not make this completely possible. Encryption    of data in use relies heavily on encryption of data at rest and    in combination with strong authorization and access controls.    By allowing only authorized users, limiting their access to the    principles of least privilege and performing on the fly    decryption of data upon access, companies are providing a    minimal level of encryption of data in use.  <\/p>\n<p>    Based on the functionality of encryption within the different    phases, it must be obvious that encryption is not a silver    bullet for the protection of data.  <\/p>\n<p>    Encrypting data in transit can be compromised even if it is    being performed across both internal and remote networks via    the placement of malware on authorized devices that can    eavesdrop or sniff data as it traverses the enterprise.    Encrypting data at rest can also be overcome via the placement    of malware on an authenticated device and it can also be    bypassed by un-authorized users who illegally obtain valid user    ids and password which have rights to view the data. The    encryption of data in use with existing technologies uses the    same but stricter rules as defined within the encryption of    data at rest phase and therefore can be compromised in the same    ways.  <\/p>\n<p>    Encryption is designed to provide an additional layer of data    protection but complex authorization policies and strict access    controls providing only the least amount of privileges    necessary for a user to perform their functions are still    required in the protection of data. If hackers get into a    network but are unable to gain authorized access with valid    credentials, encryption will protect data from being read,    copied or manipulated. However, cyber incidents facilitated by    gaining un-authorized access to systems using valid user    credentials, such as phishing scams or social engineering, can    allow hackers complete access to decrypted data.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Continued here:<br \/>\n<a target=\"_blank\" href=\"https:\/\/datacenter.cioreview.com\/cioviewpoint\/encryption-is-it-enough-nid-10469-cid-18.html\" title=\"Encryption -Is it enough? - CIOReview\">Encryption -Is it enough? - CIOReview<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Jerry Irvine, EVP, CIO, Prescient Solutions CIOs and their corporations are looking for the magic bullet to protect their intellectual property and the personally identifiable information of their clients, partners and employees. Legacy security measures such as firewalls and antivirus provide little protection from hackers and malicious users breaching the enterprise environment and the implementation of more strict access controls.Data loss prevention (DLP) solutions are cumbersome and limit the productivity of end users. With these technical and business constraints in place, CIOs are turning to encryption of data across the entire data life cycle to mitigate the risks of lost or stolen information<\/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-32549","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/32549"}],"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=32549"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/32549\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=32549"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=32549"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=32549"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}