{"id":31267,"date":"2017-02-08T21:41:57","date_gmt":"2017-02-09T02:41:57","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/encryption-without-compromise-isbuzz-news.php"},"modified":"2017-02-08T21:41:57","modified_gmt":"2017-02-09T02:41:57","slug":"encryption-without-compromise-isbuzz-news","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/encryption-without-compromise-isbuzz-news.php","title":{"rendered":"Encryption Without Compromise &#8211; ISBuzz News"},"content":{"rendered":"<p><p>    Over the past decade, organisations across every vertical    market have attempted a wary balance between regulatory    compliance and business agility. Yet with the arrival of the    General Data Protection Regulation (GDPR) set to raise the bar    yet again in 2018, how can organisations navigate ever more    onerous regulatory requirements  and penalties for failure to    comply; escalating security risks; dispersed and diverse    infrastructure models and still achieve operational performance    objectives?  <\/p>\n<p>    Given evolving regulatory demands and threat landscape,    securing data in motion  especially across Wide Area Networks    (WAN)  is clearly essential. But when traditional encryption    has fundamentally compromised both network performance and    essential troubleshooting, once again security and agility are    in conflict.  <\/p>\n<p>    Paul German, CEOCertes    Networks, explains the role stealth encryption is playing    in delivering data security without operational compromise.  <\/p>\n<p>    Encryption Imperative  <\/p>\n<p>    In this increasingly regulated environment, encryption is  or    should be  a fundamental component of the defence in depth    security model. Whilst organisations globally have been    wrestling with the escalating security demands created in a    continually evolving cyber threat landscape, the introduction    in 2018 of the GDPR radically extends the business implication    of any data breach. After May 2018, not only must a company    inform all affected by the security breach, as well as the    Information Commissioners Office,within 72    hoursbut the fines can be up to 20 million or 4% of    global revenues. There is a very real risk that a data breach    could lead to company failure.  <\/p>\n<p>    Given the growing acceptance that breach is a when not if    event, organisations have evolved beyond perimeter only    security models to increasingly lock down data  both at rest    and in motion. Yet data encryption has had a chequered history.    Whilst in theory the ability to make all information    unintelligible, unusual and valueless to hackers and thieves is    clearly compelling, the challenges associated with deploying,    maintaining and managing encryption technologies have deterred    and inhibited many organisations.  <\/p>\n<p>    The key problem is the way in which encryption has been    deployed to date. Traditionally an organisations    infrastructure is broken down into seven layers  following the    Open Systems Interconnection model (OSI model), from the    physical (Layer 1) through to Application (Layer 7). The usual    technique of adding encryption at Layer 2 (Data Link) and Layer    3 (Network) essentially means asking routers and switches to    undertake an additional  and demanding  task.  <\/p>\n<p>    The result is not only drastically compromised network    performance but also significant management and troubleshooting    issues  often bad enough to drive organisations to switch off    the encryption solution. In addition, as soon as Layer 2 and    Layer 3 encryption is switched on, the organisation is    completely blind to the traffic going across the network: it is    not just the data that is encrypted but the file headers and    network packets. The only option, therefore, when the    application team needs to investigate performance problems is    to switch off encryption  creating additional risk and    leading to a security\/operations stand-off.  <\/p>\n<p>    Layer 4 Encryption  <\/p>\n<p>    The answer to the continued friction between operational goals    and security imperatives is to decouple encryption from the    infrastructure completely. Rather than being embedded in    routers, switches or firewalls, Layer 4 encryption technology    is completely separate from the underlying infrastructure. By    creating an overlay solution that is dedicated to providing the    level of trust for data in motion and applications moving    across the infrastructure, this model avoids any impact on    network performance and complexity. Furthermore, Layer 4    operates in stealth mode: it is only the data payload that is    encrypted  not the entire network data packet.  <\/p>\n<p>    This approach has two essential benefits. Firstly, a hacker    that cannot see that encryption has been turned on (because the    file headers are not encrypted), will have no idea whether the    data is sensitive or not  it all looks like worthless data,    malformed and of no use. Secondly, if the organisation needs to    troubleshoot, key information  such as source\/destination    ports and IP Address information is still visible,    enabling investigation and remedial work to be undertaken    whilst the encryption is still turned on. All of the    complex management and maintenance problems created by Layer 2    and Layer 3 encryption are removed. The data in motion is    secure without adding complexity or compromising operational    performance of the infrastructure.  <\/p>\n<p>    Layer 4 encryption also overcomes the problems created by    application vendors opting to introduce third party encryption    solutions into applications to create a secure connection    between clients and servers. While the theory was great,    security threats such as Heartbleed and Poodle, which    compromised sessions, threw application vendors into a spin.    The challenge of getting the third party to fix the problem,    then update the application, download a patch and ensure    customers have applied that patch across their estate is huge     leaving many applications still unpatched years later.    Creating a Layer 4 encryption overlay ensures that application    data is secure and resolves the software providers security    challenges. Indeed, even if the application encryption has been    updated, adding Layer 4 encryption creates a double encryption    model that ensures whatever may happen in the future to    compromise the application  Heartbleed Mark 2  the    organisation will be secure.  <\/p>\n<p>    Zero Trust Model  <\/p>\n<p>    The additional benefit of decoupling encryption from the    infrastructure is that it supports the zero trust model that is    gaining growing support across the security industry in    response to the ever changing threat landscape. While it    may appear logical to assume all owned infrastructure  from    data centres to branch offices, LANs to private WANs  is under    the organisations control and hence secure, in practice the    reality is very different.  <\/p>\n<p>    Firstly, the vast majority of data breaches now occur as a    result of user compromised credentials  providing a hacker    with direct access to that trusted network. Secondly, the    concept of a private WAN is flawed: private WAN services are    typically multiple organisations connections delivered over a    single shared managed service network using simple labels to    separate customer traffic. Unfortunately, simple    misconfigurations can result in the networks of two or more    organisations becoming merged; at which point secure data is    not only open to the service provider? but also at the mercy of    that organisations security posture  or lack of it.    That owned infrastructure is neither under the organisations    control nor secure.  <\/p>\n<p>    What value is a Service Level Agreement with a service provider    when the organisation has been breached, the regulator is set    to impose huge fines and customer confidence has plummeted?    Passing the baton of security over to a third party without    truly understanding and then mitigating that risk is a mistake.    The only way to ensure that an organisations data is secure is    to encrypt it before it hits the WAN  if the data does fall    into the wrong hands it is of absolutely no use at all.  <\/p>\n<p>    Conclusion  <\/p>\n<p>    This is the fundamental concept that organisations need to    understand  trust nothing, secure everything. By adopting a    zero trust model and accepting an inherent risk of breach    organisations can take a far more proactive approach to    securing data across the entire infrastructure.  <\/p>\n<p>    Adding Layer 4 Stealth encryption not only secures critical    data  and underpins compliance with regulations including GDPR     but it does so without compromising network performance or    operational agility.  <\/p>\n<p>      About Paul German    <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Go here to read the rest:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.informationsecuritybuzz.com\/study-research\/encryption-without-compromise\/\" title=\"Encryption Without Compromise - ISBuzz News\">Encryption Without Compromise - ISBuzz News<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Over the past decade, organisations across every vertical market have attempted a wary balance between regulatory compliance and business agility. <\/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-31267","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31267"}],"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=31267"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31267\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=31267"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=31267"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=31267"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}