turbot/gcp_compliance

Control: 6.6 Ensure that Cloud SQL database instances do not have public IPs

Description

It is recommended to configure Second Generation SQL instance to use private IPs instead of public IPs.

To lower the organization's attack surface, Cloud SQL databases should not have public IPs. Private IPs provide improved network security and lower latency for your application.

Remediation

This recommendation is applicable for PostgreSQL, MySQL generation 1, MySQL generation 2 and SQL Server 2017 instances.

From Console

  1. Login in to Cloud SQL Instances
  2. Select the SQL Server instance to open details page.
  3. Select the Connections tab.
  4. Deselect the Public IP checkbox.
  5. Click Save to update the instance.

From Command Line

  1. For every instance remove its public IP and assign a private IP instead:
gcloud beta sql instances patch INSTANCE_NAME --network=VPC_NETWOR_NAME --noassign-ip
  1. Confirm the changes using the following command:
gcloud sql instances describe INSTANCE_NAME

Note: By default, Cloud SQL instances have a public IP.

Usage

steampipe check gcp_compliance.control.cis_v120_6_6

SQL

This control uses a named query:

sql_instance_with_no_public_ips

Tags