Remote Access Tools Policy

1. Overview

Remote desktop software, also known as remote access tools, provides a way for computer users and support staff alike to share screens, access work computer systems from home, and vice versa. Examples of such software include LogMeIn, GoToMyPC, VNC (Virtual Network Computing), and Windows Remote Desktop (RDP). While these tools can save significant time and money by eliminating travel and enabling collaboration, they also provide a back door into the eCuras network that can be used for theft of, unauthorized access to, or destruction of assets. As a result, only approved, monitored, and properly controlled remote access tools may be used on eCuras computer systems.

2. Purpose

This policy defines the requirements for remote access tools used at eCuras.

3. Scope

This policy applies to all remote access where either end of the communication terminates at a eCuras computer asset.

4. Policy

All remote access tools used to communicate between eCuras assets and other systems must comply with the following policy requirements.

4.1 Remote Access Tools

eCuras provides mechanisms to collaborate between internal users, with external partners, and from non-eCuras systems. The approved software list can be obtained from <link-to-approved-remote-access-software-list>. Because proper configuration is vital for the secure use of these tools, mandatory configuration procedures are provided for each of the approved tools.

The approved software list may change at any time, but the following requirements will be used for selecting approved products:

All remote access tools or systems that allow communication to eCuras resources from the Internet or external partner systems must require multi-factor authentication. Examples include authentication tokens and smart cards that require an additional PIN or password.
The authentication database source must be Active Directory or LDAP, and the authentication protocol must involve a challenge-response protocol that is not susceptible to replay attacks. The remote access tool must mutually authenticate both ends of the session.
Remote access tools must support the eCuras application layer proxy rather than direct connections through the perimeter firewall(s).
Remote access tools must support strong, end-to-end encryption of the remote access communication channels specified in the eCuras network encryption protocols policy.
All eCuras antivirus, data loss prevention, and other security systems must not be disabled, interfered with, or circumvented in any way.

All remote access tools must be purchased through the standard eCuras procurement process, and the information technology group must approve the purchase.

5. Policy Compliance

5.1 Compliance Measurement

The Infosec team will verify compliance with this policy through various methods, including but not limited to periodic walk-thrus, video monitoring, business tool reports, internal and external audits, and feedback to the policy owner.

5.2 Exceptions

The Infosec Team must approve any exception to the policy in advance.

5.3 Non-Compliance

An employee found to have violated this policy may be subject to disciplinary action, up to and including termination of employment.

Revised: March 14th, 2018

1. Overview

2. Purpose

3. Scope

4. Policy

5. Policy Compliance

Table of Content