Google-managed encryption keys

Related topics

• Cloud Key Management Service is an alternative to Google-managed encryption keys From the official documentation: “Change the data encryption configuration to use Google-managed encryption keys or Cloud Key Management Service keys.”
• Customer-Managed Encryption Keys is an alternative to Google-managed encryption keys From the official documentation: “Omit this argument to use the default setting, Google-managed encryption keys.”
• Google-managed encryption keys secures Cloud SQL From the official documentation: “By default, the Apigee Developer Portal Kickstart uses [Google Managed Encryption Keys](https://cloud.google.com/storage/docs/encryption/default-keys) to secure access to your Cloud SQL instance.”
• 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.”
• Customer-Managed Encryption Keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• BigQuery works with Spanner From the official documentation: “Federated analytics seamlessly combine data from Spanner and other sources in BigQuery.”
• 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 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.”
• 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:”
• Backup and DR works with Cloud Key Management Service From the official documentation: “Backup and DR supports customer-managed encryption keys (CMEK) that are managed in Cloud Key Management Service.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud Key Management Service works with Cloud SQL From the official documentation: “Cloud KMS integrates with Cloud SQL.”
• 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 works with Secret Manager From the official documentation: “This page describes four use cases for using Secret Manager to manage secrets with Cloud SQL:”
• Cloud SQL is an alternative to Spanner From the official documentation: “If a workload requires transaction processing with strong relational consistencies, [Spanner](/spanner/docs/overview) or [Cloud SQL](/sql/docs) can be better alternatives.”
• Customer-Managed Encryption Keys works with Secret Manager From the official documentation: “In Secret Manager, you can use a CMEK to protect data at rest.”
• Customer-Managed Encryption Keys secures Secret Manager From the official documentation: “You can either create CMEKs manually to protect your Secret Manager resources or use Cloud KMS Autokey.”
• Secret Manager secures Cloud SQL From the official documentation: “Secret Manager provides centralized and secure storage of sensitive data such as Cloud SQL configuration.”
• Backup and DR works with BigQuery From the official documentation: “Backup and DR integrates with Cloud Monitoring, Cloud Logging, and BigQuery services and provides the following benefits:”
• Backup and DR works with Cloud Logging From the official documentation: “You can view Backup and DR event logs in **Cloud Logging** by using the Google Cloud console and the Google Cloud CLI.”
• Backup and DR works with Cloud SQL From the official documentation: “Enhanced backups allow you to use Backup and DR Service with your Cloud SQL instances to manage your backups.”
• Backup and DR works with Customer-Managed Encryption Keys From the official documentation: “This guide explains how to enhance backup security by using Customer-Managed Encryption Keys (CMEK) with Backup and DR.”
• Cloud External Key Manager is part of Cloud Key Management Service From the official documentation: “In addition to these features, the Assured Workloads control package you choose will also determine which of the following Cloud KMS key types are available: - [Cloud EKM keys](/kms/docs/ekm#overview)”
• Cloud External Key Manager works with Cloud Key Management Service From the official documentation: “You can use an externally managed key with CMEK using the Cloud External Key Manager service to [make the key available](/kms/docs/ekm) through Cloud KMS.”
• Cloud External Key Manager is an alternative to Cloud Key Management Service 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 External Key Manager secures Cloud SQL From the official documentation: “To protect data in Cloud SQL instances, you can use keys that you manage within a supported external key management partner.”
• Cloud External Key Manager 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 External Key Manager works with Secret Manager From the official documentation: “In Secret Manager, you can use Cloud External Key Manager (Cloud EKM) keys to encrypt and decrypt secrets.”
• Cloud External Key Manager works with Spanner From the official documentation: “In addition, Spanner supports Cloud External Key Manager (Cloud EKM), which lets you store your keys in an external key manager outside of Google Cloud.”
• 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 Key Management Service works with Secret Manager 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 Secret Manager.”
• Cloud Key Management Service is an alternative to Secret Manager From the official documentation: “Secret Manager is the recommended technique for managing sensitive data with Cloud Build. For existing projects, you can continue using Cloud KMS, but for new projects, use Secret Manager.”
• Cloud Key Management Service depends on Spanner From the official documentation: “Cloud KMS stores all of its data and metadata in Spanner databases which provide high data durability and availability with synchronous replication.”
• Cloud Key Management Service works with Spanner From the official documentation: “After the database is created, Spanner calls Cloud KMS about every five minutes to make sure that the key is still valid.”
• 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.”
• Cloud Logging works with Spanner From the official documentation: “Both Spanner and Agent Platform provide monitoring dashboards and write logs to Cloud Logging, which can contain additional details.”
• Customer-Managed Encryption Keys secures Backup and DR From the official documentation: “With CMEK, you can protect your Backup and DR data using a cryptographic key that you control through Cloud Key Management Service.”
• 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 depends on Cloud External Key Manager From the official documentation: “The CMEK keys created for the EU region must be created with external protection level, requiring that you set up an EKM.”
• 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).”
• Customer-Managed Encryption Keys works with Spanner From the official documentation: “`SPANNER_PROJECT` - A Google Cloud project that contains a Spanner instance which uses the customer-managed encryption keys (CMEKs) that reside in `KEY_PROJECT`.”
• Customer-Managed Encryption Keys secures Spanner From the official documentation: “To learn how to use manually-created CMEKs to protect your Spanner resources, see [Secure a database with CMEK](/spanner/docs/use-cmek).”