-
Notifications
You must be signed in to change notification settings - Fork 349
feat(query): implements "Beta - Logs And Alerts Missing Custom Role Changes" - Terraform/gcp #7772
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
18
commits into
master
Choose a base branch
from
AST-116618_5_2-Logging_and_Monitoring_ensure_that_the_log_metric_filter_and_alerts_exist_for_costum_role_changes
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.
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
…16618_5_2-Logging_and_Monitoring_ensure_that_the_log_metric_filter_and_alerts_exist_for_costum_role_changes
…re_that_the_log_metric_filter_and_alerts_exist_for_costum_role_changes
…re_that_the_log_metric_filter_and_alerts_exist_for_costum_role_changes
…re_that_the_log_metric_filter_and_alerts_exist_for_costum_role_changes
…og_metric_filter_and_alerts_exist_for_costum_role_changes' of https://github.com/Checkmarx/kics into AST-116618_5_2-Logging_and_Monitoring_ensure_that_the_log_metric_filter_and_alerts_exist_for_costum_role_changes
…re_that_the_log_metric_filter_and_alerts_exist_for_costum_role_changes
…re_that_the_log_metric_filter_and_alerts_exist_for_costum_role_changes
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 changes to Identity
and Access Management (IAM) role creation, deletion and updating activities.
Quoting CIS_Google_Cloud_Platform_Foundation_Benchmark_v4.0.0 page 90: "
Google Cloud IAM provides predefined roles that give granular access to specific Google Cloud Platform resources and prevent unwanted access to other resources. However, to cater to organization-specific needs, Cloud IAM also provides the ability to create custom roles. Project owners and administrators with the Organization Role Administrator role or the IAM Role Administrator role can create custom roles. Monitoring role creation, deletion and updating activities will help in identifying any over- privileged role at early stages."Additionally page 90 states the specific filter that should be present :
Proposed Changes
Developed an initial implementation for a query that ensures "Custom Role Changes" are accounted for by a given filter.
Initial implementations for this query had a more complex interpretation logic for the specific logging query language used, but that has been simplified to a regex that accepts only the specific filter with some freedom for spacing wherever possible (regex), sample negative2.tf specifically tests for "unusual" spacing.
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.