An enterprise analytics team is configuring a BigQuery data warehouse to store sensitive customer interaction logs. Corporate security policy dictates that data at rest must be encrypted using Customer-Managed Encryption Keys (CMEK) managed in Cloud KMS, with automated key rotation configured every 90 days. To ensure BigQuery can encrypt new table writes and perform background re-encryption following key rotations without violating the principle of least privilege, which configuration action must the security architect perform?
- Grant the Cloud KMS CryptoKey Encrypter/Decrypter role (roles/cloudkms.cryptoKeyEncrypterDecrypter) directly to the BigQuery Service Agent service account on the designated encryption key.Cevap
- BGrant the primitive Owner role (roles/owner) to the BigQuery Service Agent on the Cloud KMS KeyRing containing the encryption key.
- CGenerate a raw 256-bit AES Customer-Supplied Encryption Key (CSEK) and pass key headers in every API call so Cloud KMS can perform automatic key rotation.
- DDefine a VPC Service Controls perimeter around Cloud KMS and BigQuery, relying on perimeter ingress rules to grant service access without assigning IAM key permissions.
Cevap
Grant the Cloud KMS CryptoKey Encrypter/Decrypter role (roles/cloudkms.cryptoKeyEncrypterDecrypter) to the BigQuery Service Agent service account on the Cloud KMS key.
Google Cloud services utilizing Customer-Managed Encryption Keys (CMEK) authenticate key access via service agents. Granting the Cloud KMS CryptoKey Encrypter/Decrypter role (roles/cloudkms.cryptoKeyEncrypterDecrypter) to the BigQuery Service Agent enables BigQuery to encrypt new data and re-encrypt existing tables upon key rotation while adhering strictly to the principle of least privilege.
Adım Adım Çözüm
Anahtar Kavram
CMEK Service Agent Authorization and Cloud KMS IAM Roles