An enterprise cloud architect is designing a multi-layered security model for a multi-tenant SaaS application hosted on Google Cloud. Match each network security and perimeter requirement on the left with the most appropriate Google Cloud security mechanism on the right.
- Protect web applications behind an HTTP(S) Load Balancer against Layer 7 attacks such as SQL injection (SQLi) and Cross-Site Scripting (XSS).Cloud Armor WAF Security Policies
- Prevent authorized internal users from exfiltrating sensitive BigQuery data to unauthorized external Google Cloud storage locations or projects.VPC Service Controls Service Perimeters
- Enforce organization-wide firewall rules across multiple VPC networks using dynamic resource metadata rather than IP subnet ranges.Hierarchical Firewall Policies with Secure Tags
- Provide secure, private cross-tenant API access between VPCs without establishing full network layer IP routability or transitive peering.Private Service Connect (PSC)
Cevap
Layer 7 web attack mitigation matches Cloud Armor WAF Security Policies; BigQuery data exfiltration prevention matches VPC Service Controls Service Perimeters; Organization-wide policy enforcement via dynamic metadata matches Hierarchical Firewall Policies with Secure Tags; Private cross-VPC API access without transitive peering matches Private Service Connect (PSC).
Each security requirement aligns directly with standard Google Cloud perimeter defense products: Cloud Armor handles edge Layer 7 protection, VPC Service Controls restrict managed API data movement, Hierarchical Firewalls with Secure Tags manage organization-wide network policy based on tags, and Private Service Connect facilitates isolated cross-VPC service access.
Adım Adım Çözüm
Anahtar Kavram
Google Cloud Perimeter Security and Network Controls (Cloud Armor, VPC Service Controls, Hierarchical Firewalls, Private Service Connect)