A financial services organization hosts sensitive client datasets in Cloud Storage and BigQuery within Google Cloud. The security team must ensure that authorized analysts working from an on-premises network can access these Google Cloud APIs over a Dedicated Interconnect connection, while preventing any authorized user from exfiltrating data to external Cloud Storage buckets outside the organization's control. IAM roles have already been restricted using custom fine-grained permissions. Which security control strategy should you implement to satisfy these perimeter security and exfiltration requirements?
- Configure a VPC Service Controls perimeter encompassing the Cloud Storage and BigQuery projects, and define ingress rules allowing API requests from the designated on-premises IP range over Private Google Access.Cevap
- BRely on the existing fine-grained IAM custom roles and remove public IP addresses from all Compute Engine virtual machines in the project network.
- CEstablish VPC Network Peering between the analyst workstation VPC and a central transit VPC, relying on transitive routing across the peering connections to reach Google API endpoints.
- DAssign the primitive Viewer IAM role to all analyst accounts across the storage buckets to restrict actions to read-only operations.
Cevap
Configure a VPC Service Controls perimeter encompassing the Cloud Storage and BigQuery projects, and define ingress rules allowing API requests from the designated on-premises IP range over Private Google Access.
The correct strategy is to construct a VPC Service Controls perimeter around the storage and analytical projects while utilizing ingress policies to grant access to the specified on-premises network range over Private Google Access. VPC Service Controls effectively mitigates data exfiltration risks by constraining Google API interactions to defined boundaries, even if an authorized user attempts to copy data to external storage targets.
Adım Adım Çözüm
Anahtar Kavram
VPC Service Controls and Hybrid Perimeter Ingress