CIS Google Cloud Platform Foundation Benchmark v1.2.0/Cloud SQL Database Services - PostgreSQL Database/59 of 83
6.2.6Ensure that the 'log_lock_waits' database flag for Cloud SQL PostgreSQL instance is set to 'on'
Control family: Cloud SQL Database Services - PostgreSQL Database
Control description
Enabling the `log_lock_waits` flag for a PostgreSQL instance creates a log for any session waits that take longer than the alloted `deadlock_timeout` time to acquire a lock.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
This flag logs any session that waits longer than the deadlock timeout for a lock. Long lock waits slow everything down and can be a sign of a denial-of-service attempt or a badly behaved application.
Before you start
The same on every cloud, before the steps in the tabs.
- Record in the PostgreSQL configuration standard that log_lock_waits is on, so every new instance starts with it.
- Agree who investigates long lock waits.
Evidence
- The PostgreSQL configuration standard
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks set the flag on each PostgreSQL instance in Cloud SQL, then watch for instances without it with Security Command Center.
Task 1Set log_lock_waits to on on each PostgreSQL instance
- Sign in to the Google Cloud console at console.cloud.google.com and open SQL.
- Choose the PostgreSQL instance and select Edit.
- Expand Database flags (shown as Flags on some instances) and choose Add a database flag, or find the flag if it is already listed.
- Choose log_lock_waits and set it to on, then choose Done.
- Choose Save; if the console says the change restarts the instance, schedule it for a quiet period first.
- Check it: the instance Overview lists log_lock_waits with the value on under Database flags.
Task 2Keep it checked with the Security Health Analytics finding SQL_LOG_LOCK_WAITS_DISABLED
- 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_LOG_LOCK_WAITS_DISABLED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and set the flag on the instance it names.
- Check it: after the next Security Health Analytics scan, no active SQL_LOG_LOCK_WAITS_DISABLED finding remains.
Evidence
- The Overview of each PostgreSQL instance, listing log_lock_waits set to on under Database flags
- Security Command Center, with no active SQL_LOG_LOCK_WAITS_DISABLED 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.