Monitor Forensic Data Ingestion Tool Execution

Note

To use the data ingestion tool features, you can add the DFIR package to your instance of the Cybereason platform for an additional cost or request an Express IR environment (partners only). Contact your Customer Success representative to request access to this package or for details on how to submit the request, see How to Request a Cybereason Express IR Environment.

Endpoint URL: https://<your server>/rest/forensics/getForensicToolRunStatus/:batchId
Endpoint URI: forensics/getForensicToolRunStatus/:batchId

Action: GET

Monitors the execution of a forensic data package (identified by the batch ID number from an execution request). For details on how to run a forensic data package, see Run a Forensic Data Ingestion Tool.

This request is supported for versions 21.2.221 and later.

You must have the Responder L2 role assigned for your Cybereason user to run this request.

Note

Ensure that you have logged into the Cybereason platform. For details, see Log in with the API.

Request Headers

You must add a Content-Type:application/json header with the request.

Note

If you are using cURL, add the authorization cookie details or the path to the file containing the cookie details as part of every request.


Request Body

None


Request Parameters

URL/URI parameters: You must add the required batchID string value (taken from the response of the request to run an forensic data package) in the URL.

Request Body Parameters: none


Response Status Codes

This request can return the following status codes:

  • 200: The request succeeded

  • 400: Bad request parameters

  • 403: Lack of permissions to perform the request / IRTools service is disabled

  • 500: Internal error on Perspective Server

  • 503: Forensics service is disabled


Response Success Schema

The response contains the following fields:

  • Sensor: The unique sensor ID for the sensors involved in the forensic data package execution.

  • Status: The status of the package execution operation.

    Note that the request can succeed and the tool process may start on the target machine(s). However, a response of success does not guarantee that the IR tool process runs correctly or collects results from the machine. To verify that the process ran correctly, you can use the Investigation screen and view the details of the tool process.

  • Error: Any relevant error messages.


Response Failure Schema

An error code with a description of the error.


Important Response Fields

All information contained in the response is important for you to understand if the package ran successfully.


Example: Monitor the status of a forensic data package

Request

curl --request GET \
  --url https://12.34.56.78/forensics/getForensicToolRunStatus/1438096773 \
  --header 'Content-Type:application/json' \

Response

Sensor,Status,Error
PYLUMCLIENT_IR-15-APRIL_WIN10-X64-19H1_005056A642D0,Succeeded,SEC_SUCCESS
PYLUMCLIENT_IR-15-APRIL_WIN10-X64-20H1_005056A66E2C,Succeeded,SEC_SUCCESS