A renewable energy utility enterprise is building a smart-grid telemetry platform on Google Cloud. The infrastructure requires a multi-layered perimeter security model to meet strict compliance guidelines. Match each perimeter security requirement on the left with the corresponding Google Cloud security control mechanism on the right that fulfills it.
- Protect public HTTPS web application endpoints against SQL injection (SQLi), cross-site scripting (XSS), and volumetric Layer 7 denial-of-service attacks.Google Cloud Armor security policies configured with preconfigured WAF rulesets and adaptive rate limiting.
- Prevent unauthorized data exfiltration from BigQuery and Cloud Storage buckets to external Google Cloud locations, even if IAM service account keys are compromised.VPC Service Controls service perimeter restricting API access context and data egress.
- Apply organization-wide SSH access rules to VM instances dynamically based on fine-grained resource metadata rather than IP subnet ranges.Hierarchical firewall policies using secure tags attached to target virtual machine instances.
- Enable workloads in isolated private VPC subnets without external IP addresses to consume Google APIs securely over internal IP endpoints.Private Service Connect (PSC) endpoints for Google APIs.
Cevap
1 matches Google Cloud Armor security policies; 2 matches VPC Service Controls service perimeter; 3 matches Hierarchical firewall policies using secure tags; 4 matches Private Service Connect (PSC) endpoints.
Each requirement maps to its specific GCP architectural component: Google Cloud Armor inspects edge HTTP(S) traffic for WAF threats; VPC Service Controls prevents perimeter exfiltration of Google API data; Hierarchical firewall policies with secure tags apply centralized policy based on instance metadata; and Private Service Connect endpoints enable internal IP connectivity to Google APIs.
Adım Adım Çözüm
Anahtar Kavram
Perimeter Security and Access Control Mechanisms in GCP