.TH "GCLOUD_SCC_FINDINGS_UPDATE\-MARKS" 1



.SH "NAME"
.HP
gcloud scc findings update\-marks \- update Security Command Center finding's security marks



.SH "SYNOPSIS"
.HP
\f5gcloud scc findings update\-marks\fR \fIFINDING\fR [\fB\-\-location\fR=\fILOCATION\fR;\ default="global"] [\fB\-\-security\-marks\fR=[\fIKEY\fR=\fIVALUE\fR,...]] [\fB\-\-source\fR=\fISOURCE\fR;\ default="\-"] [\fB\-\-start\-time\fR=\fISTART_TIME\fR] [\fB\-\-update\-mask\fR=\fIUPDATE_MASK\fR] [\fB\-\-folder\fR=\fIFOLDER\fR\ |\ \fB\-\-organization\fR=\fIORGANIZATION\fR\ |\ \fB\-\-project\fR=\fIPROJECT\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Update Security Command Center finding's security marks.



.SH "EXAMPLES"

Selectively update security mark \f5Key1\fR with value \f5v1\fR on testFinding.
Note that other security marks on \f5testFinding\fR are untouched:

.RS 2m
$ gcloud scc findings update\-marks `testFinding` \e
    \-\-organization=123456 \-\-source=5678 \-\-security\-marks="key1=v1" \e
    \-\-update\-mask="marks.markKey1"
.RE

Update all security marks on \f5testFinding\fR, under project
\f5example\-project\fR and source \f55678\fR:

.RS 2m
$ gcloud scc findings update\-marks \e
    projects/example\-project/sources/5678/findings/testFinding \e
    \-\-security\-marks="key1=v1,key2=v2"
.RE

Update all security marks on \f5testFinding\fR, under folder \f5456\fR and
source \f55678\fR:

.RS 2m
$ gcloud scc findings update\-marks \e
    folders/456/sources/5678/findings/testFinding \e
    \-\-security\-marks="key1=v1,key2=v2"
.RE

Update all security marks on \f5testFinding\fR, under organization \f5123456\fR
and source \f55678\fR:

.RS 2m
$ gcloud scc findings update\-marks `testFinding` \e
    \-\-organization=123456 \-\-source=5678 \e
    \-\-security\-marks="key1=v1,key2=v2"
.RE

Delete all security marks on \f5testFinding\fR:

.RS 2m
$ gcloud scc findings update\-marks `testFinding` \e
    \-\-organization=123456 \-\-source=5678 \-\-security\-marks=""
.RE

Update all security marks on \f5testFinding\fR, under project
\f5example\-project\fR, source \f55678\fR and \f5location=eu\fR:

.RS 2m
$ gcloud scc findings update\-marks \e
    projects/example\-project/sources/5678/findings/testFinding \e
    \-\-security\-marks="key1=v1,key2=v2" \-\-location=eu
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fIFINDING\fR

ID of the finding or fully qualified identifier for the finding.


.RE
.sp

.SH "FLAGS"

.RS 2m
.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\-\-security\-marks\fR=[\fIKEY\fR=\fIVALUE\fR,...]

SecurityMarks resource to be passed as the request body. It's a key=value pair
separated by comma (,). For example: \-\-security\-marks="key1=val1,key2=val2".

.TP 2m
\fB\-\-source\fR=\fISOURCE\fR; default="\-"

Source id. Defaults to all sources.

.TP 2m
\fB\-\-start\-time\fR=\fISTART_TIME\fR

Time at which the updated SecurityMarks take effect. See \f5$ gcloud topic
datetimes\fR for information on supported time formats.

.TP 2m
\fB\-\-update\-mask\fR=\fIUPDATE_MASK\fR

Use update\-mask if you want to selectively update marks represented by
\-\-security\-marks flag. For example: \-\-update\-mask="marks.key1,marks.key2".
If you want to override all the marks for the given finding either skip the
update\-mask flag or provide an empty value (\-\-update\-mask '') for it.

.TP 2m

At most one of these can be specified:


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

The folder ID (e.g., 456) that contains the finding.

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

The organization ID (e.g., 123) that contains the finding.

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

The project ID (e.g., example\-project) that contains the finding.


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

These variants are also available:

.RS 2m
$ gcloud alpha scc findings update\-marks
.RE

.RS 2m
$ gcloud beta scc findings update\-marks
.RE