Simply put, SecureLink helps you get the most out of your enterprise software. It is like having a service engineer on-site without buying a plane ticket. By authorizing a secure connection, you give the service engineer direct (restricted) access to the supported software application and get your problems resolved more quickly. This results in less downtime for you, so you can get back to using your enterprise software application without worrying about support. The service engineer can directly access log files and configuration settings without placing a burden on your IT department. With SecureLink, there's never a need to chase a log-file, open a hole in your firewall, deal with IT, create a vendor log-in, or surrender control of your PC while the service engineer works. In addition, you will appreciate SecureLink's enhanced security, real time monitoring, and historical audit capabilities.

SecureLink has been reviewed, approved, and is in use by companies in high-security industries, including some of the largest financial institutions in the world, healthcare and insurance providers, government entities, and even the United States military.

You only need the ability to install the application on a server of your choosing. The Gatekeeper may also be installed on a desktop, although this may limit some of the built-in functionality.

Yes, although it may limit some of the built-in services.

Only the SecureLink Gatekeeper and any standard browser are required.

No. SecureLink is designed to give the service engineer direct access to the service issue without requiring you to give up your desktop. Unless the service engineer needs control of your desktop for some reason, you will not have to give up your machine.

Screen-sharing may be an adequate choice for supporting end-user, desktop applications. One of the problems with screen-sharing for enterprise software support is that you can't regulate the level of access granted. Either the remote user has too much access, such as the ability to snoop the network or access personal and sensitive information, or not enough access, such as the ability to natively access the services running on the vendor's server. Another problem is that the software engineer is limited in his or her choice of resolution tools. For a more thorough discussion, view our SecureLink vs. Screen-sharing White Paper.

Giving a software vendor a VPN account may take weeks or months to accomplish. Then, you must maintain that account, making sure it's not being used without permission. SecureLink is like an on demand VPN without the infrastructure, administration of log-ins and passwords, and the maintenance and management headaches. Additionally, SecureLink offers better reporting capabilities and the ability to limit access on a port-by-port basis. For a more thorough discussion, view our SecureLink vs. VPN White Paper.

SecureLink only requires a small component on one of your software vendor's servers. If it hasn't been pre-bundled, simply go to securelink.yourvendorsname.com and follow the instructions. This should take no more than 5 minutes.

No. The Gatekeeper only needs to reside on a single server.

The SecureLink Gatekeeper can be configured to be �always on� or manually started.

Simply open any browser and point to the SecureLink Gatekeeper. This can be done from anywhere in your network with client access to the server where the Gatekeeper is running. This will prompt you to enter a security key, which is randomly generated by the SecureLink server and conveyed to you. Upon entering the security key, an outbound, encrypted tunnel is formed between your server and the SecureLink server in your software vendor's support center. For a more thorough explanation, view our Flash Demo or our SecureLink Overview White Paper.

SecureLink has real-time monitoring capabilities and also leaves behind a detailed historical audit report.

The connection can be ended at any time with a single mouse click.

Each connection is initiated by you, never from the outside. Essentially, you're tunneling into the vendor's support center so they can fix their system. The session requires a random, one-time-use key that's generated by the SecureLink server at your software vendor's support center and entered by you. This key is good for a single use, and you must authorize and authenticate each session.

You are always in control. The service engineer can access only the services you permit, which can be defined at a very granular (port) level. For example, you can restrict access to read-only to a particular directory. For more complex issues, the service engineer may request access to additional ports, like diagnostic services and databases, but you're always in complete control of access.

Yes. SecureLink can be configured to require a user and admin password to attempt to request a connection or change administrative settings.

Yes. We allow multiple encryption options including 128-bit AES, 256-bit AES, Triple DES (3DES), and Blowfish.

A connection can be initiated by any browser inside your network that has client access to the machine where the Gatekeeper is installed.

No. While waiting for a connection request, the Gatekeeper is about 3K, runs as a very thin client background service, and can be shut off until needed if you prefer.

If you have any level of internet access, you will not have to modify your firewall. SecureLink first tries to connect on port 22 (SSH) for speed and efficiency. If 22 is not available outbound, SecureLink will follow a negotiation process all the way up to Port 80 via a Proxy server requiring authentication.