Zoom's Device Managed Encryption is designed to help protect users' data by ensuring that only authorized users’ devices have the keys to decrypt it. Device Managed Encryption can be contrasted with other encryption types where Zoom holds the keys to allow server-side processing to provide features like efficient searches, cloud recordings, or AI Companion. Device Managed Encryption requires users to manage authorization for their own devices (and cryptographic keys), enhancing security against potential server compromises.
With Zoom’s Device Managed Encryption:
Currently, Device Managed Encryption is available for Restricted voicemails for Zoom Phone and Zoom Mail Service. End-to-end encryption is a stronger variant where only the sender and recipient (and their account administrators if escrow is in use) can access the data, without temporary server access, offering enhanced security over Device Managed Encryption.
This article covers:
To start using Device Managed Encryption, the Restricted voicemails feature for Zoom Phone or Zoom Mail Service must be enabled at the account level. Once Device Managed Encryption is enabled for a specific user, their Zoom desktop app will notify them and generate the encryption keys necessary to use the feature. This happens as each device comes online, or as the user starts to use the relevant features for the first time on that device.
In particular, for the user’s first device to do this, the following happens:
The user can access the Devices & Activity details on any of their devices:
As the user starts using their other devices, the newer devices will also be added to the Devices & Activity list, generate their own keys, and require approval from one of the user’s older devices to gain access to previously encrypted data.
When the user logs in to Zoom on a new device for the first time (or on an existing device after a feature leveraging Device Managed Encryption has been enabled for that user), this new device immediately generates the necessary encryption keys. It will immediately be able to send and receive new data using Device Managed Encryption. However, the device must be approved by an existing device before it can access previously encrypted data.
When the user signs in to a new device, the Devices & Activity pop-up window is displayed on all existing devices.
Once the user clicks Save, the existing device will share the encrypted data it can access with the newer device.
Note: Each device can only share access to previously encrypted data up to the date and time it can decrypt. For each device in the Devices & Activity list, the information dialog box will display the Data access, which shows the earliest date and time a device can decrypt data. Approving a new device upgrades its Data access to match that of the approving device.
In some cases, additional approvals from devices with the oldest data access might be needed for new devices to access all encrypted data. If these older devices are unavailable and backup keys or escrow are not set up, data may be permanently lost.
Note: When approving new devices, the user can check that the new devices are approved and the old devices show the same user fingerprint in order to prevent some sophisticated attacks. If the fingerprints are not the same, the user should not perform the approval and instead revoke the new devices.
If a device is lost, stolen, or decommissioned, it must be removed from the approved device list so that it can no longer be used to access newly generated encrypted content.
Backup keys are short alphanumeric strings that the user can generate, using one of their Zoom app devices, and use to regain access to their data if their devices are unavailable.
Each backup is treated like an additional user device. It is listed in the Devices & Activity section and can be revoked if lost or stolen. Initially, each backup key has as much access to encrypted data as the device that generated it (i.e. it has the same Data access value); but, as with regular devices, it can be approved using an older device to extend its access.
Note: If escrow is in place, escrow administrators can prevent their users from creating additional backup keys if desired.
To use a backup key to grant a device access to encrypted data, a user can: