Microsoft Remote Desktop Connection - Security
Security - More Information
Low data risk assessment:
The sensory data you and your panelists exchange with SensoryTest.com is all low risk.
There never needs to be any personal identifying information about your panelists or yourself - no names, no ss numbers,
no telephone numbers, no mailing addresses, no credit cards, no birth dates, etc. Your corporate IT Security department should
know this fact whenever they participate in your internal discussions.
Advantages of Microsoft Remote Desktop Web Connection:
- Totally safe, secure, Microsoft developed and certified.
- SSL/TLS Secured connections.
- Optional access to your local printers and files.
This document discusses Microsoft Remote Desktop Connection (RDC), Remote Desktop Protocol (RDP), Secure Sockets
Layer (SSL), and Transport Layer Security (TLS).
| Usage |
TCP port |
Encryption |
RDC client versions |
| Client.eSensory.com |
(default) 3389 |
Negotiate, SSL/TLS or RDP Security Layer encryption. |
5.1 (WinXP) |
| Client.eSensory.com:439 |
439 |
Negotiate, SSL/TLS or RDP Security Layer encryption. |
5.1 (WinXP) |
| Client.eSensory.com:443 |
443 |
Forced, SSL/TLS encryption only. |
5.2 (Win2k3), 6.x (WinXP/7) or 7.x (WinXP/Vista) |
| Client.eSensory.com:9443 |
9443 |
Forced, SSL/TLS encryption only. |
5.2 (Win2k3), 6.x (WinXP/7) or 7.x (WinXP/Vista) |
The Microsoft Remote Desktop Connection (RDC) and Remote Desktop Protocol (RDP) are
high-encryption secure connections which use RSA Security's RC4
cipher with the highest key strength of 128-bit. SensoryTest.com servers are configured to only support
the highest 128-bit RDP Security Layer encryption, or SSL/TLS. Anything less is not possible. Unlike some
other display protocols, which send data over the network using clear text or with an easily decodable
"scrambling" algorithm, RDP's built-in encryption makes it safe to use over any network, including
the Internet, as the protocol cannot be easily sniffed to discover passwords and other sensitive data.
The Microsoft Remote Desktop Connection provides remote display and input capabilities over network connections
for Windows-based applications running on a server. This is perfect for SIMS 2000 as the application running on
our servers, with your PC as the remote display.
The Microsoft Remote Desktop Connection is only used for outgoing connections initiated by you, the end user.
Microsoft Remote Desktop Connection should not be confused with Microsoft Remote Assistance inbound connections,
or with the similarly named Remote Desktop also only for inbound connections. Remote Assistance and Remote Desktop
are embedded within the XP operating system and are configured under Control Panel, System, Remote Tab. Again,
Microsoft Remote Desktop Connection is unrelated to Remote Assistance and Remote Desktop.
Microsoft Web Page Source for additional general information:
Microsoft's Remote Desktop Protocal
Microsoft Remote Desktop Connection Client Versions:
- Remote Desktop Connection (Terminal Services Client 7.0) for Windows XP & Vista, released Oct 26 2009
- MS WebPage - This version supports Server Authentication and therefore SSL/TLS
- Remote Desktop Connection (Terminal Services Client 6.1) for Windows XP, released Jun 25 2008
-
MS WebPage - This version supports Server Authentication and therefore SSL/TLS
- Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP, released Nov 28 2006
-
MS WebPage - This version supports Server Authentication and therefore SSL/TLS
- Windows XP Remote Desktop Connection version 5.1 [XPSP2 5.1.2600.2180]
-
MS WebPage - This version does **not** support Server Authentication or SSL/TLS
- Windows 2003 Remote Desktop Connection version 5.2 [Win2K3 5.2.3790.1830]
-
MS installer package - This version supports Server Authentication and therefore SSL/TLS, and can be installed in WinXP.
- This related
MS WebPage - states that RDC 5.2 is also supported for Windows 2000.
- Apple MAC OS X: Remote Desktop Connection Client for MAC 2.0.1
Microsoft Remote Desktop Web Connection:
- Good news. When you use our Web pages (and RDC Web connection) to connect to our servers,
we automatically make sure the versions are up to date and working perfectly, including full
SSL/TLS support for server authentication. We recommend using the Web Connection.
Enabling SSL/TLS:
- Requires RDC Web Connection, or RDC client version 5.2.
- Success can be verified after you press [Connect], the "Log On" screen should appear, see yellow
bar on very top, there should be a yellow lock, which you can now press for more information about
our SSL Secured Certificate.
Security information, Secure Sockets Layer (SSL), Transport Layer Security (TLS):
Computer port notes:
In addition to the ports mentioned above, we are able to enable
additional ports on our servers, please contact us as needed. Even on the tightest of firewalls,
your IT/IS staff can identify and allow port usage permission by internal IP address, Domain Computer,
and/or by User Policies, and allow port traffic as needed. Port traffic can also be further restricted
by only allowing traffic to our specific server URL/DNS Name.