Cloud EKM

Related topics

• Cloud EKM works with Cloud Key Management Service From the official documentation: “Cloud External Key Manager is integrated with Cloud Key Management Service to let you control and access external keys through supported third-party partners.”
• Cloud EKM works with Customer-Managed Encryption Keys From the official documentation: “You can also use an Cloud EKM key as a CMEK for encryption and decryption.”
• Cloud EKM works with Cloud KMS From the official documentation: “To learn how to use external keys with Cloud Key Management Service, see [Cloud External Key Manager](/kms/docs/ekm).”
• Cloud EKM depends on user managed replication From the official documentation: “Since Cloud EKM does not currently support the `global` multi-region, Cloud EKM keys can only be used with secrets configured for user managed replication.”
• Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Customer-Managed Encryption Keys depends on Cloud Key Management Service From the official documentation: “These keys are created and managed using Cloud KMS.”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud Key Management Service works with Customer-Managed Encryption Keys From the official documentation: “With CMEK, Cloud Key Management Service wraps your stored volume keys.”
• Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
• Customer-Managed Encryption Keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Customer-Managed Encryption Keys depends on Cloud KMS From the official documentation: “You must have a symmetric encryption key in Cloud KMS to use for CMEK.”
• Cloud KMS works with Customer-Managed Encryption Keys From the official documentation: “With customer-managed encryption keys (CMEK), volume keys are wrapped using your keys stored in Cloud KMS.”
• Customer-Managed Encryption Keys is part of Cloud Key Management Service From the official documentation: “The Cloud KMS keys that you create are customer-managed keys.”
• Cloud KMS Autokey configures Customer-Managed Encryption Keys From the official documentation: “Cloud KMS Autokey lets you automate the provisioning and assignment of CMEKs.”
• Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
• Customer-Managed Encryption Keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
• Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Key Management Service From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• BigQuery works with Cloud Key Management Service From the official documentation: “A Cloud KMS key is considered available and accessible by BigQuery under the following conditions:”
• Certificate Authority Service depends on Application Default Credentials From the official documentation: “To authenticate to CA Service, set up Application Default Credentials.”
• Certificate Authority Service depends on Cloud Key Management Service From the official documentation: “The CA then issues a certificate using the corresponding key in Cloud KMS to sign the certificate digest.”
• Certificate Authority Service works with Cloud Key Management Service From the official documentation: “CA Service is automatically configured to use Cloud Key Management Service for generating, storing, and utilizing CA signing keys.”
• Cloud KMS depends on Application Default Credentials From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Application Default Credentials works with Cloud KMS From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Application Default Credentials works with Cloud SQL From the official documentation: “Application Default Credentials are part of the client libraries you can use to access Cloud SQL.”
• BigQuery works with Cloud KMS From the official documentation: “BigQuery stores the name of the key used to encrypt the table content and uses that key when a table protected by Cloud KMS is queried.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Certificate Authority Service works with Cloud KMS From the official documentation: “Compared with Cloud Service Mesh certificate authority, CA Service supports per-customer, signing keys through [Cloud KMS](https://cloud.google.com/security/products/security-key-management) backed by [Cloud HSM](/kms/docs/hsm).”
• Cloud Key Management Service works with Cloud SQL From the official documentation: “Cloud KMS integrates with Cloud SQL.”
• Cloud KMS secures BigQuery From the official documentation: “If reading from BigQuery using query source, use this Cloud KMS key to encrypt any temporary tables created.”
• Cloud KMS Autokey is part of Cloud Key Management Service From the official documentation: “You can either create CMEKs manually to protect your AlloyDB resources or use Cloud KMS Autokey.”
• Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
• Cloud Logging works with Customer-Managed Encryption Keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Cloud SQL depends on Cloud KMS From the official documentation: “Cloud SQL administrator operations, such as create, clone, or update, might fail due to Cloud KMS errors, and missing roles or permissions.”
• Customer-Managed Encryption Keys is part of Cloud KMS From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Dataflow.”
• Application Default Credentials works with Certificate Authority Service From the official documentation: “To authenticate to CA Service, set up Application Default Credentials.”
• Application Default Credentials secures Cloud KMS From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Logging From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
• BigQuery works with Cloud KMS Autokey From the official documentation: “With Autokey, key rings and keys are generated on demand to support resource creation in BigQuery.”
• Certificate Authority Service works with Customer-Managed Encryption Keys From the official documentation: “CA Service supports CMEK for encrypting certain fields in certificates, such as the certificate subject and Subject Alternative Names (SANs).”
• Cloud Key Management Service depends on Application Default Credentials From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Cloud Key Management Service works with Cloud KMS Autokey From the official documentation: “Create an encryption management strategy using Cloud Key Management Service (Cloud KMS) with Autokey, Cloud External Key Manager (Cloud EKM), or both.”
• Cloud Key Management Service works with Cloud Logging From the official documentation: “If you [enable audit logging for Cloud KMS](https://cloud.google.com/logging/docs/audit/configure-data-access#config-console-enable), all the operations on the key are logged and viewable in Cloud Logging.”
• Cloud Key Management Service is an alternative to Customer-Managed Encryption Keys From the official documentation: “Unless your control package mandates a certain encryption key strategy, you can use any Google key management service, including Cloud Key Management Service, Cloud External Key Manager, or CMEK.”
• Cloud KMS Autokey works with Cloud Logging From the official documentation: “Every key generated, permission assigned, and policy adjusted by Autokey is recorded in Cloud Logging. This provides auditors with a continuous, automated audit trail to verify compliance.”
• Cloud Logging depends on Customer-Managed Encryption Keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Customer-Managed Encryption Keys is part of BigQuery From the official documentation: “If you require more control over encryption keys, BigQuery supports [customer-managed encryption keys](/bigquery/docs/customer-managed-encryption) in the [Cloud Key Management Service](/kms/docs).”
• Customer-Managed Encryption Keys configures Cloud Logging From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Customer-Managed Encryption Keys secures Cloud Logging From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Customer-Managed Encryption Keys is part of Cloud SQL From the official documentation: “Cloud SQL also lets you add another layer of encryption to data using [customer-managed encryption keys (CMEK)](/sql/docs/postgres/cmek).”