Google Cloud Compliance ControlsGoogle Cloud SQL
Cloud SQL PostgreSQL instances should have 'log_hostname' configured appropriately
This control looks at the `log_hostname` flag on Cloud SQL PostgreSQL instances. It is a check of that single flag, and the control is named for verifying that `log_hostname` is configured appropriately on each instance it covers.
What this control checks
Checks the log_hostname flag setting on Cloud SQL PostgreSQL instances
Framework mappings
The clauses this control is mapped to in each framework.
- 6.2.8 Ensure 'log_hostname' database flag for Cloud SQL PostgreSQL instance is set appropriately
- 6.2.5 Ensure 'log_hostname' database flag for Cloud SQL PostgreSQL instance is set appropriately
Related controls
- Cloud SQL PostgreSQL instances should have 'log_min_messages' set to warning or higher
- Cloud SQL PostgreSQL instances should have 'log_planner_stats' set to 'off'
- Cloud SQL SQL Server instances should not have 'user options' configured
- Cloud SQL SQL Server instances should have '3625 (trace flag)' set to 'off'
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
sql_instance_postgresql_log_hostname_database_flag_configured - Checkov Check:
CKV_GCP_108 - Powerpipe Control:
gcp_compliance.control.sql_instance_postgresql_log_hostname_database_flag_configured
Last reviewed: 2026-10-10