Single-tenant Cloud HSM

Related topics

• Cloud HSM is an alternative to Single-tenant Cloud HSM From the official documentation: “Single-tenant Cloud HSM provides the same functionality as Multi-tenant Cloud HSM, with the added benefit of cryptographic isolation from other Google Cloud customers.”
• Single-tenant Cloud HSM is part of Cloud Key Management Service From the official documentation: “You can import into Multi-tenant Cloud HSM keys, Single-tenant Cloud HSM keys, or software keys in Cloud KMS.”
• Single-tenant Cloud HSM configures key From the official documentation: “If you want to create the key in a Single-tenant Cloud HSM instance, set `PROTECTION_LEVEL` to `hsm-single-tenant` and add the `--cryptoKeyBackend` flag to specify the resource identifier of the Single-tenant Cloud HSM instance where you want to create the key:”
• Cloud HSM is part of Cloud Key Management Service From the official documentation: “You can import into Multi-tenant Cloud HSM keys, Single-tenant Cloud HSM keys, or software keys in Cloud KMS.”
• Cloud Key Management Service works with CMEK From the official documentation: “With CMEK, you can use your cryptographic keys, managed within Cloud Key Management Service (Cloud KMS), to protect your RAG corpus data.”
• 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).”
• 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.”
• 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.”
• key ring is part of Cloud Key Management Service From the official documentation: “`LOCATION`: the Cloud KMS location of the key ring.”
• Cloud HSM depends on Cloud Key Management Service From the official documentation: “Because Cloud HSM uses Cloud KMS as its front end, you can leverage all the conveniences and features that Cloud KMS provides.”
• Cloud HSM works with Cloud Key Management Service From the official documentation: “Creates a new key in Cloud KMS backed by Cloud HSM.”
• Cloud HSM works with Cloud KMS From the official documentation: “Creates a new key in Cloud KMS backed by Cloud HSM.”
• Cloud HSM works with CMEK From the official documentation: “How Cloud HSM handles request flows for creating keys, cryptographic operations, and CMEK integrations.”
• Cloud HSM works with Key Access Justifications From the official documentation: “To configure Key Access Justifications with a Cloud KMS or Cloud HSM key, you can either include the key access policy as a parameter when you create the key, or you can update the key with the policy after the key has been created.”
• 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 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 KMS works with CMEK From the official documentation: “To put project IDs in an ALLOW list to ensure that only keys from an instance of Cloud KMS within that project are used for CMEK.”
• Cloud KMS Autokey depends on Cloud HSM From the official documentation: “Cloud HSM is required if you want to use Autokey to provision Cloud KMS keys.”
• CMEK depends on Cloud Key Management Service From the official documentation: “Modify the CMEK configuration on a parameter by updating the parameter to use the new Cloud KMS key resource names.”
• key is part of Cloud Key Management Service From the official documentation: “Creates a new key in Cloud KMS with labels.”
• key is part of Cloud KMS From the official documentation: “CryptoKey: Cloud KMS key.”
• key is part of key ring From the official documentation: “Select the key ring that contains the key.”
• key is an alternative to key ring From the official documentation: “The resource name can be either a key or a key ring.”
• 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…”
• key ring is part of Cloud KMS From the official documentation: “Creates a new key ring in Cloud KMS”
• Key version is part of Cloud Key Management Service From the official documentation: “// checkStateImportedKey checks the state of a CryptoKeyVersion in KMS.”
• Key version is part of Cloud KMS From the official documentation: “// checkStateImportedKey checks the state of a CryptoKeyVersion in KMS.”
• Key version is part of key From the official documentation: “A key contains zero or more key versions.”
• Key version is part of key ring From the official documentation: “A key ring is the root resource for Cloud KMS keys and key versions.”