Instance IP assignment is not set to private Affecting Compute Engine service in Google
CCSS (Common Configuration Scoring System) is a set of measures used to determine the severity of the rule.
Each rule is associated with a high-level category. For example IAM, Container, Monitoring, Logging, Network, etc.
Is your environment affected by this misconfiguration?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CC-00716
- creditSnyk Research Team
Description
Setting the instance IP assignment to private ensures that the instance is assigned a private IP address, which improves network security by preventing direct access from the internet. This reduces the risk of unauthorized access and potential attacks on the instance. By configuring the instance IP assignment to private, the instance will only be accessible within the private network, providing an additional layer of protection.
How to fix?
Create a google_compute_instance resource with a network_interface block (optionally configure the attribute network_ip within it). However, do not create a access_config block within the network_interface block.
Example Configuration
resource "google_compute_instance" "default" {
name = "default"
machine_type = "e2-medium"
zone = "us-central1-a"
boot_disk {
initialize_params {
image = "debian-cloud/debian-11"
}
}
network_interface {
network = "default"
}
}