HEX
Server: Apache/2.4.65 (Ubuntu)
System: Linux ielts-store-v2 6.8.0-1036-gcp #38~22.04.1-Ubuntu SMP Thu Aug 14 01:19:18 UTC 2025 x86_64
User: root (0)
PHP: 7.2.34-54+ubuntu20.04.1+deb.sury.org+1
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
Upload Files
File: //snap/google-cloud-cli/current/help/man/man1/gcloud_scc_findings_list.1
.TH "GCLOUD_SCC_FINDINGS_LIST" 1



.SH "NAME"
.HP
gcloud scc findings list \- list an organization or source's findings



.SH "SYNOPSIS"
.HP
\f5gcloud scc findings list\fR [\fIPARENT\fR] [\fB\-\-compare\-duration\fR=\fICOMPARE_DURATION\fR] [\fB\-\-field\-mask\fR=\fIFIELD_MASK\fR] [\fB\-\-location\fR=\fILOCATION\fR;\ default="global"] [\fB\-\-order\-by\fR=\fIORDER_BY\fR] [\fB\-\-page\-token\fR=\fIPAGE_TOKEN\fR] [\fB\-\-read\-time\fR=\fIREAD_TIME\fR] [\fB\-\-source\fR=\fISOURCE\fR;\ default="\-"] [\fB\-\-folder\fR=\fIFOLDER\fR\ |\ \fB\-\-organization\fR=\fIORGANIZATION\fR\ |\ \fB\-\-project\fR=\fIPROJECT\fR] [\fB\-\-filter\fR=\fIEXPRESSION\fR] [\fB\-\-limit\fR=\fILIMIT\fR] [\fB\-\-page\-size\fR=\fIPAGE_SIZE\fR] [\fB\-\-sort\-by\fR=[\fIFIELD\fR,...]] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

List an organization or source's findings. To list across all sources provide a
\'\-' as the source id.



.SH "EXAMPLES"

List all ACTIVE findings under organization \f5123456\fR across all sources:

.RS 2m
$ gcloud scc findings list 123456 \-\-filter="state=\e"ACTIVE\e""
.RE

List all ACTIVE findings under project \f5abc\fR across all sources:

.RS 2m
$ gcloud scc findings list projects/abc \-\-filter="state=\e"ACTIVE\e""
.RE

List all ACTIVE findings under folder \f5456\fR across all sources:

.RS 2m
$ gcloud scc findings list folders/456 \-\-filter="state=\e"ACTIVE\e""
.RE

List all ACTIVE findings under organization \f5123456\fR and source \f55678\fR:

.RS 2m
$ gcloud scc findings list 123456 \-\-source=5678 \e
    \-\-filter="state=\e"ACTIVE\e""
.RE

Only list category and resource_name of all ACTIVE findings under organization
\f5123456\fR and source \f55678\fR:

.RS 2m
$ gcloud scc findings list 123456 \-\-source=5678 \e
    \-\-filter="state=\e"ACTIVE\e"" \e
\-\-field\-mask="finding.category,finding.resource_name"
.RE

List all ACTIVE findings of XSS category/type, under organization \f5123456\fR
and source \f55678\fR:

.RS 2m
$ gcloud scc findings list 123456 \-\-source=5678 \e
    \-\-filter="state=\e"ACTIVE\e" AND category=\e"XSS\e""
.RE

List all findings attached to a particular resource under organization
\f5123456\fR:

.RS 2m
$ gcloud scc findings list 123456 \e
    \-\-filter="resource_name=\e"//container.googleapis.com/projects/\e
pid/zones/zone\-id/clusters/cluster\-id\e""
.RE

List all ACTIVE findings that took place on \f52019\-01\-01T01:00:00 GMT\fR
time, under organization \f5123456\fR:

.RS 2m
$ gcloud scc findings list 123456 \-\-filter="state=\e"ACTIVE\e" AND \e
    event_time > 1546304400000""
.RE

List all findings under organization \f5123456\fR across all sources and
\f5location=eu\fR:

.RS 2m
$ gcloud scc findings list 123456 \-\-location=eu
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Parent resource \- parent organization, folder, or project in the Google Cloud
resource hierarchy to be used for the \f5gcloud scc\fR command. Specify the
argument as either [RESOURCE_TYPE/RESOURCE_ID] or [RESOURCE_ID], as shown in the
preceding examples. This represents a Cloud resource.


.RS 2m
.TP 2m
[\fIPARENT\fR]

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

To set the \f5parent\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5parent\fR on the command line;
.IP "\(bu" 2m
Set the parent property in configuration using \f5gcloud config set
scc/parent\fR if it is not specified in command line.
.RE
.sp


.RE
.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-compare\-duration\fR=\fICOMPARE_DURATION\fR

(DEPRECATED) When compare_duration is set, the result's "state_change" attribute
is updated to indicate whether the finding had its state changed, the finding's
state remained unchanged, or if the finding was added during the
compare_duration period of time that precedes the read_time. This is the time
between (read_time \- compare_duration) and read_time. The state_change value is
derived based on the presence and state of the finding at the two points in
time. Intermediate state changes between the two times don't affect the result.
For example, the results aren't affected if the finding is made inactive and
then active again. Possible "state_change" values when compare_duration is
specified:

.RS 2m
.IP "\(em" 2m
\'CHANGED': indicates that the finding was present at the start of
compare_duration, but changed its state at read_time.
.RE
.sp

.RS 2m
.IP "\(em" 2m
\'UNCHANGED': indicates that the finding was present at the start of
compare_duration and did not change state at read_time.
.RE
.sp

.RS 2m
.IP "\(em" 2m
\'ADDED': indicates that the finding was not present at the start of
compare_duration, but was present at read_time.
.RE
.sp

.RS 2m
.IP "\(em" 2m
\'REMOVED': indicates that the finding was present at the start of
compare_duration, but was not present at read_time.
.RE
.sp

.RS 2m
If compare_duration is not specified, then the only possible
state_change is 'UNUSED', which will be the state_change set for all
findings present at read_time. If this field is set then 'state_change'
must be a specified field in 'group_by'. See $ gcloud topic datetimes
for information on supported duration formats.
.RE

The \-\-compare\-duration option is deprecated. For more information, see the
deprecation notice
(https://cloud.google.com/security\-command\-center/docs/release\-notes#April_15_2024)
on the SCC release notes page.

.TP 2m
\fB\-\-field\-mask\fR=\fIFIELD_MASK\fR

Field mask to specify the finding fields listed in the response. An empty field
mask will list all fields. For example:
\-\-field\-mask="finding.category,finding.resource_name" will only output
category and resource_name for the findings in addition to default attributes.
Notice the difference between hyphens (\-) used with flags v/s camel case used
in field masks. An empty or missing field mask will list all fields.

.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\-\-order\-by\fR=\fIORDER_BY\fR

Expression that defines what fields and order to use for sorting. String value
should follow SQL syntax: comma separated list of fields. For example:
"name,resource_properties.a_property". The default sorting order is ascending.
To specify descending order for a field, a suffix " desc" should be appended to
the field name. For example: \-\-order\-by="name
desc,source_properties.a_property" will order by name in descending order while
source_properties.a_property in ascending order.

.TP 2m
\fB\-\-page\-token\fR=\fIPAGE_TOKEN\fR

Response objects will return a non\-null value for page\-token to indicate that
there is at least one additional page of data. User can either directly request
that page by specifying the page\-token explicitly or let gcloud fetch
one\-page\-at\-a\-time.

.TP 2m
\fB\-\-read\-time\fR=\fIREAD_TIME\fR

(DEPRECATED) Time used as a reference point when filtering. Absence of this
field will default to the API's version of NOW. See $ gcloud topic datetimes for
information on supported time formats.

The \-\-read\-time option is deprecated. For more information, see the
deprecation notice
(https://cloud.google.com/security\-command\-center/docs/release\-notes#April_15_2024)
on the SCC release notes page.

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

Source id. Defaults to all sources.

.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 "LIST COMMAND FLAGS"

.RS 2m
.TP 2m
\fB\-\-filter\fR=\fIEXPRESSION\fR

Apply a Boolean filter \fIEXPRESSION\fR to each resource item to be listed. If
the expression evaluates \f5True\fR, then that item is listed. For more details
and examples of filter expressions, run $ gcloud topic filters. This flag
interacts with other flags that are applied in this order: \fB\-\-flatten\fR,
\fB\-\-sort\-by\fR, \fB\-\-filter\fR, \fB\-\-limit\fR.

.TP 2m
\fB\-\-limit\fR=\fILIMIT\fR

Maximum number of resources to list. The default is \fBunlimited\fR. This flag
interacts with other flags that are applied in this order: \fB\-\-flatten\fR,
\fB\-\-sort\-by\fR, \fB\-\-filter\fR, \fB\-\-limit\fR.

.TP 2m
\fB\-\-page\-size\fR=\fIPAGE_SIZE\fR

Some services group resource list output into pages. This flag specifies the
maximum number of resources per page. The default is determined by the service
if it supports paging, otherwise it is \fBunlimited\fR (no paging). Paging may
be applied before or after \fB\-\-filter\fR and \fB\-\-limit\fR depending on the
service.

.TP 2m
\fB\-\-sort\-by\fR=[\fIFIELD\fR,...]

Comma\-separated list of resource field key names to sort by. The default order
is ascending. Prefix a field with ``~'' for descending order on that field. This
flag interacts with other flags that are applied in this order:
\fB\-\-flatten\fR, \fB\-\-sort\-by\fR, \fB\-\-filter\fR, \fB\-\-limit\fR.


.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 list
.RE

.RS 2m
$ gcloud beta scc findings list
.RE