Schemas

Whether file-reputation lookups are enabled.

The Reversing Labs hash-lookup URL. The same for every appliance, owned by Halo and reported here for reference; no request accepts it.

The Reversing Labs username.

The lookup timeout in seconds (1-120 inclusive).

Whether a password is currently stored.

Whether the credential is held in a secret Halo cannot write (external-secrets owns it, or the Engine has no permission on it). A write that changes the password will be refused with a 409; the endpoint, timeout and enabled state are still writable.

How to update the credential out of band, when it is externally managed. Null otherwise.

Whether file-reputation lookups are enabled.

The lookup timeout in seconds. Must be between 1 and 120 inclusive when enabled is true, or when testing a connection; ignored by a write that sets enabled to false.

The Reversing Labs username.

The Reversing Labs password. Required on first configuration; blank on a subsequent save preserves the stored value. Never returned by any response.

Whether the connection test passed.

What the probe found. Passed and RateLimited are the two that pass. CredentialsRejected means the endpoint answered and refused the credentials. HostNotFound, ConnectionRefused, TlsFailure, Unreachable and TimedOut mean nothing usable answered, and each names a different reason. UnexpectedStatus means the endpoint answered with a status that is not a hash-lookup response. NotRun means the probe did not run and reason says why. Treat an unrecognised value as a failure described by reason.

The host that was probed. Null where no probe ran.

The status the endpoint answered with, where it answered at all.

The timeout the probe was bounded by.

The reason the test failed, when it did not pass.

Set when the test passed but something is nonetheless wrong, currently only an exhausted lookup allowance. Null on a clean pass and on any failure.

The provider's retry window in seconds, when it gave one.