Enforce all incoming connections to your Cloud SQL database instances to use SSL/TLS only. If the SSL/TLS protocol is not enforced for all Cloud SQL connections, clients without a valid certificate are allowed to connect to the database.
This rule resolution is part of the Conformity Security & Compliance tool for GCP.
When Cloud SQL database connections are subjected to Man-in-the-Middle (MITM) attacks (also known as hijack attacks), the compromised database can reveal sensitive data such as user credentials, database queries and query outputs. To ensure that your data is encrypted in transit, it is strongly recommended that you enforce using the SSL/TLS protocol for all incoming connections to your Cloud SQL database instances, especially if these are using public IPs.
Audit
To determine if your Cloud SQL database instances requires all incoming connections to use SSL/TLS, perform the following actions:
Remediation / Resolution
To configure your Cloud SQL database instances to enforce SSL/TLS for all incoming connections, perform the following actions:
References
- Google Cloud Platform (GCP) Documentation
- Cloud SQL for SQL Server
- Authorizing with SSL/TLS certificates
- Configuring SSL/TLS certificates
- Managing SSL/TLS certificates
- CIS Security Documentation
- Securing Google Cloud Computing Platform
- GCP Command Line Interface (CLI) Documentation
- gcloud projects list
- gcloud sql instances list
- gcloud sql instances describe
- gcloud sql instances patch