A global healthcare SaaS provider processing protected citizen health records for an Asia-Pacific government entity must comply with strict national data sovereignty regulations and audit requirements. The compliance mandate specifies three requirements:
1. All underlying storage data at rest and cryptographic key management boundaries must be restricted to a single specified GCP region.
2. Google support personnel must be explicitly authorized prior to viewing any customer data during administrative operations, with all access attempts fully audited.
3. Authorized service accounts and insider identities within the project must be programmatically blocked from exfiltrating sensitive datasets to unauthorized external Google Cloud Storage buckets.
Which THREE architectural controls must be implemented in Google Cloud to satisfy these compliance and data governance requirements?
- Enforce the Resource Locations organization policy (constraints/gcp.resourceLocations) at the folder level restricting resource creation to the target region, and use Customer-Managed Encryption Keys (CMEK) hosted on Cloud KMS key rings provisioned within that same region.Cevap
- Enable Access Approval and Access Transparency at the organization level to require explicit customer approval before Google engineers access data and to maintain immutable audit logs of support actions.Cevap
- Construct a VPC Service Controls perimeter around sensitive resources (such as Cloud Storage and BigQuery) to prevent data copying or exfiltration to projects outside the perimeter.Cevap
- DDeploy Customer-Supplied Encryption Keys (CSEK) for all storage buckets and manually manage raw cryptographic keys within application source code deployed on Compute Engine instances.
- EAssign primitive IAM Owner and Editor roles to the central compliance service account so that it can bypass regional resource policies during audit automated remediation.
- FRely exclusively on standard IAM roles (such as roles/storage.objectViewer) without VPC network boundary controls to restrict service accounts from sending data to external endpoints.