.TH "GCLOUD_ALPHA_SCC_SETTINGS_SERVICES_DESCRIBE" 1



.SH "NAME"
.HP
gcloud alpha scc settings services describe \- display effective service settings of Security Command Center(SCC)



.SH "SYNOPSIS"
.HP
\f5gcloud alpha scc settings services describe\fR \fB\-\-service\fR=\fISERVICE_NAME\fR [\fB\-\-folder\fR=\fIFOLDER_ID\fR\ |\ \fB\-\-organization\fR=\fIORGANIZATION_ID\fR\ |\ \fB\-\-project\fR=\fIPROJECT_ID\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Describe effective service settings of Security Command
Center(SCC).



.SH "EXAMPLES"

To describe WEB_SECURITY_SCANNER settings of project id="12345", run:

.RS 2m
$ gcloud alpha scc settings services describe \-\-project=12345 \e
    \-\-service=WEB_SECURITY_SCANNER
.RE



.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-service\fR=\fISERVICE_NAME\fR

Service name in Security Command Center. \fISERVICE_NAME\fR must be one of:
\fBcontainer\-threat\-detection\fR, \fBevent\-threat\-detection\fR,
\fBsecurity\-health\-analytics\fR, \fBvirtual\-machine\-threat\-detection\fR,
\fBweb\-security\-scanner\fR.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m

At most one of these can be specified:


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

Folder ID

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

Organization ID

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

Project ID


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