-
Notifications
You must be signed in to change notification settings - Fork 349
feat(query): implements "Beta - SQL DB Instance Without Connections Logging" #7779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
cx-andre-pereira
wants to merge
8
commits into
master
Choose a base branch
from
AST-116624_11_6.2_PostgreSQL_Database_ensure_that_the_'log_connections'_database_flag_for_cloud_sql_postgresql_instance_is_set_to_on
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+243
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cx-artur-ribeiro
previously approved these changes
Oct 27, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…re_that_the_'log_connections'_database_flag_for_cloud_sql_postgresql_instance_is_set_to_on
…16624_11_6.2_PostgreSQL_Database_ensure_that_the_'log_connections'_database_flag_for_cloud_sql_postgresql_instance_is_set_to_on
cx-artur-ribeiro
approved these changes
Oct 31, 2025
…re_that_the_'log_connections'_database_flag_for_cloud_sql_postgresql_instance_is_set_to_on
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.








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_connections' flag enabled.
Quoting CIS_Google_Cloud_Platform_Foundation_Benchmark_v4.0.0 page 220: "
PostgreSQL does not log attempted connections by default. Enabling the log_connections setting will create log entries for each attempted connection as well as successful completion of client authentication which can be useful in troubleshooting issues and to determine any unusual connection attempts to the server."Proposed Changes
Implemented the missing query.
The query will flag for 4 separate instances : (all after ensuring "database_version" is POSTGRES based (possible values list))
Tenable reference
I submit this contribution under the Apache-2.0 license.