​
Event Information

  1. The cloudsql.instances.addServerCa event in GCP for CloudSQL indicates that a new server certificate authority (CA) has been added to the CloudSQL instance.
  2. This event typically occurs when there is a need to update or rotate the server CA for enhanced security or compliance requirements.
  3. The addition of a new server CA ensures that client connections to the CloudSQL instance are secure and trusted, as the CA is responsible for issuing and managing digital certificates.

​
Examples

  1. Unauthorized access: If the security of the CloudSQL instance is impacted, it could potentially lead to unauthorized access to the database. This can result in sensitive data being exposed or manipulated by unauthorized individuals or entities.

  2. Data breaches: A compromised security configuration for CloudSQL instances can increase the risk of data breaches. This can occur if an attacker gains access to the database and exfiltrates sensitive information, such as customer data, financial records, or intellectual property.

  3. Compliance violations: Inadequate security measures for CloudSQL instances can lead to compliance violations. Organizations that handle sensitive data, such as personally identifiable information (PII) or protected health information (PHI), must adhere to specific regulations and standards. A security breach in CloudSQL can result in non-compliance with these regulations, leading to legal and financial consequences.

​
Remediation

​
Using Console

  1. Enable automatic backups:
  • Go to the GCP Console and navigate to the Cloud SQL instances page.
  • Select the instance for which you want to enable automatic backups.
  • Click on the “Edit” button.
  • Scroll down to the “Backup” section and check the box next to “Automated backups”.
  • Set the desired backup retention period.
  • Click on the “Save” button to apply the changes.
  1. Enable SSL/TLS encryption for connections:
  • Go to the GCP Console and navigate to the Cloud SQL instances page.
  • Select the instance for which you want to enable SSL/TLS encryption.
  • Click on the “Edit” button.
  • Scroll down to the “Connections” section and check the box next to “Require SSL”.
  • Choose the appropriate SSL/TLS certificate option.
  • Click on the “Save” button to apply the changes.
  1. Enable VPC Service Controls:
  • Go to the GCP Console and navigate to the VPC Service Controls page.
  • Click on the “Create Perimeter” button.
  • Provide a name and description for the perimeter.
  • Select the project and location where the Cloud SQL instance is located.
  • Add the Cloud SQL API to the list of services allowed within the perimeter.
  • Configure the desired access levels and conditions.
  • Click on the “Create” button to create the perimeter.
  • Associate the perimeter with the Cloud SQL instance by going to the Cloud SQL instances page, selecting the instance, clicking on the “Edit” button, and selecting the perimeter from the “VPC Service Controls” section.
  • Click on the “Save” button to apply the changes.

​
Using CLI

To remediate the issues mentioned in the previous response for GCP CloudSQL using GCP CLI, you can follow these steps:

  1. Enable automatic backups:

    • Use the following command to enable automatic backups for a CloudSQL instance: 
      gcloud sql instances patch INSTANCE_NAME --backup-start-time START_TIME
      Replace INSTANCE_NAME with the name of your CloudSQL instance and START_TIME with the desired backup start time.

  2. Configure SSL/TLS encryption:

    • Use the following command to configure SSL/TLS encryption for a CloudSQL instance: 
      gcloud sql instances patch INSTANCE_NAME --require-ssl
      Replace INSTANCE_NAME with the name of your CloudSQL instance.

  3. Enable VPC Service Controls:

    • Use the following command to enable VPC Service Controls for a CloudSQL instance: 
      gcloud beta sql instances update INSTANCE_NAME --enable-vpc-service-controls --network NETWORK_NAME --subnet SUBNET_NAME
      Replace INSTANCE_NAME with the name of your CloudSQL instance, NETWORK_NAME with the name of your VPC network, and SUBNET_NAME with the name of your subnet.

Please note that these commands assume you have the necessary permissions to make changes to the CloudSQL instances. Make sure to replace the placeholders with the appropriate values specific to your environment.

​
Using Python

To remediate the issues mentioned in the previous response for GCP CloudSQL using Python, you can follow these steps:

  1. Enable automatic backups:
    • Use the googleapiclient library to interact with the Cloud SQL API.
    • Use the instances().get() method to retrieve the current configuration of the Cloud SQL instance.
    • Set the backupConfiguration.enabled field to True to enable automatic backups.
    • Use the instances().update() method to update the Cloud SQL instance with the new configuration.
from googleapiclient import discovery
from oauth2client.client import GoogleCredentials

credentials = GoogleCredentials.get_application_default()
service = discovery.build('sqladmin', 'v1beta4', credentials=credentials)

project_id = 'your-project-id'
instance_name = 'your-instance-name'

instance = service.instances().get(project=project_id, instance=instance_name).execute()
instance['settings']['backupConfiguration']['enabled'] = True

service.instances().update(project=project_id, instance=instance_name, body=instance).execute()
  1. Enable SSL/TLS encryption:
    • Use the googleapiclient library to interact with the Cloud SQL API.
    • Use the instances().get() method to retrieve the current configuration of the Cloud SQL instance.
    • Set the settings.ipConfiguration.requireSsl field to True to enforce SSL/TLS encryption.
    • Use the instances().update() method to update the Cloud SQL instance with the new configuration.
from googleapiclient import discovery
from oauth2client.client import GoogleCredentials

credentials = GoogleCredentials.get_application_default()
service = discovery.build('sqladmin', 'v1beta4', credentials=credentials)

project_id = 'your-project-id'
instance_name = 'your-instance-name'

instance = service.instances().get(project=project_id, instance=instance_name).execute()
instance['settings']['ipConfiguration']['requireSsl'] = True

service.instances().update(project=project_id, instance=instance_name, body=instance).execute()
  1. Enable VPC Service Controls:
    • Use the googleapiclient library to interact with the Access Context Manager API.
    • Use the accessPolicies().get() method to retrieve the current configuration of the access policy.
    • Set the servicePerimeters[].resources[].services[].vpcAccessibleServices[].enableRestriction field to True for Cloud SQL.
    • Use the accessPolicies().update() method to update the access policy with the new configuration.
from googleapiclient import discovery
from oauth2client.client import GoogleCredentials

credentials = GoogleCredentials.get_application_default()
service = discovery.build('accesscontextmanager', 'v1', credentials=credentials)

access_policy_name = 'your-access-policy-name'
service_perimeter_name = 'your-service-perimeter-name'

access_policy = service.accessPolicies().get(name=access_policy_name).execute()
for service_perimeter in access_policy['servicePerimeters']:
    if service_perimeter['name'] == service_perimeter_name:
        for resource in service_perimeter['resources']:
            if resource['service'] == 'sqladmin.googleapis.com':
                resource['vpcAccessibleServices'][0]['enableRestriction'] = True

service.accessPolicies().update(name=access_policy_name, body=access_policy).execute()

Please note that you need to replace 'your-project-id', 'your-instance-name', 'your-access-policy-name', and 'your-service-perimeter-name' with the actual values specific to your environment.