Customer-managed encryption keys (CMEK)

By default, Agent Assist encrypts customer content at rest. Agent Assist handles encryption for you without any additional actions on your part. This option is called Google default encryption.

If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in Cloud KMS with CMEK-integrated services including Agent Assist. Using Cloud KMS keys gives you control over their protection level, location, rotation schedule, usage and access permissions, and cryptographic boundaries. Using Cloud KMS also lets you view audit logs and control key life cycles. Instead of Google owning and managing the symmetric key encryption keys (KEKs) that protect your data, you control and manage these keys in Cloud KMS.

After you set up your resources with CMEKs, the experience of accessing your Agent Assist resources is similar to using Google default encryption. For more information about your encryption options, see Customer-managed encryption keys (CMEK).

Note: This is a limited access feature. In order to use CMEK, you must contact your Google representative to request access.

Protected data

Only Conversation data at-rest in a supported location can be protected with CMEKs.

Supported Locations

CMEK is available in all Agent Assist locations except global and eu. For more details, see also the Agent Assist regionalization page.

Limitations

CMEK is also available for all the features that Agent Assist locations support, including the following:

• Summarization with a baseline model
• Summarization with custom sections
• Transcription
• (Proactive) Generative Knowledge Assist

Create keys

To create keys, you use the KMS service. For instructions, see Creating symmetric keys. When creating or choosing a key, you must configure the following:

• Be sure to select the location that you use for your Agent Assist data, otherwise, requests will fail.

Enable CMEK in Agent Assist

Before you create any Agent Assist data in a specific location, you can specify whether the data in this location will be protected by a customer-managed key. Configure your key at this time.

Warning: You cannot change encryption key settings for a location once it has been specified. If you already have Agent Assist data for a Google Cloud project in a location, you won't be be able to add a CMEK key given this location.

Prerequisites

1. Create the CCAI CMEK Service account for your project with Google Cloud CLI. For more information, see gcloud services identity documentation.

   gcloud beta services identity create --service=dialogflow.googleapis.com --project=PROJECT_ID

   The service account will be created. It won't be returned in the create response, but will have the following format:

   [e-mail]

2. Grant the CCAI CMEK Service account the Cloud KMS CryptoKey Encrypter/Decrypter role to ensure that the service has permissions to encrypt and decrypt with your key.

   gcloud kms keys add-iam-policy-binding KMS_KEY_ID \
   --project=PROJECT_ID \
   --location=LOCATION_ID \
   --keyring=KMS_KEY_RING \
   --member=serviceAccount:[e-mail] \
   --role=roles/cloudkms.cryptoKeyEncrypterDecrypter

Configure a key for an Agent Assist location

1. Use InitializeEncryptionSpec API to configure the key.

   You will need to provide the following variables:

   • PROJECT_ID: Your Google Cloud project ID.
   • LOCATION_ID: The location you chose to enable CMEK in Agent Assist.
   • KMS_KEY_RING: The key ring your KMS key was created in. (The location in the key ring, like projects/PROJECT_ID/locations/LOCATION_ID/keyRings/KMS_KEY_RING, must match the location where you're enabling CMEK.)
   • KMS_KEY_ID: The name of your KMS key that will be used to encrypt and decrypt Agent Assist data in the selected location.

   For example:

   curl -X POST \
       -H "Authorization: Bearer $(gcloud auth print-access-token)" \
       -H "Content-Type: application/json; charset=utf-8" \
       -d "{ encryption_spec: { kms_key: 'projects/PROJECT_ID/locations/LOCATION_ID/keyRings/KMS_KEY_RING/cryptoKeys/KMS_KEY_ID' } }" \
       "https://LOCATION_ID-dialogflow.googleapis.com/v2/projects/PROJECT_ID/locations/LOCATION_ID/encryptionSpec:initialize"

   You should receive a JSON response similar to the following:

   {
     "name": "projects/PROJECT_ID/locations/LOCATION_ID/operations/OPERATION_ID"
   }

2. Use GetOperation API to check the long-running operation result.

   For example:

   curl -X GET \
   -H "Authorization: Bearer $(gcloud auth print-access-token)" \
   "https://LOCATION_ID-dialogflow.googleapis.com/v2/projects/PROJECT_ID/locations/LOCATION_ID/operations/OPERATION_ID"

Check CMEK Settings

Use GetEncryptionSpec API to check the encryption key configured for a location.

For example:

    curl -X GET \
      -H "Authorization: Bearer $(gcloud auth print-access-token)" \
      "https://LOCATION_ID-dialogflow.googleapis.com/v2/projects/PROJECT_ID/locations/LOCATION_ID/encryptionSpec"
  

Revoke keys

To revoke Agent Assist access to the key, you could disable the KMS key version or remove the service account's Cloud KMS CryptoKey Encrypter/Decrypter role from the KMS key.

After key revocation the encrypted data will become inaccessible to Agent Assist and the service will no longer be in an operational state until the key permissions are reinstated.

Warning: If you have revoked the key for more than 30 days, the Agent Assist data encrypted by that key will be lost.