De forma predeterminada, Application Integration cifra el contenido del cliente en reposo. La integración de aplicaciones gestiona el cifrado por ti sin que tengas que hacer nada más. Esta opción se llama Cifrado predeterminado de Google.
Si quieres controlar tus claves de cifrado, puedes usar claves de cifrado gestionadas por el cliente (CMEKs) en Cloud KMS con servicios integrados con CMEKs, como Application Integration. Si usas claves de Cloud KMS, tendrás control sobre su nivel de protección, ubicación, calendario de rotación, permisos de uso y acceso, y límites criptográficos.
Además, Cloud KMS te permite ver los registros de auditoría y controlar los ciclos de vida de las claves.
En lugar de que Google sea el propietario y gestione las claves de cifrado de claves (KEKs) simétricas que protegen tus datos, tú controlas y gestionas estas claves en Cloud KMS.
Una vez que hayas configurado tus recursos con CMEKs, la experiencia de acceder a tus recursos de integración de aplicaciones será similar a la de usar el cifrado predeterminado de Google.
Para obtener más información sobre las opciones de encriptado, consulta Claves de encriptado gestionadas por el cliente (CMEK).
Antes de empezar
Asegúrate de que se han completado las siguientes tareas antes de usar CMEK para la integración de aplicaciones:
Habilita la API Cloud KMS en el proyecto que almacenará tus claves de cifrado.
Concede el siguiente rol de IAM en la clave de CMEK a la cuenta de servicio predeterminada de Application Integration en el proyecto compartido o de alojamiento de claves:
Asigna el rol de gestión de identidades y accesos Administrador de Cloud KMS a las personas que gestionen las claves CMEK. Además, concede los siguientes permisos de gestión de identidades y accesos al proyecto que almacena tus claves de cifrado:
Selecciona la casilla de la clave CMEK que quieras.
La pestaña Permisos del panel de la ventana de la derecha estará disponible.
Haz clic en Añadir principal e introduce la dirección de correo de la cuenta de servicio predeterminada.
Haz clic en Seleccionar un rol y, en la lista desplegable, selecciona el rol Encargado del encriptado y desencriptado de la clave criptográfica Cloud KMS.
Haz clic en Guardar.
Habilitar el cifrado con CMEK en una región de integración de aplicaciones
CMEK se puede usar para cifrar y descifrar datos almacenados en discos persistentes dentro del ámbito de la región aprovisionada.
Para habilitar el cifrado con CMEK en una región de Application Integration de tu proyecto de Google Cloud, sigue estos pasos:
En la Google Cloud consola, ve a la página Integración de aplicaciones.
Aparecerá la página Regiones, que muestra las regiones aprovisionadas para Application Integration.
En la integración que quieras usar con CMEK, haz clic en more_vertAcciones y selecciona Editar cifrado.
En el panel Editar cifrado, despliega la sección Configuración avanzada.
Selecciona Usar una clave de cifrado gestionada por el cliente (CMEK) y haz lo siguiente:
Seleccione una clave CMEK de la lista desplegable disponible. Las claves de CMEK que se muestran en el menú desplegable se basan en la región aprovisionada. Para crear una clave, consulta Crear una clave CMEK.
Haz clic en Verificar para comprobar si tu cuenta de servicio predeterminada tiene acceso de clave criptográfica a la clave CMEK seleccionada.
Cuando usas CMEK en Application Integration, tus proyectos pueden consumir cuotas de solicitudes criptográficas de Cloud KMS. Por ejemplo, las claves CMEK pueden consumir estas cuotas por cada llamada de cifrado y descifrado.
Las operaciones de encriptado y desencriptado con claves CMEK afectan a las cuotas de Cloud KMS de las siguientes formas:
En el caso de las claves de CMEK de software generadas en Cloud KMS, no se consume ninguna cuota de Cloud KMS.
En el caso de las claves CMEK de hardware (a veces denominadas claves de Cloud HSM), las operaciones de cifrado y descifrado se contabilizan en las cuotas de Cloud HSM del proyecto que contiene la clave.
En el caso de las claves CMEK externas (a veces denominadas claves de Cloud EKM), las operaciones de cifrado y descifrado se contabilizan en las cuotas de Cloud EKM del proyecto que contiene la clave.
[[["Es fácil de entender","easyToUnderstand","thumb-up"],["Me ofreció una solución al problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Es difícil de entender","hardToUnderstand","thumb-down"],["La información o el código de muestra no son correctos","incorrectInformationOrSampleCode","thumb-down"],["Me faltan las muestras o la información que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-11 (UTC)."],[[["\u003cp\u003eApplication Integration uses customer-managed encryption keys (CMEK) to allow users control over data encryption for compliance or regulatory needs, alongside the default Google-managed encryption.\u003c/p\u003e\n"],["\u003cp\u003eTo use CMEK, the Cloud KMS API must be enabled, the user must have the necessary IAM roles like Cloud KMS Admin, and a key ring with a key must be created in the same region as the Application Integration setup.\u003c/p\u003e\n"],["\u003cp\u003eThe default service account needs the Cloud KMS CryptoKey Encrypter/Decrypter role assigned to access the CMEK key, and verification must be done before using the key.\u003c/p\u003e\n"],["\u003cp\u003eEnabling CMEK encryption for an Application Integration region is a permanent action that cannot be reversed, and the chosen method of encryption for a region cannot be changed once set.\u003c/p\u003e\n"],["\u003cp\u003eUsing CMEK keys affects Cloud KMS quotas, with software keys not consuming quota, while hardware (HSM) and external (EKM) keys consume specific Cloud HSM and Cloud EKM quotas respectively, within the project where the keys are stored.\u003c/p\u003e\n"]]],[],null,["# Customer-managed encryption keys\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nCustomer-managed encryption keys\n================================\n\nBy default, Application Integration encrypts customer content at\nrest. Application Integration handles encryption for you without any\nadditional actions on your part. This option is called *Google default encryption*.\n\nIf you want to control your encryption keys, then you can use customer-managed encryption keys\n(CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including\nApplication Integration. Using Cloud KMS keys gives you control over their protection\nlevel, location, rotation schedule, usage and access permissions, and cryptographic boundaries.\nUsing Cloud KMS also lets\nyou view audit logs and control key lifecycles.\n\nInstead of Google owning and managing the symmetric\n[key encryption keys (KEKs)](/kms/docs/envelope-encryption#key_encryption_keys) that protect your data, you control and\nmanage these keys in Cloud KMS.\n\nAfter you set up your resources with CMEKs, the experience of accessing your\nApplication Integration resources is similar to using Google default encryption.\nFor more information about your encryption\noptions, see [Customer-managed encryption keys (CMEK)](/kms/docs/cmek).\n| **Tip:** When you use Google-owned and Google-managed encryption keys in Application Integration, your tenant projects consumes Cloud KMS cryptographic requests quotas. For more information about the quotas and limits, see [Cloud KMS quotas](/kms/quotas).\n\nBefore you begin\n----------------\n\nEnsure that the following tasks are completed before using CMEK for Application Integration:\n\n1. Enable the Cloud KMS API for the project that will store your encryption keys.\n [Enable Cloud KMS API](https://console.cloud.google.com/flows/enableapi?apiid=cloudkms.googleapis.com)\n\n | **Tip:** You can run Application Integration and Cloud Key Management Service in the same Google Cloud project, or in different projects.\n - If you use CMEK in a different project (shared or key-hosting project) than the one where you have set up Application Integration:\n 1. Enable the following API in the shared or key-hosting project:\n - [Cloud Key Management Service API](https://console.cloud.google.com/apis/library/cloudkms.googleapis.com)\n 2. Grant the following IAM role on the CMEK key to the Application Integration [default service account](/application-integration/docs/access-control-iam#sa) in the shared or key-hosting project:\n - [Cloud KMS CryptoKey Encrypter/Decrypter](/iam/docs/understanding-roles#cloud-kms-roles)\n\n | **Note:** To enable role assignment for the default service account, you must [verify the CMEK key](#enable-cmek) at least once, even if the first attempt fails.\n2. Assign the **Cloud KMS Admin** IAM role to the individuals managing the CMEK keys. Additionally, grant the following IAM permissions for the project that stores your encryption keys:\n - `cloudkms.cryptoKeys.setIamPolicy`\n - `cloudkms.keyRings.create`\n - `cloudkms.cryptoKeys.create`\n - `cloudkms.cryptoKeyVersions.useToEncrypt`\n\n | **Caution:**The Cloud KMS Admin role contains permissions for key maintenance and key version destruction. To protect your Cloud KMS resources, this role should only be assigned to individuals responsible for key administration.\n\n For information about granting additional roles or permissions, see [Granting, changing, and revoking access](/iam/docs/granting-changing-revoking-access).\n3. Create a [key ring](/kms/docs/creating-keys#create_a_key_ring) and a [key](/kms/docs/creating-keys#create_a_key). **Note:**The key ring and CMEK key must be created in the same region where you have set up Application Integration.\n\nAdd service account to CMEK key\n-------------------------------\n\n\nIn order to use a CMEK key in Application Integration, you must ensure that your [default service account](/application-integration/docs/access-control-iam#sa) is added and assigned with the [CryptoKey Encrypter/Decrypter](/iam/docs/understanding-roles#cloud-kms-roles) IAM role for that CMEK key.\n\n1. In the Google Cloud console, go to the **Key Inventory** page.\n\n\n [Go to Key Inventory page](https://console.cloud.google.com/security/kms/keys)\n2. Select the checkbox for the desired CMEK key. The **Permissions** tab in the right window pane becomes available.\n\n3. Click **Add principal**, and enter the email address of the default service account.\n4. Click **Select a role** and select the **Cloud KMS CryptoKey Encrypter/Decrypter** role from the available dropdown list.\n5. Click **Save**.\n\nEnable CMEK encryption for an Application Integration region\n------------------------------------------------------------\n\nCMEK can be used to encrypt and decrypt [data stored](/application-integration/docs/encryption#data) on PDs within the scope of the provisioned region.\n| **Caution:**Enabling CMEK encryption for an Application Integration region cannot be undone. This also means that you can't change the encryption method for a region if CMEK is already enabled.\nTo enable CMEK encryption for an Application Integration region in your Google Cloud project, perform the following steps:\n\n1. In the Google Cloud console, go to the **Application Integration** page.\n\n\n [Go to Application Integration](https://console.cloud.google.com/integrations)\n2. In the navigation menu, click **Regions** .\n\n The **Regions** page appears, listing the provisioned regions for Application Integration.\n3. For the existing integration that you want to use CMEK, click more_vert **Actions** and select **Edit encryption**.\n4. In the **Edit encryption pane** , expand the **Advanced settings** section.\n5. Select **Use a Customer-managed encryption key (CMEK)** , and do the following:\n 1. Select a CMEK key from the available drop-down list. The CMEK keys listed in the drop-down are based on the provisioned region. To create a new key, see [Create new CMEK key](#new-key).\n 2. Click **Verify** to check if your default service account has cryptokey access to the selected CMEK key.\n 3. If the verification for the selected CMEK key fails, click **Grant** to assign the [CryptoKey Encrypter/Decrypter](/iam/docs/understanding-roles#cloud-kms-roles) IAM role to the default service account.\n6. Click **Done**.\n\n### Create new CMEK\n\n\nYou can create a new CMEK key if you don't want to use your existing key, or if you don't have a key in the specified region.\n| **Note:** You can only use a [symmetric encryption key](/kms/docs/algorithms#symmetric_encryption_algorithms) in Application Integration.\nTo create a new symmetric encryption key, perform the following steps in the **Create a new key** dialog:\n\n1. Select Key ring:\n 1. Click **Key ring** and choose an existing key ring in the specified region.\n 2. If you want to create a new key ring for your key, click the **Create key ring** toggle and do the following steps:\n 1. Click **Key ring name** and enter a name of your key ring.\n 2. Click **Key ring location** and choose the regional location of your key ring. **Note:** For CMEK encryption, your key ring must be created in the same region where you have set up Application Integration.\n 3. Click **Continue**.\n2. Create Key:\n 1. Click **Key name** and enter a name for your new key.\n 2. Click **Protection level** and select either **Software** or **HSM** .\n\n For information about protection levels, see [Cloud KMS protection levels](https://cloud.google.com/kms/docs/protection-levels).\n3. Review your key and key ring details, and click **Continue**.\n4. Click **Create**.\n\n| **Note:** You must enable CMEK in a region before creating or publishing integrations in that region. Failure to do so may result in errors.\n\nEncrypted data\n--------------\n\n\nThe following table lists the data encrypted in Application Integration:\n\nCloud KMS quotas and Application Integration\n--------------------------------------------\n\nWhen you use CMEK in Application Integration,\nyour projects can consume Cloud KMS cryptographic requests\nquotas. For example, CMEK keys can consume these quotas for each encryption and decryption call.\n\nEncryption and decryption operations\nusing CMEK keys affect Cloud KMS quotas in these ways:\n\n- For software CMEK keys generated in Cloud KMS, no Cloud KMS quota is consumed.\n- For hardware CMEK keys---sometimes called Cloud HSM keys---encryption and decryption operations count against [Cloud HSM quotas](/kms/quotas#hsm) in the project that contains the key.\n- For external CMEK keys---sometimes called Cloud EKM keys---encryption and decryption operations count against [Cloud EKM quotas](/kms/quotas#ekm) in the project that contains the key.\n\nFor more information, see\n[Cloud KMS quotas](/kms/quotas)."]]
