An enterprise logistics company plans to store sensitive customer shipment records in Cloud Storage and analyze them using BigQuery. Security compliance mandates that the data must be protected at rest using Customer-Managed Encryption Keys (CMEK) managed via Cloud KMS. The security team requires strict adherence to least privilege, explicit separation of duties, and continuous compliance automation without giving service accounts administrative key control. Which TWO architectural design decisions and IAM configurations should you implement to meet these requirements?
- Grant the Cloud KMS CryptoKey Encrypter/Decrypter role on the specific Cloud KMS key to the service agents for Cloud Storage and BigQuery.Answer
- Enable automated key rotation schedules on the Cloud KMS CryptoKey used by Cloud Storage and BigQuery.Answer
- CAssign the primitive Owner role to the Cloud Storage service account to permit dynamic generation and management of Customer-Supplied Encryption Keys (CSEK).
- DConfigure Customer-Supplied Encryption Keys (CSEK) for BigQuery to satisfy automated key lifecycle and rotation governance directly within Google Cloud.
Answer
Grant the Cloud KMS CryptoKey Encrypter/Decrypter role specifically to the GCP service agents for Cloud Storage and BigQuery, and enable automated key rotation schedules on the Cloud KMS key.
Configuring CMEK via Cloud KMS with automated key rotation and granting the Cloud KMS CryptoKey Encrypter/Decrypter role to service agents fulfills all enterprise compliance requirements for key management, separation of duties, and least privilege access.
Step-by-Step Solution
Key Concept
Customer-Managed Encryption Keys (CMEK) and IAM Separation of Duties in Cloud KMS