File Scanning and Webhooks
Last updated
Was this helpful?
Last updated
Was this helpful?
As part of submitting a file scan request, the request payload must contain a reference to a URL defined as part of a policy
defined inline.
When Nightfall prepares a file scan operation, it will issue a challenge to the to verify its legitimacy.
After the file scan has been processed asynchronously, the results will be delivered to the webhook.
For a file scan, your webhook will receive a request body that will be a JSON payload containing:
the upload UUID (uploadID
)
a boolean indicating whether or not any data in the file matched the provided detection rules (findingsPresent
)
a pre-signed S3 URL where the caller may fetch the findings for the scan (findingsURL
). if there are no findings in the file, this field will be empty.
the date until which the findingsURL is valid (validUntil
) formatted to . Results are valid for 24 hours after scan completion. The time will be in UTC.
the value you supplied for requestMetadata. Callers may opt to use this to help identify their input file upon receiving a webhook response. Maximum length 10 KB.
Below is an example of a payload sent to the webhook URL.
In this example, we have uploaded a zip file with a python script (upload.py) and a README.md file. A Detector in our DetectionRule checks for the presence of the string http://localhost
If you follow the URL (before it expires) it will return a JSON representation of the findings similar to those returned by the endpoint.