Cloud Services Are Vulnerable Without End-To-End Encryption

The growth of cloud services has been one of the most disruptive phenomena of the Internet era.  However, even the most popular cloud services (including Yahoo, Gmail, Microsoft Outlook 365, and Dropbox) are vulnerable to attack because their servers operate on unencrypted data.

 

The move to cloud-based services offers enormous benefits compared with managing these services in-house.  The cloud is scalable, cost-effective, easy to manage, and accessible to a wide range of devices anywhere.

 

But because cloud services represent a centralized repository of information, they are tempting targets for attackers. And even a single misconfiguration of a cloud server, can make them vulnerable.  If an attacker is successful in breaching a single user’s computer or phone, that user’s information will be compromised.  But if an attack targeting a server is successful, information for all users on that server can be leaked.  For example, Yahoo recently disclosed that over a billion user accounts were compromised.

 

Accordingly, the security industry has invested heavily in technologies and processes to protect cloud servers.  Many of these – such as firewalls, threat detection and analysis, and administrative processes – amount to “building taller walls” around the server.  But despite great effort and investment, attackers continue to prevail.

 

Assume the server is breached

 

What if the problem is turned around?  Instead of figuring out how to protect the server, what if the focus is on protecting the data whether or not the server has been compromised?  This can be achieved with end-to-end encryption, which means user data is decrypted only on their personal computer or smartphone; never on the server.  Therefore, if the server is breached an attacker will only be able to access encrypted data, which is unintelligible.  Unfortunately, end-to-end encryption is rarely used.

 

Many cloud providers tout their use of encryption for security, but the term “encryption” can mean many things.  Most services use something called ­encryption-in-transit.  To show how this works, we’ll consider a generic cloud-based email service.

 

Encryption in transit protects against passive attackers but not against server-side attacks

As shown in the diagram above, encryption in transit uses encryption to secure a message when it is being transmitted from a phone or computer to a server, often using technologies like SSL (Secure Sockets Layer) or TLS (Transport Layer Security).  This prevents an attacker from successfully carrying out a ‘Man In The Middle’ attack – watching Internet traffic and gleaning the contents of communication.  With encryption in transit, the decrypted message is available at both the device and the server.  This makes the server vulnerable to attack, because a successful breach of the server gives the attacker access to all the decrypted messages.

 

In attempt to address this problem, some cloud services also use encryption-at-rest, as shown below:

 

Encryption at rest protects against some attacks but also requires the keys to be on the server

Encryption-at-rest means that data is encrypted in the storage media on cloud servers when not being used.  Encryption-at-rest could prevent an attacker from accessing information on physical disks that were stolen from a data center — although such physical attacks are exceedingly rare.  Encryption at rest still cannot prevent an attack on the server from leaking valuable user data because the server can still “see” the decrypted information.  If the server can access the raw data, so can an attacker.

 

End-to-end encryption can solve the problem by adding the missing link – encryption-in-use –  as shown below:

 

With end-to-end encryption, the server is unable to ever decrypt messages since it does not have the keys

With end-to-end encryption, the server never has access to decrypted data.  The message is encrypted in the device of the sender, and it’s not decrypted until it reaches the device of the recipient.  Thus, a server attack will not compromise any user information.  An attacker may attempt to breach a single user’s device, but such an attack affects only that user – not everyone on the system.

 

 

What about Gmail, Outlook 365, and Dropbox?

 

Unfortunately, most major cloud service providers do not use end-to-end encryption – including Gmail, Outlook, Dropbox, Yahoo, and many others.  This is because these services rely on servers to process emails and files.  The servers absolutely must have access to user data.

 

 

PreVeil

 

PreVeil takes a different approach – basically not trusting the cloud.  It uses end-to-end encryption that provides encryption in-transit, in-use, and at rest.  The cloud server simply does not have access to unencrypted data so information is protected even when the cloud is breached.  Most important of all, PreVeil Email is designed to be very easy to use.   It can work with popular mail programs like Microsoft Outlook and Apple Mail, through a browser on a computer, or with an app for iPhone and iPad.  Users are identified by their regular email address; no special email or domain is required.

 
Watch our video which shows how PreVeil protects your email.
 

 

Check out and download PreVeil by visiting our download page.

 

 

The post Cloud Services Are Vulnerable Without End-To-End Encryption appeared first on PreVeil.



*** This is a Security Bloggers Network syndicated blog from PreVeil authored by Orlee Berlove. Read the original post at: https://www.preveil.com/blog/cloud-services-vulnerable-without-end-end-encryption/