Performing a dynamic scan
The command below demonstrates how to initiate a dynamic (deep) scan using the ESET scanner agent. When a file is submitted, it is sent for advanced dynamic analysis. In this example, the dynamic scan has been triggered, but the results are not yet available as the analysis is still in progress (deep scan status is pending).
Command:
scanner_agent -t 'example.com/load_balancer:50052' -s -a 'http://example.com/scanner/protocol/openid-connect/token -u 'username' -p 'password' -v CF0E53240849E03EFD7F15CC67F8E541CE17AA7900ECB7DE805C31C9BE7BD796 /samples/app-release.apk |
Default Scanner JSON response example:
Will scan these files: /samples/app-release.apk {"scanResults": [{"objectReference": "/samples/app-release.apk", "dataHashSha1": "C7D047A60BC301F715B0B4106328A6C372FBABD5", "dataHashSha256": "CF0E53240849E03EFD7F15CC67F8E541CE17AA7900ECB7DE805C31C9BE7BD796", "dataSizeBytes": "11219720", "objectType": "OBJECT_TYPE_FILE", "objectDisplayName": "/samples/app-release.apk", "scanFinishTime": "2025-07-29T10:20:36Z", "deepScanStatus": "DEEP_SCAN_STATUS_PENDING", "objectIsClean": true, "behavior": [], "parentObjectReference": "", "threatCategory": "THREAT_CATEGORY_UNSPECIFIED", "threatName": ""}]} |
Formatted JSON data (for easier readability)
{ |
Explanation of JSON Fields and dynamic scan result:
•deepScanStatus: Indicates the current status of the dynamic scan (see states above).
•behavior: Contains observed behavior during dynamic analysis. This field remains empty if the scan is pending or was not performed.
•deepScanExpectedEndTime: Shows when the dynamic scan is expected to finish; useful for determining when to check for final results.
•Other fields, such as objectReference, dataHashSha1, objectIsClean, and threatCategory, retain the same meanings as in static scanning, explained previously in section Performing a static scan.