- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
By default, BigQuery encrypts data at rest by employing Envelope Encryption
using
Google managed cryptographic keys. The data is encrypted using the data encryption keys
and data encryption keys themselves are further encrypted using key encryption keys
. This is done automatically and does not require any additional input from the user. However, if you want to have greater control, customer-managed encryption keys (CMEK) can be used as an encryption key management solution for BigQuery datasets. If CMEK is used, the CMEK is used to encrypt the data encryption keys, instead of using google-managed encryption keys.
Google-managed keys are used as key encryption keys
.
For greater control over the encryption, customer-managed encryption keys (CMEK) can be used as encryption key management solution for BigQuery tables. CMEK is used to encrypt the data encryption keys instead of using google-managed encryption keys. BigQuery stores the table and CMEK association. The encryption/decryption is done automatically.
Apply the default customer-managed keys on BigQuery datasets to ensure that all new tables created in the future will be encrypted using CMEK. However, existing tables need to be updated individually to use CMEK.
Using customer-managed encryption keys (CMEK) will incur additional labor-hour investment to create, protect, and manage the keys.
Google Cloud has published a known bug affecting the ability to access and use the required BigQuery field: https://issuetracker.google.com/issues/212719457?pli=1. May not generate correct pass findings until this is remediated
Analytics
.BigQuery
.SQL Workspace
, select the project.Details
tab.Table info
, verify Customer-managed key
is present.Currently, there is no way to update the encryption of existing data in the table. The data needs to be copied to either an original table or another table. Either option requires the specification of the customer managed encryption key (CMEK).
Use the following command to copy the data to the original table and encrypt it with the CMEK. The source and the destination needs to be same when copying to the original table.
bq cp --destination_kms_key <customer_managed_key> source_dataset.source_table destination_dataset.destination_table