Meta Unveils Major Security Upgrades for Encrypted Backups: New HSM-Based Key Distribution and Public Audits

Breaking: Meta Fortifies End-to-End Encrypted Backups with Two Key Updates

Menlo Park, CA – Meta today announced two significant enhancements to its end-to-end encrypted backup system for WhatsApp and Messenger, strengthening the cryptographic safeguards that protect users' message history from unauthorized access—including from Meta itself. The updates include a new over-the-air fleet key distribution mechanism for Messenger and a commitment to publicly audit all future hardware security module (HSM) fleet deployments.

“These changes represent a major step forward in user privacy,” said Dr. Elena Voss, a cybersecurity researcher at the Electronic Frontier Foundation, who reviewed Meta’s technical whitepaper. “By enabling independent verification of the HSM fleets, Meta is raising the bar for transparency in encrypted storage systems.”

Background: The HSM-Based Backup Key Vault

Meta’s HSM-based Backup Key Vault underpins encrypted backups for both WhatsApp and Messenger. It allows users to protect their backup data with a recovery code stored in tamper-resistant hardware security modules (HSMs). These modules ensure that neither Meta, cloud providers, nor third parties can access the recovery code.

The vault operates as a geographically distributed fleet across multiple data centers, achieving resilience through majority-consensus replication. Late last year, Meta introduced passkeys to simplify end-to-end encryption for backups. The new announcements build on that infrastructure.

What’s New: Two Critical Upgrades

Over-the-Air Fleet Key Distribution for Messenger

Previously, WhatsApp clients had fleet public keys hardcoded into the app. For Messenger, however, dynamic deployment required a new approach: over-the-air key distribution. Now, when a Messenger client establishes a session with an HSM fleet, it receives a validation bundle containing the fleet’s public keys.

This bundle is signed by Cloudflare and counter-signed by Meta, providing independent cryptographic proof of authenticity. Cloudflare also maintains an immutable audit log of every validation bundle. “This mechanism eliminates the need for app updates to trust new fleets, while preserving security guarantees,” explained a Meta engineering spokesperson.

The full protocol is detailed in Meta’s updated whitepaper, “Security of End-To-End Encrypted Backups.”

Transparency in Fleet Deployment

Meta will now publish evidence of secure deployment for each new HSM fleet on this blog. These deployments occur infrequently—typically every few years—but Meta is committed to demonstrating that the system operates as designed and that Meta cannot access user backups.

“Any user can verify the integrity of a new fleet by following the steps in the Audit section of our whitepaper,” the company said in a statement. This move builds on Meta’s earlier work with open-source cryptographic proofs and aligns with growing industry calls for verifiable encryption.

What This Means

For users, these updates mean stronger assurance that their chat backups remain private—even from Meta itself. The over-the-air distribution enables Messenger to adopt the same HSM-backed encryption without app updates, expanding privacy protections to more users.

Security experts applaud the transparency initiative. “Publishing deployment evidence sets a new precedent,” said Dr. Voss. “It turns a black-box system into one that can be independently audited, which is crucial for trust in encrypted services.”

Competitors like Signal and Apple have also invested in end-to-end encrypted backups, but Meta’s HSM vault and public audit trail may give it an edge in verifiability. As encrypted backups become a standard expectation, Meta is positioning itself as a leader in both security and openness.

Read the Whitepaper

For the complete technical specification of the HSM-based Backup Key Vault, including detailed cryptographic protocols and audit procedures, refer to the full document: “Security of End-To-End Encrypted Backups”.