How Meta Is Strengthening End-to-End Encrypted Backups

Meta’s HSM-based Backup Key Vault supports end-to-end encrypted backups for WhatsApp and Messenger by storing recovery codes in tamper-resistant hardware that Meta and third parties cannot access. The geographically distributed vault uses majority-consensus replication for resilience. Meta is strengthening the system with over-the-air fleet-key distribution for Messenger and public evidence of secure HSM fleet deployments.

Over-the-Air Fleet Key Distribution

• Clients verify HSM fleet authenticity using fleet public keys before establishing sessions.
• WhatsApp embeds these keys directly in the application.
• Messenger can receive keys over the air, allowing Meta to deploy new HSM fleets without requiring an app update.
• Keys are delivered in validation bundles:
  • Signed by Cloudflare
  • Counter-signed by Meta
  • Recorded in a Cloudflare audit log
• The complete validation process is documented in Meta’s Security of End-To-End Encrypted Backups whitepaper.

Transparent HSM Fleet Deployment

• Meta plans to publish evidence of the secure deployment of every new HSM fleet.
• Users will be able to verify deployment evidence using the audit procedures in the whitepaper.
• Deployments are expected to occur infrequently, generally no more than once every few years.
• The transparency initiative is intended to demonstrate that Meta cannot access users’ encrypted backups.

The system combines tamper-resistant HSMs, geographic replication, independently verifiable key distribution, and public deployment evidence. Readers seeking implementation details should consult the full whitepaper.