[[["わかりやすい","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 UTC。"],[[["\u003cp\u003eGoogle Distributed Cloud (GDC) air-gapped automatically encrypts all customer content at rest using one or more encryption mechanisms, without any required user action.\u003c/p\u003e\n"],["\u003cp\u003eGDC employs FIPS 140-2 compliant self-encrypting drives and additional software-level volume encryption (VE) with unique XTS-AES-256 keys for each block storage data volume, with keys stored in an external HSM.\u003c/p\u003e\n"],["\u003cp\u003eCustomer-managed encryption keys (CMEK) provide enhanced control, transparency, and compliance, allowing users to manage keys and audit the encryption process, including cryptographic erasure for data destruction.\u003c/p\u003e\n"],["\u003cp\u003eCMEK is supported by several GDC services, such as block storage, virtual machine disks, database service, user container workloads, and storage, where a CMEK is created automatically upon creation of a CMEK supported datastore.\u003c/p\u003e\n"],["\u003cp\u003eEncryption at rest in GDC ensures that data remains unreadable to attackers even if they gain access to the storage devices, and that the managed encryption keys acts as a control access point to said data.\u003c/p\u003e\n"]]],[],null,["# Encryption at rest\n\nGoogle Distributed Cloud (GDC) air-gapped provides a comprehensive\nsecurity strategy that includes encryption at rest, which helps to protect your\ncontent from attackers. GDC encrypts your content at\nrest, without any action from you, using one or more encryption\nmechanisms. This document describes the approach to default encryption at rest\nfor GDC, and how to use it to keep your information more\nsecure.\n\nThis document is for security architects and security teams who\nuse or consider GDC. This document assumes a basic\nunderstanding of encryption and cryptographic primitives.\n\nEncryption at rest\n------------------\n\nGDC encrypts all customer content stored at rest,\nwithout any action from you, using one or more encryption mechanisms.\nEncryption at rest is encryption that protects data stored on a disk, including\nsolid-state drives, or backup media.\n\nThe following sections describe the mechanisms to encrypt customer data at\nrest.\n\nGDC Block Storage Data is Encrypted at hardware level\nwith leveraging FIPS Compliant 140-2 Self-Encrypting Drives. Encryption Keys for\nSelf Encrypting Drives are stored in an external HSM, providing FIPS 140-3\ncompliant encryption at rest storage. In addition, Block Storage also implements\nadditional software-level encryption solution, Volume Encryption (VE), that\nencrypts each underlying block storage data volume with a unique XTS-AES-256\nkey, with each volume specific key stored in an external HSM.\n\nKey management systems\n----------------------\n\n[Key management systems](/distributed-cloud/hosted/docs/latest/gdch/application/ao-user/kms/kms) (KMS) lets\nyou create your own encryption and signing keys. Using KMS, you can create,\nand delete keys. KMS is not involved with encryption at rest as described\nin this page.\n\nA root key wraps the keys, which is encrypted at rest. You use the keys to\nencrypt or sign your workloads.\n\n### Customer-managed encryption keys\n\nTo protect your data at rest, use customer-managed encryption keys (CMEK). CMEK\ngives you control over the keys that protect your data at rest in\nGDC.\n\nAll data stored within GDC is encrypted at rest with FIPS\n140-2 validated cryptographic modules by keys that Hardware Security Modules\n(HSM) protect in your GDC deployment. No setup or\nconfiguration is required.\n\nCMEKs offer the following advantages:\n\n- **Control**: You have control over the CMEK, including the ability to delete keys.\n- **Transparency**: You can audit the encryption process to ensure that your data is well-protected.\n- **Compliance**: CMEKs can help you meet compliance requirements.\n\nAnother advantage for CMEK adoption is cryptographic erasure, a\nhigh-assurance data destruction method for data spill remediation and\noff-boarding. You can delete keys out-of-band of the data they protect. A set\nof CMEKs protects all of the data in your organization that your Platform\nAdministrator can monitor, audit, and delete as needed. CMEK keys are\nencryption keys that you can manage using HSM APIs.\n\n#### CMEK supported services\n\nWhenever a user creates a CMEK supported datastore in\nGDC, such as block storage, a CMEK is automatically\ncreated on behalf of the user and becomes available to the Platform\nAdministrator to manage. Services that support CMEK rotation provide service\nspecific instructions for rotating CMEK keys. This process might require\ncopying the data to a new instance.\n\nThe following GDC services support CMEK:\n\n- Block storage: Encrypts each block storage device with a key the Platform Administrator manages.\n- Virtual machine (VM) disks.\n- Database Service: Your database instance primarily stores its data with a key the Platform Administrator manages. Backups for your database are out of scope for CMEK and encrypt with the encryption settings of your backup's storage system.\n- User container workloads: Encrypts the Kubernetes metadata, the `ETCD` cluster with a key the Platform Administrator manages.\n- Storage: Encrypts each object with a unique AES-256-GCM data encryption key wrapped by a bucket-level KMS AEAD key.\n\nEncryption at rest to secure data\n---------------------------------\n\nEncryption has the following benefits:\n\n- Ensures that if data falls into an attacker's hands, the attacker cannot read the data without also having access to the encryption keys. Even if attackers get the storage devices that contain customer data, they won't be able to understand or decrypt the data.\n- Reduces the surface of attack by cutting out the lower layers of the hardware and software stack.\n- Acts as a chokepoint as centrally managed encryption keys create a single place where it enforces access to data and prevents auditing.\n- Reduces the attack surface. For example: instead of protecting all data, businesses can focus their protection strategies on the encryption keys.\n- Provides an important privacy mechanism for you. When GDC encrypts data at rest, it limits the access that systems and engineers have to the data.\n\nCustomer data\n-------------\n\nCustomer data is data that customers or end users provide to\nGDC through the services under their account. Customer\ndata includes customer content and metadata.\n\nCustomer content is data that you generate yourself or provide to us, such as\nstored data, disk snapshots, and Identity and Access Management (IAM) policies.\nThis document focuses on default encryption at rest for your content.\n\nCustomer metadata makes up the rest of your data. Customer metadata could\ninclude auto-generated project numbers, timestamps, IP addresses, the byte size\nof an object, or the virtual machine type. GDC protects\nmetadata to a degree that is reasonable for ongoing performance and operations."]]