ReversingLabs file reputation is configured at runtime from the Halo **Portal** or the Halo **API**. This is the supported path on the OVA and other self-hosted appliances, where the appliance owns `cdrplatform-secrets` and the Engine writes the settings directly. A change is appliance-wide and takes effect without a restart.

## Configure from the Portal

1. Sign in to the Portal as an administrator.
2. Open **Settings** and select the **File reputation** tab.
3. Enter the ReversingLabs **endpoint**, **username** and **password**, and optionally a **timeout** in seconds (1–120, default 5). The endpoint is supplied by you; use:

   ```
   https://data.reversinglabs.com/api/databrowser/malware_presence/query
   ```

4. Select **Test connection** to verify the endpoint and credentials.
5. Turn ReversingLabs **on** and **Save**. Enabling requires a passing test.

## Configure from the Halo API

The same operations are available on the Halo API (administrator; `basic` or `bearer` auth):

- `GET /api/v1/reversing-labs/settings` — read the current settings. The password is never returned.
- `PUT /api/v1/reversing-labs/settings` — save the settings. Enabling is gated on a passing connection test; leave the password blank to keep the stored one.
- `POST /api/v1/reversing-labs/test-connection` — test a candidate endpoint and credentials without saving.