🛡️ Google Cloud PostgreSQL Instance log_temp_files Database Flag is not set to 0🟢

• Contextual name: 🛡️ PostgreSQL Instance log_temp_files Database Flag is not set to 0🟢
• ID: /ce/ca/google/sql/postgresql-instance-log-temp-files-flag
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: COMPLIANCE_POLICY
• Policy Categories: RELIABILITY

Stats

not available

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 Google Cloud SQL Instance
  • 🔌 Google Cloud SQL Instance - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

PostgreSQL can create a temporary file for actions such as sorting, hashing, and temporary query results when these operations exceed work_mem. The log_temp_files flag controls logging of temporary file names and file size when a file is deleted. Configuring log_temp_files to 0 causes all temporary file information to be logged, while positive values log only files whose size is greater than or equal to the specified number of kilobytes. A value of -1 disables temporary file information logging.

Rationale

If all temporary files are not logged, it may be more difficult to identify potential performance issues that may be due to either poor application coding or deliberate resource starvation attempts.

Audit

From Google Cloud Console

This policy flags a Google SQL Instance as INCOMPLIANT if the log_temp_files Database Flags is not set to 0.

The Instance is marked as INAPPLICABLE if its not a PostgreSQL instance.

Default Value

By default, log_temp_files is -1.

References

... see more

Remediation

Open File

Remediation

From Google Cloud Console

1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting https://console.cloud.google.com/sql/instances.
2. Select the PostgreSQL instance for which you want to enable the database flag.
3. Click Edit.
4. Scroll down to the Flags section.
5. To set a flag that has not been set on the instance before, click Add a Database Flag, choose the flag log_temp_files from the drop-down menu, and set the value to 0.
6. Click Save.
7. Confirm the changes under Flags on the Overview page.

From Google Cloud CLI

1. Configure the log_temp_files database flag for every Cloud SQL PostgreSQL database instance using the following command.

   gcloud sql instances patch {{instance-name}} \
       --database-flags log_temp_files=0

   Note: This command will overwrite all previously set database flags. To keep those and add new ones, include the values for all flags to be 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 ("=").

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 CIS GCP v1.2.0 → 💼 6.2.15 Ensure that the 'log_temp_files' database flag for Cloud SQL PostgreSQL instance is set to '0' (on) - Level 1 (Automated)			1		no data
💼 Cloudaware Framework → 💼 Logging and Monitoring Configuration			79		no data