gcloud-help/gcloud/alpha/scc/findings/update-marks

NAME
    gcloud alpha scc findings update-marks - update Security Command Center
        finding's security marks

SYNOPSIS
    gcloud alpha 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
    (ALPHA) 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 alpha 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 alpha 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 alpha 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 alpha scc findings update-marks `testFinding` \
            --organization=123456 --source=5678 \
            --security-marks="key1=v1,key2=v2"

    Delete all security marks on testFinding:

        $ gcloud alpha 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 alpha 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
     attributes of this resource.

     This must be specified.

       FINDING
          ID of the finding or fully qualified identifier for the finding.

          To set the finding attribute:
          ▸ provide the argument finding on the command line.

          This positional argument must be specified if any of the other
          arguments in this group are specified.

       --organization=ORGANIZATION
          (Optional) If the full resource name isn't provided e.g.
          organizations/123, then provide the organization id which is the
          suffix of the organization. Example: organizations/123, the id is
          123.

          To set the organization attribute:
          ▸ provide the argument finding on the command line with a fully
            specified name;
          ▸ provide the argument --organization on the command line;
          ▸ Set the organization property in configuration using gcloud
            config set scc/organization if it is not specified in command
            line..

       --source=SOURCE
          (Optional) If the full resource name isn't provided e.g.
          organizations/123/sources/456, then provide the source id which is
          the suffix of the source. Example: organizations/123/sources/456, the
          id is 456.

          To set the source attribute:
          ▸ provide the argument finding on the command line with a fully
            specified name;
          ▸ 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:
        --security-marks="key1=val1,key2=val2".

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

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
    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. These variants are also available:

        $ gcloud scc findings update-marks

        $ gcloud beta scc findings update-marks