An e-commerce platform headquartered in Japan is expanding operations into South Korea. To comply with local regulatory compliance and data sovereignty laws, all customer personally identifiable information (PII) must be stored and processed strictly within South Korean territory. Additionally, cloud service provider personnel must be prevented from accessing customer data without explicit, auditable authorization. As a Cloud Architect, which solution should you implement to satisfy these compliance and governance requirements?
- Enforce the gcp.resourceLocations Organization Policy constraint restricted to asia-northeast3 (Seoul), configure Customer-Managed Encryption Keys (CMEK) using key rings located in asia-northeast3, and enable Access Approval for the project.Cevap
- BMandate Customer-Supplied Encryption Keys (CSEK) for all storage buckets, assign primitive Owner roles to service accounts managing data pipelines, and enable Access Transparency logging.
- CGrant Project Viewer roles to administrative service accounts, configure VPC Network Peering across global projects, and rely on IAM policies alone to prevent data exfiltration to external locations.
- DEnforce the gcp.resourceLocations Organization Policy set to asia-northeast3, grant primitive Editor roles to backend workloads, and rely on Google-managed encryption keys for default storage.
Cevap
Enforce the gcp.resourceLocations Organization Policy constraint set to asia-northeast3, configure Customer-Managed Encryption Keys (CMEK) hosted in asia-northeast3, and enable Access Approval.
Combining the gcp.resourceLocations Organization Policy constraint, regional CMEK key rings in asia-northeast3, and Access Approval provides a complete compliance architecture. It locks resource creation to South Korea, guarantees customer-managed encryption within the region, and requires manual consent before Google engineers can access system data.
Adım Adım Çözüm
Anahtar Kavram
Regulatory Compliance, Data Sovereignty, and Data Governance