Google Cloud Dataproc clusters with public IP addresses are directly accessible from the internet, creating an expanded attack surface that could be exploited by malicious actors. When internal_ip_only is set to false or omitted, clusters receive both internal and external IP addresses, potentially exposing sensitive data processing operations and administrative interfaces to unauthorized access.
Secure configuration requires setting internal_ip_only to true as shown in this example:
resource"google_dataproc_cluster""good_example"{name="good-cluster"region="us-central1"cluster_config{gce_cluster_config{internal_ip_only=true # ✅ Private cluster (no public IP)
}}}
Non-Compliant Code Examples
resource"google_dataproc_cluster""bad_example"{name="bad-cluster"region="us-central1"cluster_config{gce_cluster_config{internal_ip_only=false # ❌ Public IP enabled
}}}
1
2
rulesets:- Terraform / GCP # Rules to enforce / GCP.
맞춤형 데모 요청
Datadog 시작하기
Ask AI
AI-generated responses may be inaccurate. Verify important info.