An enterprise organization is migrating a transactional analytics workload to Google Cloud. The compliance team mandates that sensitive data stored in Cloud Storage and BigQuery must be encrypted at rest using Customer-Managed Encryption Keys (CMEK) hosted in Cloud KMS. Additionally, security policy dictates strict separation of duties between key management operations and data processing tasks. Which TWO architectural configuration steps should the cloud security architect perform to satisfy these requirements? (Select TWO.)
- Grant the Cloud KMS CryptoKey Encrypter/Decrypter role on the designated KMS key to the Google-managed Service Agents for Cloud Storage and BigQuery.Answer
- Assign the Cloud KMS Admin role to the security administration team while withholding cryptographic encrypter and decrypter roles from them.Answer
- CGrant the primitive Owner IAM role on the project to the Cloud Storage and BigQuery service accounts to allow automated key creation and rotation.
- DUpload raw 256-bit AES Customer-Supplied Encryption Keys (CSEK) into Cloud KMS key rings to allow Google Cloud to automate external key rotation.
Answer
The architect must grant the Cloud KMS CryptoKey Encrypter/Decrypter role to the Google-managed Service Agents for Cloud Storage and BigQuery, and assign the Cloud KMS Admin role to the security administration team without granting encryption or decryption permissions.
Configuring CMEK for GCP services requires granting the Cloud KMS CryptoKey Encrypter/Decrypter role specifically to the Google-managed service agents for Cloud Storage and BigQuery. Simultaneously, separation of duties is achieved by granting the Cloud KMS Admin role to security personnel while intentionally withholding data decryption roles.
Step-by-Step Solution
Key Concept
CMEK Service Agent Authorization and Separation of Duties in Cloud KMS