Meta planning a ‘Muse Confidential VM’ with user-held keys, TEE design, and expanded bug bounty
Meta intends to shift Muse agent isolation from policy-based controls to cryptographic/hardware enforcement by encrypting per-user VMs with keys held by users, publishing artifacts for third‑party review, and increasing bug-bounty payouts.
In this brief: 3 sections 2 min read
Muse Secure VM currently assigns a dedicated VM per user and uses a Sentinel gatekeeper for outbound network access.
Muse Confidential VM will encrypt the entire VM with a key held exclusively by the user.
The Confidential VM design aims to make provider access to user data cryptographically impossible rather than merely prohibited by policy.
Meta granted select third‑party security firms access to Confidential VM source code for review.
The company intends to publish binaries and maintain a transparency log to enable external verification.
These artefacts are positioned as the primary mechanisms for independent validation of the architecture.
Meta expanded its public bug-bounty program up to $300,000 total and up to $130,000 for prompt-injection bugs affecting a single user.
A key challenge remains user key management — keeping user control without risking irreversible data loss.
Effectiveness of the model will depend on usability of key handling and the transparency measures described.