​
Event Information

  • The cloudsql.instances.create event in GCP for CloudSQL indicates the creation of a new CloudSQL instance.
  • This event signifies the start of the provisioning process for a new CloudSQL database.
  • It is triggered when a user or an automated process initiates the creation of a CloudSQL instance in GCP.

​
Examples

  1. Unauthorized access: If security is impacted with cloudsql.instances.create in GCP for CloudSQL, it could potentially lead to unauthorized access to the database instance. This can occur if proper access controls and permissions are not implemented, allowing unauthorized users to create and access database instances.

  2. Data breaches: Another security impact of cloudsql.instances.create in GCP for CloudSQL is the risk of data breaches. If the database instance is not properly secured, it can be vulnerable to attacks such as SQL injection or unauthorized data access, leading to the exposure of sensitive data.

  3. Compliance violations: CloudSQL instances created without proper security measures can result in compliance violations. Depending on the industry and applicable regulations, organizations may be required to implement specific security controls to protect sensitive data. Failure to do so can result in compliance breaches and potential legal 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 in GCP CloudSQL using GCP CLI, you can follow these steps:

  1. Enable automatic backups:

    • Use the gcloud sql instances patch command to update the instance configuration.
    • Specify the --backup-start-time flag to set a specific time for backups to start.
    • Example command: gcloud sql instances patch INSTANCE_NAME --backup-start-time HH:MM

  2. Enable SSL/TLS encryption for connections:

    • Use the gcloud sql instances patch command to update the instance configuration.
    • Specify the --require-ssl flag to enforce SSL/TLS encryption for connections.
    • Example command: gcloud sql instances patch INSTANCE_NAME --require-ssl

  3. Enable VPC Service Controls:

    • Use the gcloud services vpc-peerings update command to enable VPC Service Controls.
    • Specify the --service flag to specify the service name (e.g., servicenetworking.googleapis.com).
    • Specify the --network flag to specify the VPC network name.
    • Example command: gcloud services vpc-peerings update --service=SERVICE_NAME --network=NETWORK_NAME

Note: Replace INSTANCE_NAME, HH:MM, SERVICE_NAME, and NETWORK_NAME with the appropriate values for 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.