Once your Halo order has been processed, if youโve opted to include the File Reputation feature, we will set up a new ReversingLabs account for you.
Note: you can also use an existing ReversingLabs account, provided you have the required credentials.
Please follow the steps below to configure Glasswall Halo with your ReversingLabs account.
Prerequisite
- Minimum Halo version: v2.4.15
Configure Glasswall Halo with ReversingLabs
Follow all the steps in the Deployment section to deploy Halo according to your cloud provider. The cdrplatform-engine includes the configuration needed to connect to ReversingLabs. The username and password should be set up using an external secret manager.
For any additional modifications, refer to the Halo Configuration Changes. The relevant settings can be found under the Engine section:
ReversingLabs__EndpointReversingLabs__Timeout
Retrieve threat intelligence data for your files
Single files
In the Sync API
In this example, we process a single file on the cdr-file endpoint on the Sync API.
-
Make a POST request with a single file to the Sync API, for example the cdr-file endpoint:
/api/v3/cdr-file. -
Observe the response headers, they should contain the following:
| Header | Description | Values |
|---|---|---|
| X-FileReputation-ResponseCode | The HTTP response code from the File Reputation service. |
|
| X-FileReputation-Status | Malware Presence Status |
|
| X-FileReputation-ThreatName | Detected threat name for the requested sample | (Example) Win32.Trojan.Nsis |
| X-FileReputation-ThreatLevel | Threat level is calculated by a proprietary ReversingLabs algorithm. It is a measure of how malicious a malware sample is. | A sampleโs Threat Level is expressed as a number from 0 to 5, with 5 indicating the most dangerous threats (highest severity). |
| X-FileReputation-TrustLevel | In samples classified as โknownโ, the trust level represents how confident we are that the sample is goodware. | It is computed by a proprietary ReversingLabs algorithm and expressed as a number from 0 to 5, where zero represents the highest confidence that a sample is goodware. |
Archives
In this example,we process a ZIP file on the cdr-file endpoint on the Sync API.
-
Make a POST request with a supported archive file to the Sync API, for example the cdr-file endpoint:
/api/v3/cdr-file. Ensure an Analysis report will be generated. -
Download the composite archive result containing the
/cleanand/reportfolders. -
Open the report archive file under the
/reportdirectory. -
Observe the contents of the
manifest.cdr-jsonfile. The JSON should contain a new sectionFileReputation.
{
"fileReputation": {
"response": "200",
"fileStatus": "SUSPICIOUS",
"threatName": "Win32.Trojan.Nsis",
"threatLevel": "4",
"trustLevel": "5"
}
}
Compressed files
For compressed files (.bz2 and .gzip), the file reputation data is returned via response headers (similar to single files).
Note: that the File Reputation results are for the underlying file and not the parent compressed type.