Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Cloud Build memberikan kepatuhan kunci enkripsi yang dikelola pelanggan (CMEK) dengan mengenkripsi disk persisten waktu build dengan kunci sementara yang dihasilkan untuk setiap build. Tidak
perlu konfigurasi. Kunci dibuat secara unik untuk setiap build.
Setelah build dimulai, kunci hanya dapat diakses oleh proses build
yang memerlukannya hingga 24 jam. Kemudian, kunci akan dihapus dari memori dan
dihancurkan.
Kunci tidak disimpan di mana pun, tidak dapat diakses oleh engineer atau staf dukungan Google, dan tidak dapat dipulihkan. Data yang dilindungi menggunakan kunci tersebut
tidak dapat diakses secara permanen setelah build selesai.
Bagaimana cara kerja enkripsi kunci sementara?
Cloud Build mendukung CMEK melalui penggunaan kunci sementara, sehingga
kunci tersebut sepenuhnya konsisten dan kompatibel dengan penyiapan yang mendukung CMEK.
Cloud Build melakukan hal berikut untuk memastikan disk persisten waktu build
dienkripsi dengan kunci sementara:
Cloud Build membuat kunci enkripsi acak 256-bit untuk mengenkripsi setiap persistent disk waktu build.
Cloud Build memanfaatkan fitur Kunci Enkripsi yang Disediakan Pelanggan (CSEK)
persistent disk untuk menggunakan kunci enkripsi baru ini sebagai kunci enkripsi
persistent disk.
Cloud Build akan menghancurkan kunci sementara segera setelah disk
dibuat. Kunci tidak pernah dicatat ke dalam log atau ditulis ke penyimpanan persisten apa pun dan
kini tidak dapat diambil.
Setelah build selesai, persistent disk akan dihapus, dan pada saat itu
tidak ada jejak kunci atau data persistent disk terenkripsi yang tersisa di mana pun
di infrastruktur Google.
Kapan enkripsi kunci sementara tidak berlaku?
Saat Anda membuat atau memicu build menggunakan pencerminan sumber (dan tidak menggunakan pemicu GitHub), kode sumber Anda akan disimpan di Cloud Storage atau Cloud Source Repositories. Anda memiliki kontrol penuh atas lokasi penyimpanan kode, termasuk kontrol atas enkripsinya.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-01 UTC."],[[["\u003cp\u003eCloud Build encrypts each build-time persistent disk with a unique, randomly generated 256-bit ephemeral key, ensuring CMEK compliance without requiring user configuration.\u003c/p\u003e\n"],["\u003cp\u003eThe ephemeral key is accessible only to the build processes for up to 24 hours, after which it is wiped from memory and destroyed, making it inaccessible and irretrievable.\u003c/p\u003e\n"],["\u003cp\u003eCloud Build leverages the Customer-Supplied Encryption Key (CSEK) feature to use the ephemeral key for persistent disk encryption, and then destroys the key immediately after the disk is created.\u003c/p\u003e\n"],["\u003cp\u003eUpon completion of the build, the persistent disk is deleted, leaving no traces of the key or encrypted data within Google infrastructure.\u003c/p\u003e\n"],["\u003cp\u003eSource code storage in Cloud Storage or Cloud Source Repositories, through source mirroring, does not utilize ephemeral key encryption, instead giving the user full control over the encryption settings.\u003c/p\u003e\n"]]],[],null,["# CMEK compliance in Cloud Build\n\nCloud Build provides [customer-managed encryption keys (CMEK)\ncompliance](/kms/docs/cmek#cmek_compliance) by encrypting the build-time\npersistent disk with an ephemeral key that is generated for each build. No\nconfiguration is required. The key is uniquely generated for each build.\n\nOnce a build starts, the key is accessible only to the build processes\nrequiring it for up to 24 hours. Then, the key is wiped from memory and\ndestroyed.\n\nThe key isn't retained anywhere, isn't accessible to Google engineers or support\nstaff, and can't be restored. The data that was protected using such a key is\npermanently inaccessible once the build completes.\n\nHow does the ephemeral key encryption work?\n-------------------------------------------\n\nCloud Build supports CMEK through the use of ephemeral keys, allowing\nit to be fully consistent and compatible with a CMEK-enabled setup.\n\nCloud Build does the following to ensure build-time persistent disks\nare encrypted with an ephemeral key:\n\n1. Cloud Build mints a random 256-bit encryption key\n for encrypting each build-time persistent disk.\n\n2. Cloud Build leverages the Customer-Supplied Encryption Key (CSEK)\n feature of persistent disk to use this new encryption key as a persistent\n disk encryption key.\n\n3. Cloud Build destroys the ephemeral key as soon as the disk is\n created. The key is never logged or written to any persistent storage and is\n now irretrievable.\n\n4. When the build is completed, the persistent disk is deleted, at which point\n no traces of the key nor the encrypted persistent disk data remain anywhere\n in Google infrastructure.\n\nWhen does ephemeral key encryption not apply?\n---------------------------------------------\n\nWhen you create or trigger a build using source mirroring (and not using\nGitHub triggers), your source code is stored in Cloud Storage\nor Cloud Source Repositories. You have full control over the code storage\nlocation, including control over its encryption."]]
