gcp_compliance

GCP Compliance

Enabling the log_connections setting causes each attempted connection to the server to be logged, along with successful completion of client authentication. This parameter cannot be changed after the session starts.

sql_instance_postgresql_log_connections_database_flag_on

nist_800_53_rev_5_au_12

Audit Record Generation (AU-12)

nist_800_53_rev_5_au_7

Audit Record Reduction And Report Generation (AU-7)

soc_2_2017_cc_5_2_3

CC5.2.3

soc_2_2017_cc_7_2_1

CC7.2.1

soc_2_2017_cc_7_2_2

CC7.2.2

soc_2_2017_cc_7_2_3

CC7.2.3

nist_800_53_rev_5_au_3

Content of Audit Records (AU-3)

nist_csf_v10_de_ae_3

DE.AE-3

nist_csf_v10_de_cm_1

DE.CM-1

all_controls_sql

Ensure that the 'log_connections' database flag for Cloud SQL PostgreSQL instance is set to 'on'

Run individual configuration, compliance and security controls or full compliance benchmarks for CIS, Forseti Security and CFT Scorecard across all your GCP projects using Powerpipe and Steampipe.

Apache License 2.0

steampipe-mod-gcp-compliance

Control: Ensure that the 'log_connections' database flag for Cloud SQL PostgreSQL instance is set to 'on'

Description

Usage

SQL

Tags