Skip to main content

πŸ“ Google Logging Log Metric Filter and Alerts for SQL Instance Configuration Changes do not exist 🟒

  • Contextual name: πŸ“ Log Metric Filter and Alerts for SQL Instance Configuration Changes do not exist 🟒
  • ID: /ce/ca/google/logging/sql-instance-configuration-changes-monitoring
  • Located in: πŸ“ Google Logging

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Logic​

Description​

Open File

Description​

It is recommended that a metric filter and alarm be established for SQL instance configuration changes.

Rationale​

Monitoring changes to SQL instance configuration changes may reduce the time needed to detect and correct misconfigurations done on the SQL server.

Below are a few of the configurable options which may the impact security posture of an SQL instance:

β€’ Enable auto backups and high availability: Misconfiguration may adversely impact business continuity, disaster recovery, and high availability
β€’ Authorize networks: Misconfiguration may increase exposure to untrusted networks

Impact​

Enabling of logging may result in your project being charged for the additional logs usage. These charges could be significant depending on the size of the organization.

Audit​

From Google Cloud Console​

Ensure the prescribed log metric is present:

  1. For each project that contains Cloud SQL instances, go to Logging/Logs-based Metrics by visiting https://console.cloud.google.com/logs/metrics.
  2. In the User-defined Metrics section, ensure that at least one metric <Log_Metric_Name> is present with the filter text:

... see more

Remediation​

Open File

Remediation​

From Google Cloud Console​

Create the prescribed Log Metric:

  1. Go to Logging/Logs-based Metrics by visiting https://console.cloud.google.com/logs/metrics and click "CREATE METRIC".

  2. Click the down arrow symbol on the Filter Bar at the rightmost corner and select Convert to Advanced Filter.

  3. Clear any text and add:

         protoPayload.methodName="cloudsql.instances.update"
  4. Click Submit Filter. Display logs appear based on the filter text entered by the user.

  5. In the Metric Editor menu on right, fill out the name field. Set Units to 1 (default) and Type to Counter. This ensures that the log metric counts the number of log entries matching the user's advanced logs query.

  6. Click Create Metric.

Create the prescribed alert policy:

  1. Identify the newly created metric under the section User-defined Metrics at https://console.cloud.google.com/logs/metrics.
  2. Click the 3-dot icon in the rightmost column for the new metric and select Create alert from Metric. A new page appears.

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
πŸ’Ό CIS GCP v3.0.0 β†’ πŸ’Ό 2.11 Ensure That the Log Metric Filter and Alerts Exist for SQL Instance Configuration Changes - Level 2 (Automated)1
πŸ’Ό Cloudaware Framework β†’ πŸ’Ό Logging and Monitoring Configuration49