Jump Policies

What are Jump Policies?

Jump Policies are configurations that control the access schedule for Jump Items, determining when they can be accessed.

How are Jump Policies useful in Remote Support?

Jump Policies allow administrators to manage when certain Jump Items are available, ensuring that access aligns with organizational needs, security requirements, or specific time frames. This helps in maintaining control and compliance over remote access activities.

How do I access the Jump Policies page?

1. Use a Chromium-based browser to sign in to your Remote Support URL.
   This URL is provided in the BeyondTrust welcome email and includes your site URL followed by /login.
2. From the left menu, click Jump.
   The Jump Clients page opens and displays by default.
3. At the top of the page, click Jump Policies.
   The Jump Policies page displays.

Add, edit, delete

Create a new policy, modify an existing policy, or remove an existing policy.

Add or edit a policy

Display name

Create a unique name to help identify this policy. This name should help users identify this policy when assigning it to Jump Clients.

Code name

Set a code name for integration purposes. If you do not set a code name, one is created automatically.

Description

Add a brief description to summarize the purpose of this policy.

Jump Schedule: enabled

Set a schedule to define when Jump Items under this policy can be accessed. Set the time zone you want to use for this schedule, and then add one or more schedule entries. For each entry, set the start day and time and the end day and time.

If, for instance, the time is set to start at 8 PM and end at 5 PM, a user can start a session using this Jump Item at any time during this window but may continue to work past the set end time. Attempting to re-access this Jump Item after 5 PM, however, results in a notification that the schedule does not permit a session to start. If necessary, the user may choose to override the schedule restriction and start the session anyway.

Force session to end when schedule does not permit access

If stricter access control is required, check Force session to end when schedule does not permit access. This forces the session to disconnect at the scheduled end time. In this case, the user receives recurring notifications beginning 15 minutes prior to being disconnected.

Ticket system

Check to Require a ticket ID before a session starts.

Two factor authentication challenge

For additional security, the Jump Policy can require an end-user to confirm their identity using a multi-factor authentication challenge before starting or elevating a session. Check to require this.

Simultaneous Jumps

For Jump Client, Local Jump, Remote Jump, Local VNC, Remote VNC, Intel vPro

If this option is set to Use Global Setting, then the simultaneous Jump setting configured on Jump > Jump Items > Jump Item Settings will be used.

Set this option to Join Existing Session to provide a way for multiple users to gain access to the same Jump Item without an invitation to join an active session by another user. The first user to access the Jump Item maintains ownership of the session. Users in a shared Jump session see each other and can chat.

If Join Existing Session is selected, there is an option to apply the setting to copies of Jump Clients.

• If checked, a user can join a session that was started from another copy of a Jump Client in a different Jump Group. Session permissions are based on the original Jump Client that started the session.
• If not checked, a user cannot join a session that was started from another copy of a Jump Client, unless it is the same Jump Group.

Set this option to Disallow Jump to ensure only one user can Jump to a Jump Item at a time. Only an invitation by the user who originated the session can allow for a second user to access the session.

For Remote RDP, Local RDP

If this option is set to Use Global Setting, then the simultaneous Jump setting configured on Jump > Jump Items > Jump Item Settings will be used.

Set this option to Start New Session to provide a way for multiple users to gain access to the same Jump Item without an invitation to join an active session by another user. For RDP, multiple users may gain access to a Jump Item, but each starts an independent session.

Set this option to Disallow Jump to ensure only one user at a time can Jump to a Jump Item. Only an invitation by the user who originated the session can allow for a second user to access the session.