imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00
Code Activity

gcloud: Thu Feb 29 10:17:22 UTC 2024

Browse source
This commit is contained in:
Automated 2024-02-29 10:17:22 +00:00
parent 8778dcbd7e
commit 37dd57701a
203 changed files with 3473 additions and 5938 deletions
Download patch file Download diff file Expand all files Collapse all files

50
gcloud/beta/scc/findings/create
View file

@ -1,49 +1,59 @@
NAME
gcloud beta scc findings create - create a Cloud Security Command Center
finding
gcloud beta scc findings create - create a Security Command Center finding
SYNOPSIS
gcloud beta scc findings create
(FINDING : --organization=ORGANIZATION --source=SOURCE)
--category=CATEGORY --event-time=EVENT_TIME
--resource-name=RESOURCE_NAME [--external-uri=EXTERNAL_URI]
[--location=LOCATION; default="global"]
[--source-properties=[KEY=VALUE,...]] [--state=STATE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create a Cloud Security Command Center finding.
(BETA) Create a Security Command Center finding.
EXAMPLES
Create an ACTIVE myFinding with category: XSS_SCRIPTING attached to
example-project under organization 123456 and source 5678:
Create an ACTIVE finding testFinding with category: XSS_SCRIPTING attached
to example-project under organization 123456 and source 5678:
$ gcloud beta scc findings create `myFinding` \
$ gcloud beta scc findings create `testFinding` \
--organization=123456 --source=5678 --state=ACTIVE \
--category='XSS_SCRIPTING' \
--event-time=2023-01-11T07:00:06.861Z \
--resource-name='//cloudresourcemanager.googleapis.com/projects/\
example-project'
Create an ACTIVE myFinding attached to example-project under project
example-project and source 5678:
Create an ACTIVE finding testFinding attached to example-project under
project example-project and source 5678:
$ gcloud beta scc findings create \
projects/example-project/sources/5678/findings/myFinding \
projects/example-project/sources/5678/findings/testFinding \
--state=ACTIVE --category='XSS_SCRIPTING' \
--event-time=2023-01-11T07:00:06.861Z \
--resource-name='//cloudresourcemanager.googleapis.com/projects/\
example-project'
Create an ACTIVE myFinding attached to example-project under folder 456 and
source 5678:
Create an ACTIVE finding testFinding attached to example-project under
folder 456 and source 5678:
$ gcloud beta scc findings create \
folders/456/sources/5678/findings/myFinding --state=ACTIVE \
folders/456/sources/5678/findings/testFinding --state=ACTIVE \
--category='XSS_SCRIPTING' \
--event-time=2023-01-11T07:00:06.861Z \
--resource-name='//cloudresourcemanager.googleapis.com/projects/\
example-project'
Create an ACTIVE finding testFinding with category: XSS_SCRIPTING attached
to example-project under organization 123456, source 5678 and location=eu:
$ gcloud beta scc findings create `testFinding` \
--organization=123456 --source=5678 --state=ACTIVE \
--category='XSS_SCRIPTING' \
--event-time=2023-01-11T07:00:06.861Z \
--resource-name='//cloudresourcemanager.googleapis.com/projects/\
example-project' --location=eu
POSITIONAL ARGUMENTS
Finding resource - The finding to be used for the SCC (Security Command
Center) command. The arguments in this group can be used to specify the
@ -108,6 +118,17 @@ OPTIONAL FLAGS
finding can be found. This field is guaranteed to be either empty or a
well formed URL.
--location=LOCATION; default="global"
When data residency controls are enabled, this attribute specifies the
location in which the resource is located and applicable. The location
attribute can be provided as part of the fully specified resource name
or with the --location argument on the command line. The default
location is global.
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.
--source-properties=[KEY=VALUE,...]
Source specific properties. These properties are managed by the source
that writes the finding. The key names in the source_properties map
@ -128,8 +149,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the securitycenter/v1 API. The full documentation for
this API can be found at: https://cloud.google.com/security-command-center
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)
NOTES
This command is currently in beta and might change without notice. These

25
gcloud/beta/scc/findings/group
View file

@ -5,7 +5,8 @@ NAME
SYNOPSIS
gcloud beta scc findings group [PARENT]
[--compare-duration=COMPARE_DURATION] [--filter=FILTER]
[--group-by=GROUP_BY] [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN]
[--group-by=GROUP_BY] [--location=LOCATION; default="global"]
[--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN]
[--read-time=READ_TIME] [--source=SOURCE; default="-"]
[GCLOUD_WIDE_FLAG ...]
@ -54,6 +55,12 @@ EXAMPLES
$ gcloud beta scc findings group 123456 --source=5678 \
--group-by="state_change" --compare-duration=86400s
Group findings under organization 123456 and location=eu across all sources
by their category:
$ gcloud beta scc findings group 123456 --group-by="category" \
--location=eu
POSITIONAL ARGUMENTS
Parent resource - parent organization, folder, or project in the Google
Cloud resource hierarchy to be used for the gcloud scc command. Specify
@ -127,6 +134,17 @@ FLAGS
◆ state
◆ parent
--location=LOCATION; default="global"
When data residency controls are enabled, this attribute specifies the
location in which the resource is located and applicable. The location
attribute can be provided as part of the fully specified resource name
or with the --location argument on the command line. The default
location is global.
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.
--page-size=PAGE_SIZE
Maximum number of results to return in a single response. Default is
10, minimum is 1, maximum is 1000.
@ -154,8 +172,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the securitycenter/v1 API. The full documentation for
this API can be found at: https://cloud.google.com/security-command-center
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)
NOTES
This command is currently in beta and might change without notice. These

6
gcloud/beta/scc/findings/help
View file

@ -17,7 +17,7 @@ COMMANDS
COMMAND is one of the following:
create
(BETA) Create a Cloud Security Command Center finding.
(BETA) Create a Security Command Center finding.
group
(BETA) Filter an organization or source's findings and groups them by
@ -30,10 +30,10 @@ COMMANDS
(BETA) List a finding's security marks.
update
(BETA) Update a Cloud Security Command Center finding.
(BETA) Update a Security Command Center finding.
update-marks
(BETA) Update Cloud Security Command Center finding's security marks.
(BETA) Update Security Command Center finding's security marks.
NOTES
This command is currently in beta and might change without notice. These

24
gcloud/beta/scc/findings/list
View file

@ -4,7 +4,8 @@ NAME
SYNOPSIS
gcloud beta scc findings list [PARENT]
[--compare-duration=COMPARE_DURATION] [--field-mask=FIELD_MASK]
[--order-by=ORDER_BY] [--page-token=PAGE_TOKEN] [--read-time=READ_TIME]
[--location=LOCATION; default="global"] [--order-by=ORDER_BY]
[--page-token=PAGE_TOKEN] [--read-time=READ_TIME]
[--source=SOURCE; default="-"] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
@ -64,6 +65,11 @@ EXAMPLES
$ gcloud beta scc findings list 123456 \
--filter="state=\"ACTIVE\"" --read-time="2019-01-01T01:00:00Z"
List all findings under organization 123456 across all sources and
location=eu:
$ gcloud beta scc findings list 123456 --location=eu
POSITIONAL ARGUMENTS
Parent resource - parent organization, folder, or project in the Google
Cloud resource hierarchy to be used for the gcloud scc command. Specify
@ -118,6 +124,17 @@ FLAGS
v/s camel case used in field masks. An empty or missing field mask will
list all fields.
--location=LOCATION; default="global"
When data residency controls are enabled, this attribute specifies the
location in which the resource is located and applicable. The location
attribute can be provided as part of the fully specified resource name
or with the --location argument on the command line. The default
location is global.
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.
--order-by=ORDER_BY
Expression that defines what fields and order to use for sorting.
String value should follow SQL syntax: comma separated list of fields.
@ -177,8 +194,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the securitycenter/v1 API. The full documentation for
this API can be found at: https://cloud.google.com/security-command-center
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)
NOTES
This command is currently in beta and might change without notice. These

42
gcloud/beta/scc/findings/list-marks
View file

@ -4,30 +4,36 @@ NAME
SYNOPSIS
gcloud beta scc findings list-marks
(FINDING : --organization=ORGANIZATION --source=SOURCE)
[--page-token=PAGE_TOKEN] [--read-time=READ_TIME] [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
[--location=LOCATION; default="global"] [--page-token=PAGE_TOKEN]
[--read-time=READ_TIME] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List a finding's security marks.
EXAMPLES
List all security marks for myFinding under organization 123456 and source
5678:
List all security marks for testFinding under organization 123456 and
source 5678:
$ gcloud beta scc findings list-marks `myFinding` \
$ gcloud beta scc findings list-marks `testFinding` \
--organization=123456 --source=5678
List all security marks for myFinding under project example-project and
List all security marks for testFinding under project example-project and
source 5678:
$ gcloud beta scc findings list-marks \
projects/example-project/sources/5678/findings/myFinding
projects/example-project/sources/5678/findings/testFinding
List all security marks for myFinding under folder 456 and source 5678:
List all security marks for testFinding under folder 456 and source 5678:
$ gcloud beta scc findings list-marks \
folders/456/sources/5678/findings/myFinding
folders/456/sources/5678/findings/testFinding
List all security marks for testFinding under organization 123456, source
5678 and location=eu:
$ gcloud beta scc findings list-marks `testFinding` \
--organization=123456 --source=5678 --location=eu
POSITIONAL ARGUMENTS
Finding resource - The finding to be used for the SCC (Security Command
@ -71,6 +77,17 @@ POSITIONAL ARGUMENTS
▸ provide the argument --source on the command line.
FLAGS
--location=LOCATION; default="global"
When data residency controls are enabled, this attribute specifies the
location in which the resource is located and applicable. The location
attribute can be provided as part of the fully specified resource name
or with the --location argument on the command line. The default
location is global.
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.
--page-token=PAGE_TOKEN
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
@ -117,8 +134,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the securitycenter/v1 API. The full documentation for
this API can be found at: https://cloud.google.com/security-command-center
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)
NOTES
This command is currently in beta and might change without notice. These

48
gcloud/beta/scc/findings/update
View file

@ -1,48 +1,54 @@
NAME
gcloud beta scc findings update - update a Cloud Security Command Center
finding
gcloud beta scc findings update - update a Security Command Center finding
SYNOPSIS
gcloud beta scc findings update
(FINDING : --organization=ORGANIZATION --source=SOURCE)
[--event-time=EVENT_TIME] [--external-uri=EXTERNAL_URI]
[--location=LOCATION; default="global"]
[--source-properties=[KEY=VALUE,...]] [--state=STATE]
[--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update a Cloud Security Command Center finding.
(BETA) Update a Security Command Center finding.
EXAMPLES
Update myFinding's state from ACTIVE to INACTIVE:
Update testFinding's state from ACTIVE to INACTIVE:
$ gcloud beta scc findings update `myFinding` \
$ gcloud beta scc findings update `testFinding` \
--organization=123456 --source=5678 --state=INACTIVE
Update myFinding's state from ACTIVE to INACTIVE using project name for
Update testFinding's state from ACTIVE to INACTIVE using project name for
example-project:
$ gcloud beta scc findings update \
projects/example-project/sources/5678/findings/myFinding \
projects/example-project/sources/5678/findings/testFinding \
--state=INACTIVE
Update myFinding's state from ACTIVE to INACTIVE using folder name 456:
Update testFinding's state from ACTIVE to INACTIVE using folder name 456:
$ gcloud beta scc findings update \
folders/456/sources/5678/findings/myFinding --state=INACTIVE
folders/456/sources/5678/findings/testFinding --state=INACTIVE
Override all source properties on myFinding:
Override all source properties on testFinding:
$ gcloud beta scc findings update `myFinding` \
$ gcloud beta scc findings update `testFinding` \
--organization=123456 --source=5678 \
--source-properties="propKey1=propVal1,propKey2=propVal2"
Selectively update a specific source property on myFinding:
Selectively update a specific source property on testFinding:
$ gcloud beta scc findings update `myFinding` \
$ gcloud beta scc findings update `testFinding` \
--organization=123456 --source=5678 \
--source-properties="propKey1=propVal1,propKey2=propVal2" \
--update-mask="source_properties.propKey1"
Update finding testFinding with location=eu, state from ACTIVE to INACTIVE:
$ gcloud beta scc findings update `testFinding` \
--organization=123456 --source=5678 --state=INACTIVE \
--location=eu
POSITIONAL ARGUMENTS
Finding resource - The finding to be used for the SCC (Security Command
Center) command. The arguments in this group can be used to specify the
@ -98,6 +104,17 @@ FLAGS
finding can be found. This field is guaranteed to be either empty or a
well formed URL.
--location=LOCATION; default="global"
When data residency controls are enabled, this attribute specifies the
location in which the resource is located and applicable. The location
attribute can be provided as part of the fully specified resource name
or with the --location argument on the command line. The default
location is global.
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.
--source-properties=[KEY=VALUE,...]
Source specific properties. These properties are managed by the source
that writes the finding. The key names in the source_properties map
@ -133,8 +150,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the securitycenter/v1 API. The full documentation for
this API can be found at: https://cloud.google.com/security-command-center
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)
NOTES
This command is currently in beta and might change without notice. These

52
gcloud/beta/scc/findings/update-marks
View file

@ -1,49 +1,57 @@
NAME
gcloud beta scc findings update-marks - update Cloud Security Command
Center finding's security marks
gcloud beta scc findings update-marks - update Security Command Center
finding's security marks
SYNOPSIS
gcloud beta scc findings update-marks
(FINDING : --organization=ORGANIZATION --source=SOURCE)
[--location=LOCATION; default="global"]
[--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME]
[--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update Cloud Security Command Center finding's security marks.
(BETA) Update Security Command Center finding's security marks.
EXAMPLES
Selectively update security mark (Key1) with value (v1) on myFinding. Note
that other security marks on myFinding are untouched:
Selectively update security mark Key1 with value v1 on testFinding. Note
that other security marks on testFinding are untouched:
$ gcloud beta scc findings update-marks `myFinding` \
$ gcloud beta scc findings update-marks `testFinding` \
--organization=123456 --source=5678 --security-marks="key1=v1" \
--update-mask="marks.markKey1"
Update all security marks on myFinding, under project example-project and
Update all security marks on testFinding, under project example-project and
source 5678:
$ gcloud beta scc findings update-marks \
projects/example-project/sources/5678/findings/myFinding \
projects/example-project/sources/5678/findings/testFinding \
--security-marks="key1=v1,key2=v2"
Update all security marks on myFinding, under folder 456 and source 5678:
Update all security marks on testFinding, under folder 456 and source 5678:
$ gcloud beta scc findings update-marks \
folders/456/sources/5678/findings/myFinding \
folders/456/sources/5678/findings/testFinding \
--security-marks="key1=v1,key2=v2"
Update all security marks on myFinding, under organization 123456 and
Update all security marks on testFinding, under organization 123456 and
source 5678:
$ gcloud beta scc findings update-marks `myFinding` \
$ gcloud beta scc findings update-marks `testFinding` \
--organization=123456 --source=5678 \
--security-marks="key1=v1,key2=v2"
Delete all security marks on myFinding:
Delete all security marks on testFinding:
$ gcloud beta scc findings update-marks `myFinding` \
$ gcloud beta scc findings update-marks `testFinding` \
--organization=123456 --source=5678 --security-marks=""
Update all security marks on testFinding, under project example-project,
source 5678 and location=eu:
$ gcloud beta scc findings update-marks \
projects/example-project/sources/5678/findings/testFinding \
--security-marks="key1=v1,key2=v2" --location=eu
POSITIONAL ARGUMENTS
Finding resource - The finding to be used for the SCC (Security Command
Center) command. The arguments in this group can be used to specify the
@ -86,6 +94,17 @@ POSITIONAL ARGUMENTS
▸ provide the argument --source on the command line.
FLAGS
--location=LOCATION; default="global"
When data residency controls are enabled, this attribute specifies the
location in which the resource is located and applicable. The location
attribute can be provided as part of the fully specified resource name
or with the --location argument on the command line. The default
location is global.
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.
--security-marks=[KEY=VALUE,...]
SecurityMarks resource to be passed as the request body. It's a
key=value pair separated by comma (,). For example:
@ -111,8 +130,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the securitycenter/v1 API. The full documentation for
this API can be found at: https://cloud.google.com/security-command-center
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)
NOTES
This command is currently in beta and might change without notice. These

48
gcloud/beta/scc/notifications/create
View file

@ -1,16 +1,22 @@
NAME
gcloud beta scc notifications create - create a Cloud Security Command
Center notification config
gcloud beta scc notifications create - create a Security Command Center
notification config
SYNOPSIS
gcloud beta scc notifications create NOTIFICATION_CONFIG_ID
--pubsub-topic=PUBSUB_TOPIC [--description=DESCRIPTION]
[--filter=FILTER]
[--filter=FILTER] [--location=LOCATION; default="global"]
[--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create a Cloud Security Command Center notification config.
(BETA) Create a Security Command Center notification config.
Notification configs that are created with Security Command Center API V2
and later include a location attribute. If a location is not specified, the
default global location is used. For example, the following Notification
config name has location=global attribute:
organizations/123/locations/global/notificationConfigs/my-config.
EXAMPLES
Create a notification config test-config under organization 123 for
@ -21,10 +27,6 @@ EXAMPLES
--organization=123 \
--pubsub-topic=projects/test-project/topics/notification-test \
--filter="resource_name: \"a\""
$ gcloud beta scc notifications create \
organizations/123/notificationConfigs/test-config \
--pubsub-topic=projects/test-project/topics/notification-test \
--filter="resource_name: \"a\""
Create a notification config test-config under folder 456 for findings for
pubsub-topic projects/test-project/topics/notification-test with a filter
@ -33,10 +35,6 @@ EXAMPLES
$ gcloud beta scc notifications create test-config --folder=456 \
--pubsub-topic=projects/test-project/topics/notification-test \
--filter="resource_name: \"a\""
$ gcloud beta scc notifications create \
folders/456/notificationConfigs/test-config \
--pubsub-topic=projects/test-project/topics/notification-test \
--filter="resource_name: \"a\""
Create a notification config test-config under project 789 for findings for
pubsub-topic projects/test-project/topics/notification-test with a filter
@ -45,10 +43,14 @@ EXAMPLES
$ gcloud beta scc notifications create test-config --project=789 \
--pubsub-topic=projects/test-project/topics/notification-test \
--filter="resource_name: \"a\""
$ gcloud beta scc notifications create \
projects/789/notificationConfigs/test-config \
Create a notification config test-config under organization 123 for
findings for pubsub-topic projects/test-project/topics/notification-test
with a filter on resource name and location=eu
$ gcloud beta scc notifications create test-config --project=789 \
--pubsub-topic=projects/test-project/topics/notification-test \
--filter="resource_name: \"a\""
--filter="resource_name: \"a\"" --location=eu
POSITIONAL ARGUMENTS
NOTIFICATION_CONFIG_ID
@ -67,6 +69,17 @@ OPTIONAL FLAGS
--filter=FILTER
Filter to be used for notification config.
--location=LOCATION; default="global"
When data residency controls are enabled, this attribute specifies the
location in which the resource is located and applicable. The location
attribute can be provided as part of the fully specified resource name
or with the --location argument on the command line. The default
location is global.
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.
At most one of these can be specified:
--folder=FOLDER
@ -90,8 +103,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the securitycenter/v1 API. The full documentation for
this API can be found at: https://cloud.google.com/security-command-center
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)
NOTES
This command is currently in beta and might change without notice. These

60
gcloud/beta/scc/notifications/delete
View file

@ -1,33 +1,47 @@
NAME
gcloud beta scc notifications delete - delete a Cloud Security Command
Center notification config
gcloud beta scc notifications delete - delete a Security Command Center
notification config
SYNOPSIS
gcloud beta scc notifications delete NOTIFICATION_CONFIG_ID
[--location=LOCATION; default="global"]
[--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Delete a Cloud Security Command Center notification config.
(BETA) Delete a Security Command Center notification config.
Notification configs that are created with Security Command Center API V2
and later include a location attribute. If the location attribute is
included in the resource name of a Notification configs, you must specify
it when referencing the Notification config. For example, the following
Notification configs name has location=eu:
organizations/123/locations/eu/notificationConfigs/test-config.
EXAMPLES
Delete notification config 'my-config' from organization 123
Delete notification config 'test-config' from organization 123
$ gcloud beta scc notifications delete my-config --organization=123
$ gcloud beta scc notifications delete \
organizations/123/notificationConfigs/my-config
$ gcloud beta scc notifications delete test-config --organization=123
Delete notification config 'my-config' from folder 456
Delete notification config 'test-config' from folder 456
$ gcloud beta scc notifications delete my-config --folder=456
$ gcloud beta scc notifications delete \
folders/456/notificationConfigs/my-config
$ gcloud beta scc notifications delete test-config --folder=456
Delete notification config 'my-config' from project 789
Delete notification config 'test-config' from project 789
$ gcloud beta scc notifications delete my-config --project=789
$ gcloud beta scc notifications delete \
projects/789/notificationConfigs/my-config
$ gcloud beta scc notifications delete test-config --project=789
Delete notification config 'test-config' with location global from
organization 123
$ gcloud beta scc notifications delete test-config \
--organization=123 --location=global
Delete notification config 'test-config' with location=eu from organization
123
$ gcloud beta scc notifications delete test-config \
--organization=123 --location=eu
POSITIONAL ARGUMENTS
NOTIFICATION_CONFIG_ID
@ -35,6 +49,17 @@ POSITIONAL ARGUMENTS
"organizations/123/notificationConfigs/456" or just "456".
FLAGS
--location=LOCATION; default="global"
When data residency controls are enabled, this attribute specifies the
location in which the resource is located and applicable. The location
attribute can be provided as part of the fully specified resource name
or with the --location argument on the command line. The default
location is global.
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.
At most one of these can be specified:
--folder=FOLDER
@ -58,8 +83,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the securitycenter/v1 API. The full documentation for
this API can be found at: https://cloud.google.com/security-command-center
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)
NOTES
This command is currently in beta and might change without notice. These

58
gcloud/beta/scc/notifications/describe
View file

@ -1,36 +1,42 @@
NAME
gcloud beta scc notifications describe - describe a Cloud Security Command
Center notification config
gcloud beta scc notifications describe - describe a Security Command Center
notification config
SYNOPSIS
gcloud beta scc notifications describe NOTIFICATION_CONFIG_ID
[--location=LOCATION; default="global"]
[--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Describe a Cloud Security Command Center notification config.
(BETA) Describe a Security Command Center notification config.
Notification configs that are created with Security Command Center API V2
and later include a location attribute. If the location attribute is
included in the resource name of a Notification configs, you must specify
it when referencing the Notification config. For example, the following
Notification configs name has location=eu:
organizations/123/locations/eu/notificationConfigs/test-config.
EXAMPLES
Describe notification config 'my-config' from organization 123
Describe notification config 'test-config' from organization 123
$ gcloud beta scc notifications describe notifications describe \
my-config --organization=123
$ gcloud beta scc notifications describe notifications describe \
organizations/123/notificationConfigs/my-config
$ gcloud beta scc notifications describe test-config \
--organization=123
Describe notification config 'my-config' from folder 456
Describe notification config 'test-config' from folder 456
$ gcloud beta scc notifications describe notifications describe \
my-config --folder=456
$ gcloud beta scc notifications describe notifications describe \
folders/456/notificationConfigs/my-config
$ gcloud beta scc notifications describe test-config --folder=456
Describe notification config 'my-config' from project 789
Describe notification config 'test-config' from project 789
$ gcloud beta scc notifications describe notifications describe \
my-config --project=789
$ gcloud beta scc notifications describe notifications describe \
projects/789/notificationConfigs/my-config
$ gcloud beta scc notifications describe test-config --project=789
Describe notification config 'test-config' from organization 123 and
location=global
$ gcloud beta scc notifications describe test-config \
--organization=123 --location=global
POSITIONAL ARGUMENTS
NOTIFICATION_CONFIG_ID
@ -38,6 +44,17 @@ POSITIONAL ARGUMENTS
"organizations/123/notificationConfigs/456" or just "456".
FLAGS
--location=LOCATION; default="global"
When data residency controls are enabled, this attribute specifies the
location in which the resource is located and applicable. The location
attribute can be provided as part of the fully specified resource name
or with the --location argument on the command line. The default
location is global.
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.
At most one of these can be specified:
--folder=FOLDER
@ -61,8 +78,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the securitycenter/v1 API. The full documentation for
this API can be found at: https://cloud.google.com/security-command-center
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)
NOTES
This command is currently in beta and might change without notice. These

10
gcloud/beta/scc/notifications/help
View file

@ -17,19 +17,19 @@ COMMANDS
COMMAND is one of the following:
create
(BETA) Create a Cloud Security Command Center notification config.
(BETA) Create a Security Command Center notification config.
delete
(BETA) Delete a Cloud Security Command Center notification config.
(BETA) Delete a Security Command Center notification config.
describe
(BETA) Describe a Cloud Security Command Center notification config.
(BETA) Describe a Security Command Center notification config.
list
(BETA) List Cloud Security Command Center notification configs.
(BETA) List Security Command Center notification configs.
update
(BETA) Update a Cloud Security Command Center notification config.
(BETA) Update a Security Command Center notification config.
NOTES
This command is currently in beta and might change without notice. These

34
gcloud/beta/scc/notifications/list
View file

@ -1,14 +1,19 @@
NAME
gcloud beta scc notifications list - list Cloud Security Command Center
gcloud beta scc notifications list - list Security Command Center
notification configs
SYNOPSIS
gcloud beta scc notifications list [PARENT] [--filter=EXPRESSION]
gcloud beta scc notifications list [PARENT]
[--location=LOCATION; default="global"] [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List Cloud Security Command Center notification configs.
(BETA) List Security Command Center notification configs.
Notification Configs that are created with Security Command Center API V2
and later include a `location` attribute. Include the `--location` flag to
list Notification Configs with `location` attribute other than `global`.
EXAMPLES
List notification configs from organization 123
@ -24,6 +29,12 @@ EXAMPLES
$ gcloud beta scc notifications list projects/789
List notification configs from organization 123 and location=eu
$ gcloud beta scc notifications list 123 --location=eu
$ gcloud beta scc notifications list organizations/123 \
--location=locations/eu
POSITIONAL ARGUMENTS
Parent resource - parent organization, folder, or project in the Google
Cloud resource hierarchy to be used for the gcloud scc command. Specify
@ -38,6 +49,18 @@ POSITIONAL ARGUMENTS
▸ Set the parent property in configuration using gcloud config set
scc/parent if it is not specified in command line.
FLAGS
--location=LOCATION; default="global"
When data residency controls are enabled, this attribute specifies the
location in which the resource is located and applicable. The location
attribute can be provided as part of the fully specified resource name
or with the --location argument on the command line. The default
location is global.
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.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
@ -73,8 +96,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the securitycenter/v1 API. The full documentation for
this API can be found at: https://cloud.google.com/security-command-center
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)
NOTES
This command is currently in beta and might change without notice. These

88
gcloud/beta/scc/notifications/update
View file

@ -1,81 +1,69 @@
NAME
gcloud beta scc notifications update - update a Cloud Security Command
Center notification config
gcloud beta scc notifications update - update a Security Command Center
notification config
SYNOPSIS
gcloud beta scc notifications update NOTIFICATION_CONFIG_ID
[--description=DESCRIPTION] [--filter=FILTER]
[--pubsub-topic=PUBSUB_TOPIC]
[--location=LOCATION; default="global"] [--pubsub-topic=PUBSUB_TOPIC]
[--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update a Cloud Security Command Center notification config.
(BETA) Update a Security Command Center notification config.
Notification configs that are created with Security Command Center API V2
and later include a location attribute. If the location attribute is
included in the resource name of a Notification configs, you must specify
it when referencing the Notification config. For example, the following
Notification configs name has location=eu:
organizations/123/locations/eu/notificationConfigs/test-config.
EXAMPLES
Update all mutable fields under an organization parent my-config
Update all mutable fields under an organization parent test-config
(description + pubsub topic + filter):
$ gcloud beta scc notifications update scc notifications update \
my-config --organization=123 --description="New description" \
test-config --organization=123 --description="New description" \
--pubsub-topic="projects/22222/topics/newtopic"
$ gcloud beta scc notifications update scc notifications update \
organizations/123/notificationConfigs/my-config \
--description="New description" \
--pubsub-topic="projects/22222/topics/newtopic"
Update all mutable fields under a folder parent my-config (description +
Update all mutable fields under a folder parent test-config (description +
pubsub topic + filter):
$ gcloud beta scc notifications update scc notifications update \
my-config --folder=456 --description="New description" \
test-config --folder=456 --description="New description" \
--pubsub-topic="projects/22222/topics/newtopic"
$ gcloud beta scc notifications update scc notifications update \
folders/456/notificationConfigs/my-config \
--description="New description" \
--pubsub-topic="projects/22222/topics/newtopic"
Update all mutable fields under a project parent my-config (description +
Update all mutable fields under a project parent test-config (description +
pubsub topic + filter):
$ gcloud beta scc notifications update scc notifications update \
my-config --project=789 --description="New description" \
test-config --project=789 --description="New description" \
--pubsub-topic="projects/22222/topics/newtopic"
$ gcloud beta scc notifications update scc notifications update \
projects/789/notificationConfigs/my-config \
--description="New description" \
--pubsub-topic="projects/22222/topics/newtopic"
Update test-config's description
Update my-config's description
$ gcloud beta scc notifications update my-config \
$ gcloud beta scc notifications update test-config \
--organization=123 --description="New description"
$ gcloud beta scc notifications update \
organizations/123/notificationConfigs/my-config \
--description="New description"
Update test-config's pubsub-topic
Update my-config's pubsub-topic
$ gcloud beta scc notifications update my-config \
$ gcloud beta scc notifications update test-config \
--organization=123 \
--pubsub-topic="projects/22222/topics/newtopic"
$ gcloud beta scc notifications update \
organizations/123/notificationConfigs/my-config \
--pubsub-topic="projects/22222/topics/newtopic"
Update test-config's filter
Update my-config's filter
$ gcloud beta scc notifications update my-config \
$ gcloud beta scc notifications update test-config \
--organization=123 --filter='state = \"ACTIVE\"'
$ gcloud beta scc notifications update \
organizations/123/notificationConfigs/my-config \
--filter='state = \"ACTIVE\"'
Update all mutable fields for test-config with location=global under an
organization parent (description + pubsub topic + filter):
$ gcloud beta scc notifications update scc notifications update \
test-config --organization=123 --description="New description" \
--pubsub-topic="projects/22222/topics/newtopic" \
--location=global
POSITIONAL ARGUMENTS
NOTIFICATION_CONFIG_ID
@ -90,6 +78,17 @@ FLAGS
The filter string which will applied to events of findings of a
notification configuration.
--location=LOCATION; default="global"
When data residency controls are enabled, this attribute specifies the
location in which the resource is located and applicable. The location
attribute can be provided as part of the fully specified resource name
or with the --location argument on the command line. The default
location is global.
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.
--pubsub-topic=PUBSUB_TOPIC
The Pub/Sub topic which will receive notifications. Its format is
"projects/[project_id]/topics/[topic]".
@ -117,8 +116,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the securitycenter/v1 API. The full documentation for
this API can be found at: https://cloud.google.com/security-command-center
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)
NOTES
This command is currently in beta and might change without notice. These