Set attack discovery alerts workflow status
https://{kibana_url}
- POST /api/detection_engine/attacks/status
Set the workflow status of one or more attack discovery alerts by IDs, optionally cascading the status to their related detection alerts.
Request
An object containing the desired status and explicit attack ids
One of:status: closed
-
idsobject · min: 1required -
A list of alerts
ids. -
reason -
The reason for closing the alerts. Can be one of following predefined reasons: [false_positive, duplicate, true_positive, benign_positive, automated_closure, other] or a custom reason provided by the user through the advanced settings.
-
Values:
false_positiveduplicatetrue_positivebenign_positiveautomated_closureother -
statusrequired -
Values:
closed -
When
true, the change is also applied to detection alerts related to the attacks viakibana.alert.attack_discovery.alert_ids.
status: open | acknowledged | in-progress
-
idsobject · min: 1required -
A list of alerts
ids. -
statusrequired -
The status of an alert, which can be
open,acknowledged,in-progress, orclosed. -
Values:
openacknowledgedin-progress -
When
true, the change is also applied to detection alerts related to the attacks viakibana.alert.attack_discovery.alert_ids.
Responses
Successful response
Response Type: object
Invalid input data response
-
errorstringrequired -
messagestringrequired -
statusCodeintegerrequired
-
messagestringrequired -
status_codeintegerrequired
Unsuccessful authentication response
-
errorstringrequired -
messagestringrequired -
statusCodeintegerrequired
Internal server error response
-
messagestringrequired -
status_codeintegerrequired