What Makes I’m InTouch Remote Access So Secure?
No changes required on the firewall
I’m InTouch’s private portal architecture (US Patent #6,928,479) ensures no ports are being opened on the firewall when using any of our Remote Access features. In other words, there is no need to bypass or compromise the existing IT security established by the company resulting in an extremely secure connection.
Remote Wake-up architecture (patent-pending)
With our patent-pending remote wake-up feature users have the ability to remotely power-up their PCs or they can choose to “Shut Down” their PCs when leaving the office to conform to corporate security or environmental policy.
Computer Name, Login Name and Password are the first Layers of Security
Users at a remote location launch a browser and connect to the Location server at http://locator.01com.com. The user enters the Computer Name (set during registration) and secures the connection with SSL. A unique Computer Name is necessary to allow the Location server to establish a remote connection to the I’m InTouch “host” computer. One must then correctly input a further sequence of security - Login name and Password. The password can be
changed as often as the user wishes.
Login Name / Password are on the user’s PC, not on the Central Server:
Integrity of our users’ information is critical and we continually work to maintain
the highest degree of security possible for our customers. Both the Login name and Password are stored on the user’s computer and never passed on to any other server, thus protecting against un-authorized access.
Session is 100% secured by SSL encryption:
I’m InTouch supports Secure Socket Layer (SSL) 128 bit encryption for users. This ensures that the information being communicated over the Internet from the I’m InTouch PC to the Local computer is not visible to anyone except the authorized user.
Secure connection from the browser to the user’s PC
I’m InTouch operates through firewalls to allow secure remote access for users. It uses a unique “hybrid” architecture to achieve a secure connection. Users can freely choose between two secure methods at any time (with a single mouse click) to best fit their technical and work requirements:
1. Indirect communication session (through a central server)
2. Direct communication session (directly from the remote browser to the user’s PC)
Tags: Remote Access
Remote Access | 01 Communique | 14 April 2009 |
