BigQuery data sets should specify a default customer-managed encryption key
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Description
By default, BigQuery uses envelope encryption with Google-managed cryptographic keys to encrypt the data at rest. The data is encrypted using data encryption keys, and the data encryption keys themselves are further encrypted using key encryption keys. This is seamless and does not require any additional input from the user. For greater control, customer-managed encryption keys (CMEKs) can be used as an encryption key management solution for BigQuery datasets.
Default Value
Google-managed keys are used as key encryption keys.
Rationale
By default, BigQuery uses envelope encryption with Google-managed cryptographic keys to encrypt the data at rest. The data is encrypted using data encryption keys, and the data encryption keys themselves are further encrypted using key encryption keys. This is seamless and does not require any additional input from the user.
For greater control, CMEKs can be used as an encryption key management solution for BigQuery datasets. Setting a default CMEK for a dataset ensures that any tables created in the future will use the specified CMEK, if no others are provided.
Impact
Using CMEKs incurs an additional labor-hour
investment to create, protect, and manage the keys.
Note: Google does not store your keys on its servers and cannot access your
protected data unless you provide the key. This also means that if you forget
or lose your key, there is no way for Google to recover the key or to recover
any data encrypted with the lost key.
To update the default CMEK for existing data sets, specify the default key in the EncryptionConfiguration.kmsKeyName field when calling the datasets.insert or datasets.patch methods.
References
- https://cloud.google.com/bigquery/docs/customer-managed-encryption
