Kicks off an LRO to bulk mute findings for a parent based on a filter. The parent can be either an organization, folder or project. The findings matched by the filter will be muted after the LRO is done.
HTTP request
POST https://securitycenter.googleapis.com/v1/{parent=folders/*}/findings:bulkMute
The URLs use gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
parent
|
Required. The parent, at which bulk action needs to be applied. Its format is |
Request body
The request body contains data with the following structure:
| JSON representation |
|---|
{
"filter"
:
string
,
"muteAnnotation"
:
string
,
"muteState"
:
enum (
|
filter
string
Expression that identifies findings that should be updated. The expression is a list of zero or more restrictions combined via logical operators AND
and OR
. Parentheses are supported, and OR
has higher precedence than AND
.
Restrictions have the form <field> <operator> <value>
and may have a -
character in front of them to indicate negation. The fields map to those defined in the corresponding resource.
The supported operators are:
-
=for all value types. -
>,<,>=,<=for integer values. -
:, meaning substring matching, for strings.
The supported value types are:
- string literals in quotes.
- integer literals without quotes.
- boolean literals
trueandfalsewithout quotes.
muteAnnotation
(deprecated)
string
This can be a mute configuration name or any identifier for mute/unmute of findings based on the filter.
muteState
enum (
MuteState
)
Optional. All findings matching the given filter will have their mute state set to this value. The default value is MUTED
. Setting this to UNDEFINED
will clear the mute state on all matching findings.
Response body
If successful, the response body contains an instance of Operation
.
Authorization scopes
Requires the following OAuth scope:
-
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview .
