Home Cyber Security News WhatsApp Rolls Out End-to-End Encrypted Cloud Backups

WhatsApp Rolls Out End-to-End Encrypted Cloud Backups

by Abeerah Hashim
WhatsApp encrypted cloud backup

WhatsApp has recently announced the launch of their end-to-end encrypted backups feature, even on cloud services. Earlier, despite having end-to-end encryption available by default, WhatsApp lacked a security feature for cloud backups.

WhatsApp End-to-End Encrypted Cloud Backups

As announced in the recent blog post, Facebook has introduced end-to-end encrypted cloud chat backups for WhatsApp users. The tech giant claims to be one of the first secure messaging apps to implement E2EE cloud backups.

WhatsApp already implements end-to-end encryption (powered by Signal’s protocol) for all users by default. This encryption applies to all chats, calls, and media exchanged on the platform, hence making the platform safe from interception.

However, users’ chats would become vulnerable upon backing up data to clouds, such as Google Drive or iCloud. Anyone accessing the drives could find the WhatsApp databases unencrypted there.

Nonetheless, with the recent move, WhatsApp users can securely backup their data to cloud services with E2E encryption.

This feature makes use of a newly implemented encryption key storage system. Users can enable E2EE backups managed by a securely generated encryption key. They can then store the key either manually or via a secure password to the Backup Key Vault.

Announcing this move in a Facebook post, Facebook’s CEO Mark Zuckerberg claimed WhatsApp to be the first to take such a step.

How WhatsApp E2EE Cloud Backup Works

Regarding how the key storage with the password would work, the post reads,

When someone opts for a password, the key is stored in a Backup Key Vault that is built based on a component called a hardware security module (HSM) — specialized, secure hardware that can be used to securely store encryption keys.

Whenever a user would require accessing backups (such as when installing WhatsApp to a new device), it would do so via the encryption key or the password.

In the latter case, the user would actually fetch the encryption key from the HSM via the password. At this point, the user needs to be careful about the password typed since multiple wrong attempts would render the key permanently inaccessible. WhatsApp implements this measure to curb brute-force attempts.

Explaining the mechanism further, the post reads,

WhatsApp’s front-end service, ChatD, handles client connections and client-server authentication, and will implement a protocol that sends the keys to the backups to and from WhatsApp’s servers. The client and HSM-based Backup Key Vault will exchange encrypted messages, the contents of which will not be accessible to ChatD itself.
The HSM-based Backup Key Vault will sit behind ChatD and provide highly available and secure storage for the encryption keys to the backups.

To implement this feature with reliability, the tech giant has distributed the HSM-based Backup Key Vault service across numerous data centers globally. With this step, the tech giant aims at preventing any issues due to potential data center outages.

The new feature will be available to all iOS and Android users in a few weeks.

Let us know your thoughts in the comments.

You may also like

Latest Hacking News

Privacy Preference Center


The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]


DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.



The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid