See: newBatchUpdateFindings smart constructor.

Create a value of BatchUpdateFindings with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:criticality:BatchUpdateFindings', batchUpdateFindings_criticality - The updated value for the level of importance assigned to the resources associated with the findings.

A score of 0 means that the underlying resources have no criticality, and a score of 100 is reserved for the most critical resources.

$sel:note:BatchUpdateFindings', batchUpdateFindings_note - Undocumented member.

$sel:severity:BatchUpdateFindings', batchUpdateFindings_severity - Used to update the finding severity.

$sel:types:BatchUpdateFindings', batchUpdateFindings_types - One or more finding types in the format of namespace/category/classifier that classify a finding.

Valid namespace values are as follows.

• Software and Configuration Checks
• TTPs
• Effects
• Unusual Behaviors
• Sensitive Data Identifications

$sel:relatedFindings:BatchUpdateFindings', batchUpdateFindings_relatedFindings - A list of findings that are related to the updated findings.

$sel:confidence:BatchUpdateFindings', batchUpdateFindings_confidence - The updated value for the finding confidence. Confidence is defined as the likelihood that a finding accurately identifies the behavior or issue that it was intended to identify.

Confidence is scored on a 0-100 basis using a ratio scale, where 0 means zero percent confidence and 100 means 100 percent confidence.

$sel:workflow:BatchUpdateFindings', batchUpdateFindings_workflow - Used to update the workflow status of a finding.

The workflow status indicates the progress of the investigation into the finding.

$sel:verificationState:BatchUpdateFindings', batchUpdateFindings_verificationState - Indicates the veracity of a finding.

The available values for VerificationState are as follows.

• UNKNOWN – The default disposition of a security finding
• TRUE_POSITIVE – The security finding is confirmed
• FALSE_POSITIVE – The security finding was determined to be a false alarm
• BENIGN_POSITIVE – A special case of TRUE_POSITIVE where the finding doesn't pose any threat, is expected, or both

$sel:userDefinedFields:BatchUpdateFindings', batchUpdateFindings_userDefinedFields - A list of name/value string pairs associated with the finding. These are custom, user-defined fields added to a finding.

$sel:findingIdentifiers:BatchUpdateFindings', batchUpdateFindings_findingIdentifiers - The list of findings to update. BatchUpdateFindings can be used to update up to 100 findings at a time.

For each finding, the list provides the finding identifier and the ARN of the finding provider.

The updated value for the level of importance assigned to the resources associated with the findings.

A score of 0 means that the underlying resources have no criticality, and a score of 100 is reserved for the most critical resources.

Undocumented member.

Used to update the finding severity.

One or more finding types in the format of namespace/category/classifier that classify a finding.

Valid namespace values are as follows.

• Software and Configuration Checks
• TTPs
• Effects
• Unusual Behaviors
• Sensitive Data Identifications

A list of findings that are related to the updated findings.

The updated value for the finding confidence. Confidence is defined as the likelihood that a finding accurately identifies the behavior or issue that it was intended to identify.

Confidence is scored on a 0-100 basis using a ratio scale, where 0 means zero percent confidence and 100 means 100 percent confidence.

Used to update the workflow status of a finding.

The workflow status indicates the progress of the investigation into the finding.

Indicates the veracity of a finding.

The available values for VerificationState are as follows.

• UNKNOWN – The default disposition of a security finding
• TRUE_POSITIVE – The security finding is confirmed
• FALSE_POSITIVE – The security finding was determined to be a false alarm
• BENIGN_POSITIVE – A special case of TRUE_POSITIVE where the finding doesn't pose any threat, is expected, or both

A list of name/value string pairs associated with the finding. These are custom, user-defined fields added to a finding.

The list of findings to update. BatchUpdateFindings can be used to update up to 100 findings at a time.

For each finding, the list provides the finding identifier and the ARN of the finding provider.

See: newBatchUpdateFindingsResponse smart constructor.

Create a value of BatchUpdateFindingsResponse with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:httpStatus:BatchUpdateFindingsResponse', batchUpdateFindingsResponse_httpStatus - The response's http status code.

$sel:processedFindings:BatchUpdateFindingsResponse', batchUpdateFindingsResponse_processedFindings - The list of findings that were updated successfully.

$sel:unprocessedFindings:BatchUpdateFindingsResponse', batchUpdateFindingsResponse_unprocessedFindings - The list of findings that were not updated.

The response's http status code.

The list of findings that were updated successfully.

The list of findings that were not updated.