feat(query): implements "Beta - SQL DB Instance With Unrecommended Logging Threshold"

[cx-andre-pereira]

Reason for Proposed Changes

• Currently there is no query to ensure that a "google_sql_database_instance" resource with a "POSTGRES" based "database_version" has the 'log_min_messages' flag set to the severity threshold of "WARNING" or higher.

• Quoting CIS_Google_Cloud_Platform_Foundation_Benchmark_v4.0.0 page 229: "Auditing helps in troubleshooting operational problems and also permits forensic analysis. If log_min_messages is not set to the correct value, messages may not be classified as error messages appropriately. Setting the threshold to 'Warning' will log messages for the most needed error messages."

Proposed Changes

• Implemented the missing query.
• The query will flag for a specific instance : (all after ensuring "database_version" is POSTGRES based (possible values list))
  • Setting the "log_min_messages" flag to a value that is not warning or higher: "WARNING"|"ERROR"|"LOG"|"FATAL"|"PANIC" (default value is ERROR)

Tenable reference

I submit this contribution under the Apache-2.0 license.

[github-actions]

KICS version: v2.1.13

Category Results CRITICAL 0 HIGH 0 MEDIUM 0 LOW 0 INFO 0 TRACE 0 TOTAL 0	Metric Values Files scanned 1 Files parsed 1 Files failed to scan 0 Total executed queries 47 Queries failed to execute 0 Execution time 0

[cx-artur-ribeiro]

Only a quality of life change, if you agree with my suggestion. Rather than that, looks good to me.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
21271469	Triggered	Generic Password	45d88e7	assets/queries/terraform/azure/unrestricted_sql_server_access/test/negative4.tf	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}