.TH "GCLOUD_ALPHA_SCC_MANAGE_SERVICES_UPDATE" 1



.SH "NAME"
.HP
gcloud alpha scc manage services update \- update a Security Command Center service



.SH "SYNOPSIS"
.HP
\f5gcloud alpha scc manage services update\fR \fISERVICE_NAME\fR (\fB\-\-enablement\-state\fR=\fIENABLEMENT_STATE\fR\ \fB\-\-module\-config\-file\fR=\fIPATH_TO_FILE\fR) (\fB\-\-folder\fR=\fIFOLDER_ID\fR\ |\ \fB\-\-organization\fR=\fIORGANIZATION_ID\fR\ |\ \fB\-\-parent\fR=\fIPARENT\fR\ |\ \fB\-\-project\fR=\fIPROJECT_ID_OR_NUMBER\fR) [\fB\-\-validate\-only\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Update the enablement state of the Security Center service and its
corresponding modules for the specified folder, project or organization.



.SH "EXAMPLES"

To update a Security Center Service with name \f5sha\fR for organization 123,
run:

.RS 2m
$ gcloud alpha scc manage services update sha \e
  \-\-organization=organizations/123 \-\-enablement\-state="ENABLED"
.RE

To update a Security Center Service with name \f5sha\fR and its modules for
organization 123, run:

.RS 2m
$ gcloud alpha scc manage services update sha \e
  \-\-organization=organizations/123 \-\-enablement\-state="ENABLED" \e
  \-\-module\-config\-file=module_config.yaml
.RE

To validate an update of Security Center Service with name \f5sha\fR and its
modules for organization 123, run:

.RS 2m
$ gcloud alpha scc manage services update sha \e
  \-\-organization=organizations/123 \-\-enablement\-state="ENABLED" \e
  \-\-module\-config\-file=module_config.yaml \-\-validate\-only
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fISERVICE_NAME\fR

The service name, provided either in lowercase hyphenated form (e.g.
security\-health\-analytics), or in abbreviated form (e.g. sha) if applicable.

The list of supported services is:

.RS 2m
.IP "\(em" 2m
security\-health\-analytics (can be abbreviated as sha)
.RE
.sp

.RS 2m
.IP "\(em" 2m
event\-threat\-detection (can be abbreviated as etd)
.RE
.sp

.RS 2m
.IP "\(em" 2m
container\-threat\-detection (can be abbreviated as ctd)
.RE
.sp

.RS 2m
.IP "\(em" 2m
vm\-threat\-detection (can be abbreviated as vmtd)
.RE
.sp

.RS 2m
.IP "\(em" 2m
web\-security\-scanner (can be abbreviated as wss)
.RE
.sp

.RS 2m
.IP "\(em" 2m
vm\-threat\-detection\-aws (can be abbreviated as vmtd\-aws)
.RE
.sp

.RS 2m
.IP "\(em" 2m
cloud\-run\-threat\-detection (can be abbreviated as crtd)
.RE
.sp

.RS 2m
.IP "\(em" 2m
vm\-manager (can be abbreviated as vmm)
.RE
.sp

.RS 2m
.IP "\(em" 2m
ec2\-vulnerability\-assessment (can be abbreviated as ec2\-va)
.RE
.sp

.RS 2m
.IP "\(em" 2m
gce\-vulnerability\-assessment (can be abbreviated as gce\-va)
.RE
.sp

.RS 2m
.IP "\(em" 2m
azure\-vulnerability\-assessment (can be abbreviated as azure\-va)
.RE
.sp

.RS 2m
.IP "\(em" 2m
notebook\-security\-scanner (can be abbreviated as nss)
.RE
.sp


.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m

At least one of these must be specified:


.RS 2m
.TP 2m
\fB\-\-enablement\-state\fR=\fIENABLEMENT_STATE\fR

Sets the enablement state of the Security Center service. Valid options are
ENABLED, DISABLED, OR INHERITED. The INHERITED state is only valid when setting
the enablement state at the project or folder level.

.TP 2m
\fB\-\-module\-config\-file\fR=\fIPATH_TO_FILE\fR

Path to a JSON or YAML file that contains the module config to set for the given
module and service. Use a full or relative path to a local file containing the
value of module_config_file.

.RE
.sp
.TP 2m

Exactly one of these must be specified:


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

Folder associated with the custom module.

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

Organization associated with the custom module.

.TP 2m
\fB\-\-parent\fR=\fIPARENT\fR

Parent associated with the custom module. Can be one of organizations/<id>,
projects/<id or name>, folders/<id>

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

Project associated with the custom module.


.RE
.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-validate\-only\fR

If present, the request is validated (including IAM checks) but no action is
taken.


.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 "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 manage services update
.RE