gcloud alpha scc findings bulk-mute - bulk mute Security Command Center findings based on a filter
gcloud alpha scc findings bulk-mute (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) [--filter=FILTER] [GCLOUD_WIDE_FLAG ...]
(ALPHA) Bulk mute Security Command Center findings based on a filter.
To bulk mute findings given organization 123 based on a filter on category that equals XSS_SCRIPTING, run:
$ gcloud alpha scc findings bulk-mute \ --organization=organizations/123 \ --filter="category=\"XSS_SCRIPTING\"" $ gcloud alpha scc findings bulk-mute --organization=123 \ --filter="category=\"XSS_SCRIPTING\""
To bulk mute findings given folder 123 based on a filter on category that equals XSS_SCRIPTING, run:
$ gcloud alpha scc findings bulk-mute --folder=folders/123 \ --filter="category=\"XSS_SCRIPTING\"" $ gcloud alpha scc findings bulk-mute --folder=123 \ --filter="category=\"XSS_SCRIPTING\""
To bulk mute findings given project 123 based on a filter on category that equals XSS_SCRIPTING, run:
$ gcloud alpha scc findings bulk-mute --project=projects/123 \ --filter="category=\"XSS_SCRIPTING\"" $ gcloud alpha scc findings bulk-mute --project=123 \ --filter="category=\"XSS_SCRIPTING\""
- Exactly one of these must be specified:
- --folder=FOLDER
Folder where the findings reside. Formatted as folders/456 or just 456.
- --organization=ORGANIZATION
Organization where the findings reside. Formatted as organizations/123 or just 123.
- --project=PROJECT
Project (id or number) where the findings reside. Formatted as projects/789 or just 789.
- --filter=FILTER
The filter string which will applied to findings being muted.
These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
This command uses the securitycenter/v1 API. The full documentation for this API can be found at: https://cloud.google.com/security-command-center
This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. This variant is also available:
$ gcloud scc findings bulk-mute