Using Customer Managed Key

Last Updated:

The Customer Managed Key service allows organizations to provide and manage their own encryption keys for certain customer content stored in the Zoom Cloud. Zoom supports Amazon Key Management Service (KMS) and Oracle OCI Vault. Organizations need to manage the keys with either of these cloud KMS providers. This allows for encryption of applicable content stored in the Zoom Cloud using the keys that the organization controls.

The following types of content are protected by Customer Managed Key:

  • Zoom Meeting and Webinar recordings (including transcripts and in-meeting chat text, unless shared with with Team Chat)
    Note: Meeting/Webinar transcripts do not include a search index of transcripts
  • Archiving for meetings and webinars
  • Zoom Phone voicemail and recordings (including transcripts) and MMS messages
  • Zoom calendar tokens for Zoom rooms as well as user calendar tokens
  • Microsoft Teams tokens
  • Zoom Team chat (any internal messages including emojis, attached files including code snippets, but not reaction emojis or giphys as they are only referenced)

Note: Associated metadata such as used for searching may not be encrypted with the customer’s key.

This article covers:

Prerequisites for using Customer Managed Key

How to use Customer Managed Key with AWS

How to set up your AWS account           

To set up your AWS account, sign up at https://aws.amazon.com/ 

Where to create an AWS KMS key

Create your KMS in the same location/region where you have configured your account data to reside. This is US East 1 region by default.

How to configure Customer Managed Key in AWS

The AWS KMS keys that you create are considered Customer Managed Keys. Customer Managed Keys are KMS keys in your AWS account that you create, own, and manage. Before you get started with Customer Managed Key service in the Zoom cloud, follow the steps below:

  1. Create a KMS key with the following configuration:
    • Key type: Symmetric
    • Key usage: Encrypt and decrypt
    • Key material origin: KMS
    • Regionality: Multi-Region key
  2. Replicate the KMS key to other AWS regions you wish to host the key in, for redundancy. 
  3. Configure your key policy and IAM (Identity access management) policy appropriately in all of your AWS regions to specify access to your keys by copying and editing the template below into your AWS console.

Configuring your key’s policy

In order to configure your key’s policy, go to the Customer Managed Key page in the Encryption Keys section of the AWS KMS management console. The first time you edit the generated key policy, you have to click Switch to policy view in order to see and edit the JSON representation. 

Editing the JSON allows you to do the following:

  • Allow-list the Zoom Key Broker AWS account number
  • Specify which AWS KMS methods are permitted

Note: Remember to include your unique customer account number from your Zoom representative. 

This is an example template of a key policy that you could customize to meet your organization's needs:

{ "Version": "2012-10-17",

    "Statement": [

        {   "Effect": "Allow",

            "Principal": {

                    "AWS": "arn:aws:iam::YOUR_AWS_ACCOUNT_NUMBER:root"

                        },

                    "Action": "kms:*",

                    "Resource": "*"

        },

        {

            "Effect":"Allow",

            "Principal": {

                "AWS": [

                    "arn:aws:iam::409910850980:root"

                ]

        },

        "Action": [

                "kms:Decrypt",

                "kms:Encrypt",

                "kms:DescribeKey",

                "kms:GenerateDataKey*"

        ],

        "Resource":"*"       

    }

]

}

Once you set up replication of your key to another region, the key policy will be copied, but thereafter you need to make policy changes for each region separately.                           

How to enroll your keys with Zoom

  1. Sign in to the Zoom web portal.
  2. In the navigation menu, click Account Management then Security.
  3. Under Customer Managed Key, click Add Key.
  4. Choose Amazon AWS.
  5. Enter the key information and click Create. Enter the ARN of the KMS key.
  6. A message will appear displaying the ARNs that will be used for different regions. Click Continue when you are done reviewing. 
  7. Click + Add Services and determine which items will be encrypted. Place a check in the box next to any of the data types / services you want encrypted with your key, then click Add.   
  8. Click +Add recipient and add the users who will be notified by email if there is a key status change.

How to assign Customer Managed Key licenses to users

Users with assigned Customer Managed Key licenses will have their data encrypted. 

  1. Sign in to the Zoom web portal.
  2. Click User Management, then Users.
  3. Locate the user(s) you want to assign a license to. Check the box to the left of the user’s name then click the License drop down. 
  4. Cilck Zoom Customer Managed Key, then check the box next to the Feature
  5. Click Save

How to edit your keyset

  1. Sign in to the Zoom web portal.
  2. In the navigation menu, click Account Management then Security.
  3. Under Customer Managed Key, click Rotate Key.
  4. Add the key information and click Save.

Approaches to managing keys

To learn more about different approaches to managing keys, such as auto key rotation, manual key management, and external HSM key management, see Key management concepts.

How to use Customer Managed Key with OCI

How to set up your OCI account           

To set up your Oracle account, sign up for an Oracle Cloud Account.

Where to create an OCI Vault key

Create a Vault by selecting Security from the Oracle Cloud Infrastructure Console and then Vault (default selection). Additionally, one can define several options for these keys to support rotation, cross-region backup, etc. as required.

How to configure Customer Managed Key in OCI

The OCI Key Vault keys that you create are considered Customer Managed Keys. Customer Managed Keys are the Key Vault keys in your Oracle account that you create, own, and manage.

Configuring your key’s policy

To configure your key’s policy, it is recommended to create a new compartment for isolation. Only allow Zoom Customer Managed Key (CMK) to access the vault resources under this compartment, and then add the following key policy:

Define tenancy ZoomCMK as OCID: ocid1.tency.oc1..aaaaaaaat53ohyp5y7k4fiat6nqjsbt4yycrbqk5uixvut3g3jewutnfplaa

Define group CMKKeyBroker as OCID: ocid1.group.oc1..aaaaaaaabsasfty6c533e4iokfyl643hsmpwzposdx2eum7nu4jc244nrhka

Admit group CMKKeyBroker of tenancy ZoomCMK to use key-family in compartment {config compartment} where any {request.operation='Decrypt',request.operation='GenerateDataEncryptionKey’,request.operation=’Encrypt’}  

For more information on OCI Vault, its policies and other configuration guidelines please refer to their configuration docs.             

How to enroll your keys with Zoom

  1. Sign in to the Zoom web portal.
  2. In the navigation menu, click Account Management then Security.
  3. Under Customer Managed Key, click Add Key.
  4. Choose Oracle Key Vault.
  5. Enter the key information and click Create. Enter the OCID and the cryptographic endpoint  of the OCI Vault key.
  6. A message will appear displaying the OCIDs that will be used for different regions. Click Continue when you are done reviewing. 
  7. Click + Add Services and determine which items will be encrypted. Place a check in the box next to any of the data types / services you want encrypted with your key, then click Add.   
  8. (Optional) Click Users if you still need to assign licenses designating which users’ data will be encrypted.
  9. Click +Add recipient and add the users who will be notified by email if there is a key status change.

How to assign Customer Managed Key licenses to users

Users with assigned Customer Managed Key licenses will have their data encrypted. 

  1. Sign in to the Zoom web portal.
  2. Click User Management, then Users.
  3. Locate the user(s) you want to assign a license to. Check the box to the left of the user’s name then click the License drop down. 
  4. Click Zoom Customer Managed Key, then check the box next to the Feature
  5. Click Save

How to edit your keyset

  1. Sign in to the Zoom web portal.
  2. In the navigation menu, click Account Management then Security.
  3. Under Customer Managed Key, click Rotate Key.
  4. Add the key information and click Save.

Approaches to managing keys

To learn more about different approaches to managing keys, such as auto key rotation, manual key management, and external HSM key management, see the Oracle Key Management FAQ.

Guidelines to help monitor keys

Fallback Control

Access to the customer’s key at all times is critical to create and access any content which has been selected to be secured by CMK. Zoom not only encourages the use of replicated keys, but also supports a global "fallback control" option. If enabled and the customer’s key is not available for any reason, CMK falls back to a Zoom provided backup key for encryption. If the fallback option is not enabled and the customer’s key is not available, content will not be stored. Zoom Phone has specific settings that do not record or drop calls in case the customer’s key is inaccessible and fallback control is not enabled.

Once the customer’s key becomes available again, CMK will re-encrypt all content with the customer’s key.

Customer Managed Key deprovisioning

  1. If you want to revert to let Zoom manage encryption, schedule a date with your Zoom representative to deprovision this service.
    NOTE: Organization’s must keep their key available until the Zoom representative informs them that it can be deactivated. 
  2. Your Zoom representative will confirm the deprovisioning dates with our operations team.
  3. Your Zoom representative will let you know once deprovisioning has concluded, so that you can disable your keys.

Limitations

  • Keys are unreachable
    If Zoom cannot access the customer’s KMS key, then the functionality tied to key management, e.g., recording and viewing will fail. Once Customer Managed Key is enabled, it is important to have one or more KMS keys available for Zoom for encryption and decryption. If the organization wishes to deprovision Customer Managed Key, an administrator must work with a Zoom representative to plan a date for the deprovisioning. If the KMS key becomes unreachable, then functionality will be affected and Zoom cannot provide support.
  • Enrolling new keys
    Once an organization enrolls its KMS keys with Zoom, the supported types of assets are encrypted with customer-supplied keys from that point in time forward. Data that was created preceding key enrollment is still protected using a key that is managed by Zoom. That data is not re-encrypted using customer-supplied keys.
  • Zoom Phone
    Administrators can configure Zoom Phone to drop calls if encryption/decryption keys are not available for operation.
  • Uploading Recordings
    Users can upload a local recording to the Zoom cloud. Customer Managed Key does not protect these assets.

 

Zoom Community

Join the 100K+ other members in the Zoom Community! Login with your Zoom account credentials and start collaborating.