A multinational financial processing enterprise is designing perimeter controls for its multi-tenant workload architecture on Google Cloud. Match each specific network security requirement on the left with the most appropriate Google Cloud perimeter control mechanism on the right.
- Prevent data exfiltration from managed analytics services like BigQuery and Cloud Storage to unauthorized external resources, even when authenticated with valid IAM credentials.VPC Service Controls
- Inspect incoming HTTPS traffic at the edge of Google Cloud External HTTP(S) Load Balancers to mitigate Layer 7 SQL injection and cross-site scripting (XSS) attacks.Cloud Armor Security Policies
- Enforce mandatory baseline egress network firewall rules across all VPC networks across all folders in the GCP organization without allowing project administrators to override them.Hierarchical Firewall Policies
- Enable private, unidirectionally exposed access to a third-party SaaS partner application hosted in an external VPC without establishing full VPC Network Peering.Private Service Connect
Answer
Data exfiltration prevention matches VPC Service Controls; Layer 7 HTTPS threat protection matches Cloud Armor Security Policies; Organization-level enforced network security rules match Hierarchical Firewall Policies; Private third-party service access without peering matches Private Service Connect.
Each perimeter control satisfies a distinct security layer in Google Cloud: VPC Service Controls protect API and storage service boundaries against data exfiltration; Cloud Armor provides Layer 7 WAF protections at the load balancer edge; Hierarchical Firewall Policies mandate organization-level network restrictions across the resource hierarchy; Private Service Connect provides secure, isolated service access across networks without establishing network peering.
Step-by-Step Solution
Key Concept
Google Cloud Perimeter Security & Network Isolation Controls