Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Firestore dalam mode Datastore otomatis mengenkripsi semua data sebelum ditulis ke disk.
Tidak diperlukan penyiapan atau konfigurasi, dan Anda tidak perlu mengubah cara mengakses layanan. Data didekripsi secara otomatis dan transparan saat
dibaca oleh pengguna yang diotorisasi.
Pengelolaan kunci
Dengan enkripsi sisi server, Anda dapat mengizinkan Google mengelola kunci kriptografis atas nama Anda atau menggunakan kunci enkripsi yang dikelola pelanggan (CMEK) untuk mengelola kunci sendiri.
Secara default, Google mengelola kunci kriptografis atas nama Anda menggunakan sistem
pengelolaan kunci hasil hardening yang sama dengan yang kami gunakan untuk data terenkripsi kami sendiri,
termasuk pengauditan dan kontrol akses kunci yang ketat. Data dan metadata setiap objek mode Datastore dienkripsi dan setiap kunci enkripsinya sendiri
dienkripsi dengan kumpulan kunci master keystore yang dirotasi secara rutin.
Untuk mengetahui informasi tentang cara mengelola kunci sendiri, lihat
CMEK untuk Datastore.
Enkripsi sisi klien
Enkripsi sisi server dapat digunakan bersama dengan enkripsi sisi klien.
Dalam enkripsi sisi klien, Anda mengelola kunci enkripsi Anda sendiri dan mengenkripsi data
sebelum menulisnya ke database. Dalam hal ini, data Anda
dienkripsi dua kali, sekali dengan kunci Anda dan sekali dengan kunci sisi server.
Untuk melindungi data Anda saat data berpindah melalui Internet selama operasi baca dan
tulis, kami menggunakan Transport Layer Security (TLS). Untuk mengetahui informasi selengkapnya tentang
versi TLS yang didukung, lihat Enkripsi dalam pengiriman di Google Cloud.
Langkah selanjutnya
Untuk mengetahui informasi selengkapnya tentang enkripsi dalam penyimpanan untuk Firestore dalam mode Datastore dan produk Google Cloud lainnya, lihat Enkripsi dalam Penyimpanan di Google Cloud.
[[["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-05 UTC."],[[["\u003cp\u003eFirestore in Datastore mode automatically encrypts all data before writing it to disk, without requiring any setup or configuration.\u003c/p\u003e\n"],["\u003cp\u003eServer-side encryption allows for either Google-managed cryptographic keys or customer-managed encryption keys (CMEK), providing flexibility in key management.\u003c/p\u003e\n"],["\u003cp\u003eClient-side encryption can be used in combination with server-side encryption, resulting in double encryption, but it necessitates secure management of user's own encryption keys.\u003c/p\u003e\n"],["\u003cp\u003eData in transit is protected using Transport Layer Security (TLS) during read and write operations.\u003c/p\u003e\n"],["\u003cp\u003eEach Datastore object's data and metadata are encrypted, and each encryption key is further encrypted with a regularly rotated set of keystore master keys.\u003c/p\u003e\n"]]],[],null,["# Server-Side Encryption\n\nFirestore in Datastore mode automatically encrypts all data before it is written to disk.\nThere is no setup or configuration required and no need to modify the way you\naccess the service. The data is automatically and transparently decrypted when\nread by an authorized user.\n\nKey management\n--------------\n\nWith server-side encryption, you can either let Google manage cryptographic keys on your\nbehalf or use customer-managed encryption keys (CMEK) to manage the keys\nyourself.\n\nBy default, Google manages cryptographic keys on your behalf using the same\nhardened key management systems that we use for our own encrypted data,\nincluding strict key access controls and auditing. Each Datastore mode\nobject's data and metadata is [encrypted](/security/encryption/default-encryption) and each encryption key is itself\nencrypted with a regularly rotated set of keystore master keys.\n\nFor information about managing the keys yourself, see\n[CMEK for Datastore](/datastore/docs/cmek).\n\nClient-side encryption\n----------------------\n\nServer-side encryption can be used in combination with client-side encryption.\nIn client-side encryption, you manage your own encryption keys and encrypt data\nbefore writing it to your database. In this case, your data is\nencrypted twice, once with your keys and once with the server-side keys.\n| **Warning:** Firestore in Datastore mode does not know if your data has already been encrypted client-side, nor does Datastore mode have any knowledge of your client-side encryption keys. If you use client-side encryption, you must securely manage your encryption keys.\n\nTo protect your data as it travels over the Internet during read and write\noperations, we use Transport Layer Security (TLS). For more information about\nthe supported TLS versions, see [Encryption in transit in Google Cloud](/docs/security/encryption-in-transit#user_to_google_front_end_encryption).\n\nWhat's next\n-----------\n\nFor more information about encryption at rest for Firestore in Datastore mode and\nother Google Cloud products, see\n[Encryption at Rest in Google Cloud](/security/encryption/default-encryption)."]]
