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 able to communicate over TLS 1.2 on the device but continue to experience issues with installing the Console, it is likely that the version of the .NET framework on the device does meet the minimum version (4.7.2) required.
Please Note: Microsoft has been working to stop use of TLS 1.1 since June of 2017. Recent updates to Windows 10 have disabled TLS 1.1 completely. So, the only way for Movere to communicate over TLS 1.1 back to the console machine from older versions of Windows that dont' support TLS 1.2 would be to run the Movere console from an older version of Windows that still supports TLS 1.1 (such as a copy of Winodws 10 without the Windows updates that disable TLS 1.1).