Control: 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', and 'all'.
Usage
Run the control in your terminal:
powerpipe control run gcp_compliance.control.sql_instance_postgresql_log_statement_database_flag_ddl
Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run gcp_compliance.control.sql_instance_postgresql_log_statement_database_flag_ddl --share
SQL
This control uses a named query:
select self_link as resource, case when database_version not like 'POSTGRES%' then 'skip' when database_flags is null or not (database_flags @> '[{"name":"log_statement"}]') then 'alarm' when database_flags @> '[{"name": "log_statement","value":"ddl"}]' then 'ok' else 'alarm' end as status, case when database_version not like 'POSTGRES%' then title || ' not a PostgreSQL database.' when database_flags is null or not (database_flags @> '[{"name":"log_statement"}]') then title || ' log_statement database flag not set.' when database_flags @> '[{"name": "log_statement","value":"ddl"}]' then title || ' log_statement database flag set to ddl.' when database_flags @> '[{"name": "log_statement","value":"mod"}]' then title || ' log_statement database flag set to mod.' when database_flags @> '[{"name": "log_statement","value":"all"}]' then title || ' log_statement database flag set to all.' when database_flags @> '[{"name": "log_statement","value":"none"}]' then title || ' log_statement database flag set to none.' end as reason , location as location, project as projectfrom gcp_sql_database_instance;