Request message for grouping by findings.
Expression that defines the filter to apply across findings.
The expression is a list of one 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. Examples include: - name -
source_properties.a_property - security_marks.marks.marka
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 true and false
without quotes. The following field and operator combinations
are supported: - name: = - parent: =, : -
resource_name: =, : - state: =, : -
category: =, : - external_uri: =, : -
event_time: =, >, <, >=, <= Usage: This
should be milliseconds since epoch or an RFC3339 string.
Examples: "event_time = "2019-06-10T16:07:18-07:00""
"event_time = 1560208038000" - security_marks.marks:
=, : - source_properties: =, :, >,
<, >=, <= For example, source_properties.size =
100 is a valid filter string.
Time used as a reference point when filtering findings. The filter is limited to findings existing at the supplied time and their values are those at that specific time. Absence of this field will default to the API's version of NOW.
Filter that specifies what fields to further filter on after
the query filter has been executed. Currently only
finding.state and state_change are supported and
requires compare_duration to be specified.
The maximum number of results to return in a single response. Default is 10, minimum is 1, maximum is 1000.