An enterprise architecture team is designing a perimeter security strategy for an internal analytics application processing sensitive records across multiple Google Cloud projects. Authorized analysts execute queries in Project A against BigQuery datasets hosted in Project B. The security compliance team requires that data exfiltration to unauthorized Google Cloud storage resources or non-approved GCP projects be strictly prevented, even if an analyst possesses elevated IAM administrative privileges. The analysts must maintain seamless ability to query BigQuery datasets spanning both Project A and Project B. Which perimeter control architecture should the Cloud Architect recommend?
- Define a VPC Service Controls service perimeter that includes both Project A and Project B, and restrict the BigQuery API within the perimeter.Answer
- BApply fine-grained IAM custom roles across Project A and Project B, explicitly revoking Cloud Storage object creation permissions from all analyst identities.
- CEstablish VPC Network Peering between Project A and Project B, routing all BigQuery API traffic through a central hub VPC inspection appliance using transitive routing.
- DGrant primitive Viewer permissions to analysts on Project B while removing Owner and Editor roles to prevent bulk export functionality.
Answer
Define a VPC Service Controls service perimeter that includes both Project A and Project B, and restrict the BigQuery API within the perimeter.
Defining a VPC Service Controls perimeter around both Project A and Project B with the BigQuery API restricted effectively creates a cryptographic and network boundary. This permits communication between the two enclosed projects while preventing data exfiltration to any project or storage bucket outside the perimeter, even if an identity possesses administrative IAM privileges.
Step-by-Step Solution
Key Concept
VPC Service Controls Perimeter Defense and Data Exfiltration Prevention
Estimated Time:2m 0s