feat(query): implements "Beta - Logs And Alerts Missing Project Ownership Assignment And Changes"#7804
Merged
Conversation
Contributor
…re_log_metric_filter_and_alerts_exist_for_project_ownership_assignments/changes
cx-artur-ribeiro
suggested changes
Nov 14, 2025
cx-artur-ribeiro
left a comment
Contributor
There was a problem hiding this comment.
Just quality of life changes, everything looks okay besides that!
We could also improve the variables naming (i2, x...) but I leave it to you to decide.
…_filter_and_alerts_exist_for_project_ownership_assignments/changes' of https://github.com/Checkmarx/kics into AST-116616_3_2-Logging_and_Monitoring_ensure_log_metric_filter_and_alerts_exist_for_project_ownership_assignments/changes
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 21271469 | Triggered | Generic Password | 72ca9f3 | assets/queries/terraform/azure/unrestricted_sql_server_access/test/negative6.tf | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
…re_log_metric_filter_and_alerts_exist_for_project_ownership_assignments/changes
cx-artur-ribeiro
approved these changes
Dec 5, 2025
…re_log_metric_filter_and_alerts_exist_for_project_ownership_assignments/changes
…re_log_metric_filter_and_alerts_exist_for_project_ownership_assignments/changes
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
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 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
roles/Ownerassignments.Quoting CIS_Google_Cloud_Platform_Foundation_Benchmark_v4.0.0 page 81: "
Project ownership has the highest level of privileges on a project. To avoid misuse of project resources, the project ownership assignment/change actions mentioned above should be monitored and alerted to concerned recipients. • Sending project ownership invites • Acceptance/Rejection of project ownership invite by user • Adding role\Owner to a user/service-account • Removing a user/Service account from role\Owner"Additionally page 82 states the specific filter that should be present :
Proposed Changes
Developed an initial implementation for a query that ensures "
roles/Ownerassignments" 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.