How to secure remote desktop management in Desktop Central ?

How to secure remote desktop management in Desktop Central ?

I have a question, how to secure remote desktop management in Desktop Central. How does an installed agent on remote user computer verify that it is connecting to the correct Desktop Central server?

 

To verify that, I performed the following test

 

I created a Desktop Central server that was available under the public IP address [1.1.1.1], and at the FQDN desktopcentral.example.com [1.1.1.1], On client computers I installed an agent that communicated with the central desktop server. Everything worked properly

 

To verify whether it is possible to take complete control over the client computer, I decided to install an additional Desktop Central server, let's call it "evil". The server was available under the public ip address [2.2.2.2].

 

Then, on the client computer I made a change to the local HOSTS file, I changed desktopcentral.example.com from ip address [1.1.1.1] to ip [2.2.2.2]. After changing and rebooting the client computer, this connects to the “evil” desktop central server without verifying that it is a valid server for managing this agent. I took complete control of the client computer using the “evil”  desktop central server.

Is it possible to secure agent computers to only connect to dedicated servers?
              New to ADManager Plus?

                New to ADSelfService Plus?