External key manager

Related topics

• Cloud External Key Manager works with External key manager From the official documentation: “A Google Cloud service for using your external keys that are managed within a supported EKM.”
• Cloud Key Management Service works with External key manager From the official documentation: “Indicates whether this is the last request to the EKM for a given Cloud KMS request.”
• Cloud KMS works with External key manager From the official documentation: “Destroying a *coordinated external key* version in Cloud KMS first destroys the key version in Google Cloud, and then sends a destruction request to the EKM to destroy the external key material.”
• customer-managed encryption keys works with External key manager From the official documentation: “Using external key manager (EKM) or hardware security module (HSM) with CMEK is in GA with allowlist.”
• External key manager is part of Cloud KMS From the official documentation: “NetApp Volumes supports Cloud KMS capabilities such as hardware security modules, External Key Manager, and the full key management lifecycle—generate, use, rotate, destroy.”
• 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.”
• 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 Key Management Service works with customer-managed encryption keys From the official documentation: “With CMEK, Cloud Key Management Service wraps your stored volume keys.”
• Cloud External Key Manager works with Key Access Justifications From the official documentation: “If you [use a Cloud EKM key](/alloydb/docs/cmek#ekm), then you can use Key Access Justifications to view the reason for each Cloud EKM request.”
• 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 Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• Cloud SQL works with Secret Manager From the official documentation: “Secret Manager attempts to update the credentials in your Cloud SQL instance.”
• customer-managed encryption keys secures Secret Manager From the official documentation: “In Secret Manager, you can use a CMEK to protect data at rest.”
• Key Access Justifications is part of Cloud External Key Manager From the official documentation: “You can use Key Access Justifications as part of Cloud EKM.”
• 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.”
• Certificate Authority Service works with Cloud SQL From the official documentation: “Cloud SQL hosts and manages the root CA and subordinate server CAs on Google Cloud Certificate Authority Service (CA Service).”
• 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 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.”
• BigQuery works with Cloud Key Management Service From the official documentation: “Change the Cloud KMS key for a BigQuery table”
• Cloud EKM works with Cloud Key Management Service From the official documentation: “You can use an [externally managed key](/kms/docs/ekm) with CMEK using the Cloud EKM service to make the key available through Cloud KMS.”
• Cloud Key Management Service works with Cloud SQL From the official documentation: “Cloud KMS integrates with Cloud SQL.”
• 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 part of Cloud KMS From the official documentation: “To protect your agents' data by using encryption keys that you control,<br>you can use [CMEKs](/kms/docs/cmek)<br>that you create and manage in Cloud KMS.”
• BigQuery works with Cloud KMS From the official documentation: “# Enable the BigQuery service account to encrypt/decrypt Cloud KMS keys”
• 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.”
• Cloud Key Management Service secures BigQuery From the official documentation: “You can encrypt data at the dataset or project level with the default customer-managed Cloud Key Management Service keys in BigQuery.”
• 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 works with Key Access Justifications From the official documentation: “Key Access Justifications enable control over viewing and approving key access<br>requests in Cloud KMS or [certain external key<br>management partners](/kms/docs/ekm#compatibility).”
• Key Access Justifications configures Cloud Key Management Service From the official documentation: “[Key Access Justifications](/assured-workloads/key-access-justifications/docs/overview) lets you set a policy on Cloud KMS keys to view, approve, and deny key access requests depending on the provided justification code.”
• Certificate Authority Service depends on 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).”
• 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).”
• 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 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 works with Key Access Justifications From the official documentation: “[Key Access Justifications](https://cloud.google.com/blog/products/identity-security/control-access-to-gcp-data-with-key-access-justifications) integrate with Cloud KMS and Cloud EKM.”
• 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. For more information, see [Cloud External Key Manager](/kms/docs/ekm), including the [Considerations](/kms/docs/ekm#considerations) section.”
• 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 Key Management Service works with Key Access Justifications From the official documentation: “[Key Access Justifications](https://cloud.google.com/blog/products/identity-security/control-access-to-gcp-data-with-key-access-justifications) integrate with Cloud KMS and Cloud EKM.”
• 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 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 secures Cloud SQL From the official documentation: “The reason is because Cloud SQL uses [regional Cloud KMS keys](https://cloud.google.com/sql/docs/mysql/configure-cmek#key) for encryption when CMEK is enabled on the instance.”
• Cloud SQL works with customer-managed encryption keys From the official documentation: “To learn more about using customer-managed encryption keys with Cloud SQL, see [Overview of customer-managed encryption keys](/sql/docs/postgres/cmek).”
• 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 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 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.”
• Key Access Justifications is part of Cloud EKM From the official documentation: “You can use Key Access Justifications as part of Cloud EKM.”
• Key Access Justifications configures Cloud KMS From the official documentation: “[Key Access Justifications](https://cloud.google.com/assured-workloads/key-access-justifications/docs/overview) | View logged justifications for each access request to Cloud KMS keys and optionally set a policy to authorize key access requests based on the provided…”