feat(query): implements Postgres_RDS_Logging_Disabled--terraform/aws

[cx-andre-pereira]

Reason for Proposed Changes

• There is currently no query to detect whether the capturing of logs generated by Amazon RDS for PostgreSQL is properly configured.
• Without these configurations, critical visibility into query behavior and system health may be lost.

Proposed Changes

• Added the query "Postgres_RDS_Logging_Disabled".
• Added a condition to validate that the log_statement parameter is set to "all" in aws_db_parameter_group, ensuring every SQL statement is logged.
• Added a condition to check that the log_min_duration_statement parameter is set to "1"(1ms), enabling the logging of even the shortest-running queries. This helps with granular performance profiling while still ignoring near-zero-duration or trivial queries that are unlikely to provide meaningful insights.
• Case scenarios include: (same order as CxPolicy's definitions)
  • Complete lack of the parameter field / log_statement+log_min_duration_statement fields.
  • Either log_statement or log_min_duration_statement being set to the wrong value.
  • Both log_statement and log_min_duration_statement being set to the wrong value.

I submit this contribution under the Apache-2.0 license.

[github-actions]

KICS version: v2.1.11

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]

Hey André,
Let me know what you think of my suggestions please.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets 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 secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
4266022	Triggered	Generic Password	e0698da	assets/queries/cloudFormation/aws/amplify_branch_basic_auth_config_password_exposed/test/negative7.yaml	View secret
9419039	Triggered	Username Password	e0698da	assets/queries/cloudFormation/aws/amplify_branch_basic_auth_config_password_exposed/test/positive6.json	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.}

[cx-artur-ribeiro]

Nice work André, great auxiliar functions!