CIS Google Cloud Platform Foundation Benchmark v1.2.0/Cloud SQL Database Services - PostgreSQL Database/55 of 83
6.2.2Ensure 'log_error_verbosity' database flag for Cloud SQL PostgreSQL instance is set to 'DEFAULT' or stricter
Control family: Cloud SQL Database Services - PostgreSQL Database
Control description
The `log_error_verbosity` flag controls the verbosity/details of messages logged. Valid values are:
- `TERSE`
- `DEFAULT`
- `VERBOSE`
`TERSE` excludes the logging of `DETAIL`, `HINT`, `QUERY`, and `CONTEXT` error information.
`VERBOSE` output includes the `SQLSTATE` error code, source code file name, function name, and line number that generated the error.
Ensure an appropriate value is set to 'DEFAULT' or stricter.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
This flag sets how much detail goes into each logged error. Too little (terse) leaves out the context you need to investigate; default keeps enough without flooding the log. Choose default, or verbose if your logging policy asks for more.
Before you start
The same on every cloud, before the steps in the tabs.
- Record in the PostgreSQL configuration standard the log_error_verbosity value (default, or verbose if your logging policy asks), so every new instance starts with it.
- Check the extra log volume is affordable if you choose verbose.
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_error_verbosity to default 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_error_verbosity and set it to default, 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_error_verbosity with the value default under Database flags.
Task 2Keep it checked with the Security Health Analytics finding SQL_LOG_ERROR_VERBOSITY
- 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_ERROR_VERBOSITY 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_ERROR_VERBOSITY finding remains.
Evidence
- The Overview of each PostgreSQL instance, listing log_error_verbosity set to default under Database flags
- Security Command Center, with no active SQL_LOG_ERROR_VERBOSITY 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.