[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eConfidential VMs are Compute Engine VMs that encrypt sensitive code and data in memory during processing, using N2D, C2D, \u003ccode\u003ec3-standard-*\u003c/code\u003e, or C3D machine types.\u003c/p\u003e\n"],["\u003cp\u003eConfidential VMs provide encryption-in-use, complementing encryption-at-rest and encryption-in-transit, ensuring continuous data and application encryption.\u003c/p\u003e\n"],["\u003cp\u003eOrganization policies can be implemented to mandate the creation of Confidential VMs, and Cloud Monitoring and Cloud Logging are available to monitor and validate Confidential VM instances.\u003c/p\u003e\n"],["\u003cp\u003eFor enhanced security, Confidential mode for Hyperdisk Balanced can be used with Confidential VMs, leveraging hardware-based disk data encryption through Cloud HSM and trusted execution environments (TEEs).\u003c/p\u003e\n"],["\u003cp\u003eSecurity perimeter for Confidential VM interaction can be set up using shared VPC networks, org policies and firewall rules, allowing them to interact only with other Confidential VM instances.\u003c/p\u003e\n"]]],[],null,["*** ** * ** ***\n\nA Confidential VM is a Compute Engine VM that uses a\n[specific machine type](/confidential-computing/confidential-vm/docs/supported-configurations#machine-type-cpu-zone)\nand keeps your sensitive code and other data encrypted in memory during\nprocessing, that is, it performs *encryption-in-use* .\nTogether with [*encryption-at-rest*](/security/encryption/default-encryption)\nand [*encryption-in-transit*](/security/encryption-in-transit),\nConfidential VM can help keep your data and applications encrypted at\nall times.\n\nFor a more detailed conceptual overview, see\n[Confidential VM overview](/confidential-computing/confidential-vm/docs/confidential-vm-overview).\n\nTo get started using Confidential VM, see [Create a Confidential VM instance](/confidential-computing/confidential-vm/docs/create-a-confidential-vm-instance).\n\nYou can manage your Confidential VMs in some of the following ways:\n\n- You can use organization policy constraints to\n [ensure that instances created in your organization are Confidential VMs](/confidential-computing/confidential-vm/docs/enforce-confidential-vm-use).\n\n- You can use Cloud Monitoring and Cloud Logging to\n [monitor and validate your Confidential VM instances](/confidential-computing/confidential-vm/docs/monitor-integrity).\n\n- You can use shared Virtual Private Cloud (VPC) networks, organization policy\n constraints, and firewall rules to [set up a security perimeter](/confidential-computing/confidential-vm/docs/restrict-confidential-vm-interaction)\n that ensures your Confidential VM instances can only interact with\n other Confidential VM instances.\n\n- With the A3 machine series, you can create a Confidential VM instance\n that uses Intel TDX and has an attached\n GPU. For more information, see\n Confidential VM\n [supported configurations](/confidential-computing/confidential-vm/docs/supported-configurations).\n\nFor enhanced block storage security with Confidential VM, you can use\n[Confidential mode for Hyperdisk Balanced](/compute/docs/disks/disk-encryption#conf_hdb).\nConfidential mode for Hyperdisk Balanced adds another layer of security by enabling hardware-based encryption\nof disk data. Hyperdisk volumes in Confidential mode use\n[Cloud HSM](/kms/docs/hsm) and Trusted Execution Environments (TEE) to\nprovide additional cryptographic isolation. For more information about TEEs, see\n[Trusted Execution Environment Explainer](https://services.google.com/fh/files/misc/confidential_computing_overview.pdf)."]]