customer-managed encryption key

Related topics

• customer-managed encryption key is part of Cloud Key Management Service From the official documentation: “[Create a customer-managed encryption key (CMEK)](/kms/docs/creating-keys) in Cloud Key Management Service.”
• customer-managed encryption key depends on Cloud Key Management Service From the official documentation: “The Cloud Key Management Service key for encrypting your log data”
• Cloud HSM works with customer-managed encryption key From the official documentation: “Cloud HSM provides a layer of abstraction on top of the HSM modules. This abstraction lets you use your keys in CMEK integrations or the Cloud KMS APIs or client libraries without HSM-specific code.”
• customer-managed encryption key is an alternative to Google-owned and Google-managed encryption key From the official documentation: “Optional. To use a customer-managed encryption key (CMEK) to encrypt messages, select **Cloud KMS key**. By default, Pub/Sub uses Google default encryption, which doesn't require a CMEK.”
• BigQuery Data Transfer Service works with customer-managed encryption key From the official documentation: “When you specify a CMEK with a transfer, the BigQuery Data Transfer Service applies the CMEK to any intermediate on-disk cache of ingested data so that the entire data transfer workflow is CMEK compliant.”
• Cloud EKM works with customer-managed encryption key From the official documentation: “You can use your Cloud EKM keys in CMEK-integrated services or using the Cloud KMS APIs and client libraries.”
• Cloud Key Management Service works with customer-managed encryption key From the official documentation: “Several Google Cloud products are integrated with Cloud KMS to support Customer-Managed Encryption Key (CMEK) functionality.”
• customer-managed encryption key depends on Cloud KMS From the official documentation: “To encrypt restored disks with a Customer-Managed Encryption Key (CMEK), make sure that the Compute Engine service agent (`service-PROJECT_NUMBER@compute-system.iam.gserviceaccount.com`) has the [Cloud KMS CryptoKey Encrypter/Decrypter…”
• customer-managed encryption key secures Cloud SQL From the official documentation: “To use a configured customer-managed encryption key (CMEK) to secure access to Cloud SQL, enter the **Resource Name of the Encryption key** in the text field.”
• customer-managed encryption key is an alternative to customer-supplied encryption keys From the official documentation: “Alternatively, you can encrypt your snapshots by using either a [customer-managed encryption key (CMEK)](/kms/docs/cmek) or a [customer-supplied encryption key (CSEK)](/docs/security/encryption/customer-supplied-encryption-keys).”
• customer-managed encryption key secures Dataflow From the official documentation: “(Optional) To [encrypt the Dataflow pipeline state](/dataflow/docs/guides/customer-managed-encryption-keys) with a customer-managed encryption key, click **Show encryption options** and select **Use a customer-managed encryption key (CMEK)**.”
• customer-managed encryption key secures log bucket From the official documentation: “Log buckets are regional resources with a fixed location and are encrypted with either a customer-managed encryption key (CMEK) or a Google-owned and Google-managed encryption key.”
• customer-managed encryption key secures Pub/Sub From the official documentation: “Your topic is configured to use a [customer-managed encryption key](/pubsub/docs/encryption) from Cloud Key Management Service (Cloud KMS), and Pub/Sub can't encrypt the published message:”
• 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 Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
• Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
• Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
• BigQuery works with BigQuery Data Transfer Service From the official documentation: “The BigQuery Data Transfer Service uses load jobs to load Amazon S3 data into BigQuery.”
• Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• CMEK secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• 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.”
• Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, 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.”
• Application Default Credentials secures Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• 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.”
• Cloud Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• CMEK secures BigQuery From the official documentation: “Enable CMEK for BigQuery Tables”
• 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.”
• Customer-Managed Encryption Keys is an alternative to customer-supplied encryption keys From the official documentation: “CSEK and CMEK are mutually exclusive for the target disk.”
• Application Default Credentials works with Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
• CMEK secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• 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.”
• Customer-Managed Encryption Keys secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• Dataflow depends on Application Default Credentials From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
• 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:”
• BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud KMS depends on Application Default Credentials From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• log bucket is part of Cloud Logging From the official documentation: “Cloud Logging log buckets can be configured to encrypt data with CMEK.”
• Application Default Credentials works with Cloud KMS From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, 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.”
• BigQuery Data Transfer Service works with Cloud Logging From the official documentation: “The BigQuery Data Transfer Service exports logs and metrics to Cloud Monitoring and Cloud Logging that provide observability into your transfers.”
• BigQuery Data Transfer Service works with Pub/Sub From the official documentation: “If you intend to set up transfer run notifications for Pub/Sub, you must have `pubsub.topics.setIamPolicy` permissions.”
• 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.”