Control: 6.2.4 Ensure 'log_statement' database flag for Cloud SQL PostgreSQL instance is set appropriately
Description
The value of log_statement flag determined the SQL statements that are logged. Valid values are:
- none
- ddl
- mod
- all
The value ddl logs all data definition statements. The value mod logs all ddl statements, plus data-modifying statements. The statements are logged after a basic parsing is done and statement type is determined, thus this does not logs statements with errors. When using extended query protocol, logging occurs after an Execute message is received and values of the Bind parameters are included.
A value of 'ddl' is recommended unless otherwise directed by your organization's logging policy.
Auditing helps in forensic analysis. If log_statement is not set to the correct value, too many statements may be logged leading to issues in finding the relevant information from the logs, or too few statements may be logged with relevant information missing from the logs. Setting log_statement to align with your organization's security and logging policies facilitates later auditing and review of database activities. This recommendation is applicable to PostgreSQL database instances.
Remediation
From Console:
- Go to the Cloud SQL Instances page in the Google Cloud Console by visiting https://console.cloud.google.com/sql/instances.
- Select the PostgreSQL instance for which you want to enable the database flag.
- Click
Edit
. - Scroll down to the
Flags
section. - To set a flag that has not been set on the instance before, click
Add item
, choose the flaglog_statement
from the drop-down menu and set appropriate value. - Click
Save
to save your changes. - Confirm your changes under
Flags
on the Overview page.
From Command Line:
- CConfigure the log_statement database flag for every Cloud SQL PosgreSQL database instance using the below command.
gcloud sql instances patch <INSTANCE_NAME> --database-flags log_statement=<ddl|mod|all|none>
Note: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign ("=").
Usage
Run the control in your terminal:
powerpipe control run gcp_compliance.control.cis_v130_6_2_4
Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run gcp_compliance.control.cis_v130_6_2_4 --share
SQL
This control uses a named query:
manual_control