- NAME
-
- gcloud alpha scc findings set-mute - update a Security Command Center finding's mute state
- SYNOPSIS
-
-
gcloud alpha scc findings set-muteFINDING--mute=MUTE[--location=LOCATION; default="global"] [--source=SOURCE] [--folder=FOLDER|--organization=ORGANIZATION|--project=PROJECT] [GCLOUD_WIDE_FLAG …]
-
- DESCRIPTION
-
(ALPHA)Update a Security Command Center finding's mute state. - EXAMPLES
-
To update finding's mute state to
, given findingMUTEDorganizations/123/sources/456/findings/789, run:gcloud alpha scc findings set-mute 789 --organization=organizations/123 --source=456 --mute=MUTEDTo update finding's mute state to
, given findingUNMUTEDorganizations/123/sources/456/findings/789, run:gcloud alpha scc findings set-mute 789 --organization=organizations/123 --source=456 --mute=UNMUTEDTo update finding's mute state to
, given findingMUTEDfolders/123/sources/456/findings/789, run:gcloud alpha scc findings set-mute 789 --folder=folders/123 --source=456 --mute=MUTEDTo update finding's mute state to
, given findingMUTEDprojects/123/sources/456/findings/789, run:gcloud alpha scc findings set-mute 789 --project=projects/123 --source=456 --mute=MUTEDTo update finding's mute state to
, given findingMUTEDorganizations/123/sources/456/findings/789andlocation=eu, run:gcloud alpha scc findings set-mute 789 --organization=organizations/123 --source=456 --mute=MUTED --location=locations/eu - POSITIONAL ARGUMENTS
-
FINDING- ID of the finding or the full resource name of the finding.
- REQUIRED FLAGS
-
--mute=MUTE-
Desired mute state of the finding.
MUTEmust be one of:muted,unmuted,undefined.
- OPTIONAL FLAGS
-
--location=LOCATION; default="global"-
When data residency controls are enabled, this attribute specifies the location
in which the resource is located and applicable. The
locationattribute can be provided as part of the fully specified resource name or with the--locationargument on the command line. The default location isglobal.NOTE: If you override the endpoint to a regional endpoint you must specify the correct data location using this flag. The default location on this command is unrelated to the default location that is specified when data residency controls are enabled for Security Command Center.
NOTE: If no location is specified, the default location is
globalAND the request will be routed to the SCC V1 API. To use the SCC V2 API - please explicitly specify the flag. --source=SOURCE- ID of the source.
-
At most one of these can be specified:
--folder=FOLDER-
Folder where the finding resides. Formatted as
or justfolders/456.456 --organization=ORGANIZATION-
Organization where the finding resides. Formatted as
or justorganizations/123.123 --project=PROJECT-
Project (id or number) where the finding resides. Formatted as
or justprojects/789.789
- GCLOUD WIDE FLAGS
-
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 helpfor details. - API REFERENCE
- This command uses the Security Command Center API. For more information, see Security Command Center API.
- NOTES
-
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 set-mute
gcloud alpha scc findings set-mute
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-10-21 UTC.