.TH "GCLOUD_ALPHA_SCC_MUTECONFIGS_CREATE" 1



.SH "NAME"
.HP
gcloud alpha scc muteconfigs create \- create a Security Command Center mute config



.SH "SYNOPSIS"
.HP
\f5gcloud alpha scc muteconfigs create\fR \fIMUTE_CONFIG\fR [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-expiry\-time\fR=\fIEXPIRY_TIME\fR] [\fB\-\-filter\fR=\fIFILTER\fR] [\fB\-\-location\fR=\fILOCATION\fR;\ default="global"] [\fB\-\-type\fR=\fITYPE\fR;\ default="static"] [\fB\-\-folder\fR=\fIFOLDER\fR\ |\ \fB\-\-organization\fR=\fIORGANIZATION\fR\ |\ \fB\-\-project\fR=\fIPROJECT\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Create a Security Command Center mute config.



.SH "EXAMPLES"

To create a mute config \f5\fItest\-mute\-config\fR\fR given organization
\f5\fI123\fR\fR with a filter on category that equals to
\f5\fIXSS_SCRIPTING\fR\fR, run:

.RS 2m
$ gcloud alpha scc muteconfigs create test\-mute\-config \e
    \-\-organization=123 \-\-description="This is a test mute config" \e
    \-\-filter="category=\e"XSS_SCRIPTING\e""
.RE

To create a mute config \f5\fItest\-mute\-config\fR\fR given folder
\f5\fI456\fR\fR with a filter on category that equals to
\f5\fIXSS_SCRIPTING\fR\fR, run:

.RS 2m
$ gcloud alpha scc muteconfigs create test\-mute\-config \e
    \-\-folder=456 \-\-description="This is a test mute config" \e
    \-\-filter="category=\e"XSS_SCRIPTING\e""
.RE

To create a mute config \f5\fItest\-mute\-config\fR\fR given project
\f5\fI789\fR\fR with a filter on category that equals to
\f5\fIXSS_SCRIPTING\fR\fR, run:

.RS 2m
$ gcloud alpha scc muteconfigs create test\-mute\-config \e
    \-\-project=789 \-\-description="This is a test mute config" \e
    \-\-filter="category=\e"XSS_SCRIPTING\e""
.RE

To create a mute config \f5\fItest\-mute\-config\fR\fR given organization
\f5\fI123\fR\fR, \f5location=eu\fR with a filter on category that equals to
\f5\fIXSS_SCRIPTING\fR\fR, run:

.RS 2m
$ gcloud alpha scc muteconfigs create test\-mute\-config \e
    \-\-organization=123 \-\-description="This is a test mute config" \e
    \-\-filter="category=\e"XSS_SCRIPTING\e"" \-\-location=eu
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fIMUTE_CONFIG\fR

ID of the mute config or the full resource name of the mute config.


.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR

The text that will be used to describe a mute configuration.

.TP 2m
\fB\-\-expiry\-time\fR=\fIEXPIRY_TIME\fR

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
\f5$ gcloud topic datetimes\fR for information on supported time formats.

.TP 2m
\fB\-\-filter\fR=\fIFILTER\fR

The filter string which will applied to findings muted by a mute configuration.

.TP 2m
\fB\-\-location\fR=\fILOCATION\fR; default="global"

When data residency controls are enabled, this attribute specifies the location
in which the resource is located and applicable. The \f5location\fR attribute
can be provided as part of the fully specified resource name or with the
\f5\-\-location\fR argument on the command line. The default location is
\f5global\fR.

NOTE: If you override the endpoint to a regional endpoint
(https://cloud.google.com/security\-command\-center/docs/reference/rest/index.html?rep_location=global#regional\-service\-endpoint)
you must specify the correct data location
(https://cloud.google.com/security\-command\-center/docs/data\-residency\-support#locations)
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 \f5global\fR AND the
request will be routed to the SCC V1 API. To use the SCC V2 API \- please
explicitly specify the flag.

.TP 2m
\fB\-\-type\fR=\fITYPE\fR; default="static"

The mute configuration type. Immutable after creation. \fITYPE\fR must be one
of: \fBstatic\fR, \fBdynamic\fR.

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-folder\fR=\fIFOLDER\fR

Folder where the mute config resides. Formatted as \f5\fIfolders/456\fR\fR or
just \f5\fI456\fR\fR.

.TP 2m
\fB\-\-organization\fR=\fIORGANIZATION\fR

Organization where the mute config resides. Formatted as
\f5\fIorganizations/123\fR\fR or just \f5\fI123\fR\fR.

.TP 2m
\fB\-\-project\fR=\fIPROJECT\fR

Project (id or number) where the mute config resides. Formatted as
\f5\fIprojects/789\fR\fR or just \f5\fI789\fR\fR.


.RE
.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "API REFERENCE"

This command uses the Security Command Center API. For more information, see
Security Command Center API.
(https://cloud.google.com/security\-command\-center/docs/reference/rest)



.SH "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:

.RS 2m
$ gcloud scc muteconfigs create
.RE