GATEWAY GUIDE | RS

What is Jump technology?

With BeyondTrust Jump Technology, authorized users can securely access and control remote computers, attended and unattended, as well as switches and other network devices in any network. Jump Technology is integral to the BeyondTrust software offerings. All sessions are logged for reporting and auditing. Because BeyondTrust Remote Support is licensed per active representative and not per remote system, Jump Technology is a cost-effective way to reach every device in your enterprise.

What is a Gateway?

A Gateway acts as a conduit for access to computers on a known remote network. A single Gateway installed on a computer within a LAN is used to access multiple systems, eliminating the need to pre-install software on every computer you might need to access.

How are Gateways and Jump technology useful?

Within a LAN, the BeyondTrust user's computer can initiate a session to a system directly without using a Gateway, if appropriate user permissions are enabled. This is called a Local Jump. A Gateway is needed only for a Remote Jump when the BeyondTrust user's computer cannot access the target computer directly.

ℹ️

For more information on Assets for mobile devices, see the following:

• Use Assets to Access Unattended Computers from the Android Representative Console
• Use Jump Clients to Access Unattended Computers from the Android Representative Console
• Use Assets to Access Unattended Computers from the iOS Representative Console
• Use Jump Clients to Access Unattended Computers from the iOS Representative Console

Recommended steps for implementing BeyondTrust Gateways

When working with Jump Technology, there are a lot of moving parts. Here is a recommended order of implementation to make full use of your software.

1. Add Asset Roles. Asset Roles determine how users are allowed to interact with Assets. These roles are applied to users by means of individual account settings, group policies, and when added to Asset Groups.
2. Add Asset Policies. Asset Policies are used to control when certain Assets can be accessed by implementing schedules. Asset Policies are applied to Assets upon creation and can be modified from the representative console.
3. Add Asset Groups. An Asset Group is a way to organize Assets, granting members varying levels of access to those items. Users are assigned to Asset Groups either individually, by means of group policy.
4. Deploy Gateways. A Gateway acts as a conduit for unattended access to computers on a known remote network. A Gateway is necessary to use Remote Jumps, Remote RDP, Remote VNC, SSH sessions, and Intel® vPro sessions. Local Jumps, Local RDP, and Local VNC can be performed to systems on the same local network.
5. Create Assets. An Asset is a quick way to start sessions with frequently accessed remote systems. Assets are created from the representative console or are imported from /login > Asset Management > Assets. When creating or importing Assets, be sure to set the Asset Group and Asset Policy to determine who can access the Asset and with what restrictions.