CIS Google Cloud Platform Foundation Benchmark v1.2.0/Logging and Monitoring/26 of 83
2.11Ensure that the log metric filter and alerts exist for SQL instance configuration changes
Control family: Logging and Monitoring
Control description
It is recommended that a metric filter and alarm be established for SQL instance configuration changes.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Changes to a Cloud SQL instance's settings can switch off SSL, open it to new networks or turn off backups. An alert on instance updates means each change is seen and checked against a request.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree who receives these alerts, how quickly they respond and how they record what they found.
- Decide which projects to cover: every project, or the project that holds an organization-wide log sink (2.2), since a logs-based metric only counts the logs in its own project.
Evidence
- The alert routing and the response notes for alerts raised during the period
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks create a logs-based metric in Cloud Logging that counts Cloud SQL instance changes, alert on it in Cloud Monitoring, and confirm with Security Command Center.
Task 1Count the changes with a logs-based metric
- Sign in to the Google Cloud console at console.cloud.google.com and pick the project to monitor.
- Open Logging > Log-based Metrics and choose Create metric.
- Under Metric type, select Counter.
- Under Details, enter sql-instance-changes as the Log-based metric name, add a short description and set Units to 1.
- Under Filter selection, replace the text in the Build filter box with this filter, exactly: protoPayload.methodName="cloudsql.instances.update"
- Choose Create metric.
- Check it: the metric appears under User-defined metrics.
Task 2Alert the security team when it happens
- On Log-based Metrics, under User-defined metrics, find sql-instance-changes, open its More menu and choose Create alert from metric.
- Choose Next, keep the threshold so a single matching entry triggers the alert, and enter a Condition name.
- Choose Next, open Notification channels, select the security team's channel and choose OK (add an email or chat channel first under Monitoring > Alerting > Edit notification channels if there is none).
- Enter an Alert name such as sql-instance-changes-alert, and choose Create policy.
- Check it: change a harmless setting, such as a label, on a test instance in the same project, and confirm the notification arrives.
Task 3Keep it checked with the Security Health Analytics finding SQL_INSTANCE_NOT_MONITORED
- Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
- In the query editor, filter on category SQL_INSTANCE_NOT_MONITORED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and create the metric and alert in the project it names.
- Check it: after the next Security Health Analytics scan, no active SQL_INSTANCE_NOT_MONITORED finding remains.
Evidence
- Logging > Log-based Metrics, showing sql-instance-changes with its filter
- Monitoring > Alerting, showing the sql-instance-changes-alert policy and its notification channel
- Security Command Center, with no active SQL_INSTANCE_NOT_MONITORED finding
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.