feat(query): implements "Beta - Logs And Alerts Missing Audit Configuration Changes" #7801
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 are no queries addressing the Terraform/gcp "google_logging_metric" and "google_monitoring_alert_policy" resources's "filter" fields. This query is meant to ensure those resources's filters properly check for admin activity and data access logs.
Quoting CIS_Google_Cloud_Platform_Foundation_Benchmark_v4.0.0 page 86: "
Admin activity and data access logs produced by cloud audit logging enable security analysis, resource change tracking, and compliance auditing. Configuring the metric filter and alerts for audit configuration changes ensures the recommended state of audit configuration is maintained so that all activities in the project are audit-able at any point in time."Additionally page 86 states the specific filter that should be present :
Proposed Changes
Developed an initial implementation for a query that ensures "Audit Configuration Changes" are accounted for by a given filter.
Based on the audit described by the CIS entry the query will flag if :
Note: there are currently issues with the search values, i could not get them to point to the "filter" field for either of the target resources in the scan results.
Tenable Reference
I submit this contribution under the Apache-2.0 license.