- NAME
-
- gcloud scc muteconfigs create - create a Security Command Center mute config
- SYNOPSIS
-
-
gcloud scc muteconfigs create
MUTE_CONFIG
[--description
=DESCRIPTION
] [--expiry-time
=EXPIRY_TIME
] [--filter
=FILTER
] [--location
=LOCATION
; default="global"] [--type
=TYPE
; default="static"] [--folder
=FOLDER
|--organization
=ORGANIZATION
|--project
=PROJECT
] [GCLOUD_WIDE_FLAG …
]
-
- DESCRIPTION
- Create a Security Command Center mute config.
- EXAMPLES
-
To create a mute config
given organizationtest-mute-config
with a filter on category that equals to123
, run:XSS_SCRIPTING
gcloud scc muteconfigs create test-mute-config --organization=123 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\""
To create a mute config
given foldertest-mute-config
with a filter on category that equals to456
, run:XSS_SCRIPTING
gcloud scc muteconfigs create test-mute-config --folder=456 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\""
To create a mute config
given projecttest-mute-config
with a filter on category that equals to789
, run:XSS_SCRIPTING
gcloud scc muteconfigs create test-mute-config --project=789 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\""
To create a mute config
given organizationtest-mute-config
,123
location=eu
with a filter on category that equals to
, run:XSS_SCRIPTING
gcloud scc muteconfigs create test-mute-config --organization=123 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\"" --location=eu
- POSITIONAL ARGUMENTS
-
MUTE_CONFIG
- ID of the mute config or the full resource name of the mute config.
- FLAGS
-
--description
=DESCRIPTION
- The text that will be used to describe a mute configuration.
--expiry-time
=EXPIRY_TIME
-
The expiry of the mute config. Only applicable for dynamic configs. If the
expiry is set, when the config expires, it is removed from all findings. See
$ gcloud topic datetimes
for information on supported time formats. --filter
=FILTER
- The filter string which will applied to findings muted by a mute configuration.
--location
=LOCATION
; default="global"-
When data residency controls are enabled, this attribute specifies the location
in which the resource is located and applicable. The
location
attribute can be provided as part of the fully specified resource name or with the--location
argument on the command line. The default location isglobal
.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.
--type
=TYPE
; default="static"-
The mute configuration type. Immutable after creation.
TYPE
must be one of:static
,dynamic
. -
At most one of these can be specified:
--folder
=FOLDER
-
Folder where the mute config resides. Formatted as
or justfolders/456
.456
--organization
=ORGANIZATION
-
Organization where the mute config resides. Formatted as
or justorganizations/123
.123
--project
=PROJECT
-
Project (id or number) where the mute config 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 help
for details. - API REFERENCE
- This command uses the Security Command Center API. For more information, see Security Command Center API.
- NOTES
-
This variant is also available:
gcloud alpha scc muteconfigs create
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 2024-08-06 UTC.