All traffic that Remote Utilities sends over the network is encrypted. Encryption is always on and cannot be disabled by the user. The program uses a symmetric AES-256 algorithm for data encryption and an asymmetric RSA-2048 algorithm to secure the initial key exchange between Viewer and Host. For each new remote session, new AES and RSA keys are generated.
The access credentials data stored in Viewer address books can be encrypted in order to prevent unauthorized access to your remote access data if your computer is compromised. This is especially important if you save your access passwords in connection properties.
You can deploy and use Remote Utilities in a totally isolated environment — no communication with our servers is necessary:
Regardless of the authorization method you choose, blank passwords are not allowed. There are no default or technical passwords either. Only you and the people you authorize will know how to access the Host that you have installed.
Remote Utilities is protected against brute-force password cracking. Whenever there is an excessive number of incorrect password attempts, the system automatically begins to increase the amount of time required before each new attempt can be made.
Additionally, the system can algorithmically determine whether the Host is under brute-force attack and temporarily ban the originating IP address.
A persistent Host icon in the system tray informs the remote user that Remote Utilities is running on their computer. The program also appears in the process list. This ensures that the remote user can always stop or uninstall the Host, provided they have administrative privileges.
When enabled the Ask user permission option shows a message on the remote computer asking the remote user to accept or reject an incoming remote session request. Additionally, you can set a timeout and a default action to apply in case there is no one attending the remote PC. The request can be accepted or rejected automatically according to your settings.
With IP filtering enabled, you can restrict a remote Host and RU Server to accept incoming connections from certain IP addresses only.
A white list allows you to set trusted IP addresses whereas connections from all other IP addresses that do not fall in the trusted range will be declined. A black list allows connections to the given Host from all IP addresses or IP address ranges except the ones which you have explicitly blacklisted.
Protect the Host settings from modification by the remote user by locking the settings with a password. You can also hide the Host right-click menu so the menu won’t show when the Host icon is clicked.
A shared secret is an alphanumeric code that provides a means of verifying the identity of the Host. You can generate the shared secret in the Host settings, copy it and add it to the corresponding Viewer connection properties.
Every time a remote session is about to start, Remote Utilities will check the shared secrets on both ends (Viewer and Host). If they are not identical, the connection will be refused.