All communications between Movere and the Movere Console, including token download and payload upload, and user interactions with the Movere website, are performed over a TLS 1.2 connection. The only exception is when scanning older Windows systems, (e.g. Windows 2003/XP, which do not support TLS 1.2). When scanning a device locally, Movere encrypts the data it collects in memory before being transferred. As these operating systems do not support TLS 1.2, Movere has no way of enforcing it. If the automatic upload option is selected and these older Windows systems cannot communicate back to the Movere Console, they will send their payloads to Movere over a non-TLS 1.2 connection. The payload itself is PGP-encrypted, but if all communications must occur over a TLS 1.2 connection, all payloads should be sent to Movere via the Movere Console.
Why won’t TLS 1.2 work to download console?
Movere uses TLS 1.2 to communicate from the console and bots back to the Movere Cloud. If you are only able to communicate using other than TLS 1.2 then it is likely that the .NET framework on the device being used to download the console does not have the minimum version of the .NET framework (4.5.2) required.