NAME gcloud scc findings update-marks - update Security Command Center finding's security marks SYNOPSIS gcloud scc findings update-marks FINDING [--location=LOCATION; default="global"] [--security-marks=[KEY=VALUE,...]] [--source=SOURCE; default="-"] [--start-time=START_TIME] [--update-mask=UPDATE_MASK] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update Security Command Center finding's security marks. EXAMPLES Selectively update security mark Key1 with value v1 on testFinding. Note that other security marks on testFinding are untouched: $ gcloud scc findings update-marks `testFinding` \ --organization=123456 --source=5678 --security-marks="key1=v1" \ --update-mask="marks.markKey1" Update all security marks on testFinding, under project example-project and source 5678: $ gcloud scc findings update-marks \ projects/example-project/sources/5678/findings/testFinding \ --security-marks="key1=v1,key2=v2" Update all security marks on testFinding, under folder 456 and source 5678: $ gcloud scc findings update-marks \ folders/456/sources/5678/findings/testFinding \ --security-marks="key1=v1,key2=v2" Update all security marks on testFinding, under organization 123456 and source 5678: $ gcloud scc findings update-marks `testFinding` \ --organization=123456 --source=5678 \ --security-marks="key1=v1,key2=v2" Delete all security marks on testFinding: $ gcloud 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 scc findings update-marks \ projects/example-project/sources/5678/findings/testFinding \ --security-marks="key1=v1,key2=v2" --location=eu POSITIONAL ARGUMENTS FINDING ID of the finding or fully qualified identifier for the finding. 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: --security-marks="key1=val1,key2=val2". --source=SOURCE; default="-" Source id. Defaults to all sources. --start-time=START_TIME Time at which the updated SecurityMarks take effect. See $ gcloud topic datetimes for information on supported time formats. --update-mask=UPDATE_MASK 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. At most one of these can be specified: --folder=FOLDER The folder ID (e.g., 456) that contains the finding. --organization=ORGANIZATION The organization ID (e.g., 123) that contains the finding. --project=PROJECT The project ID (e.g., example-project) that contains the finding. 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 $ gcloud help for details. 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) NOTES These variants are also available: $ gcloud alpha scc findings update-marks $ gcloud beta scc findings update-marks