---
updatedAt: 2026-10-02T21:24:14.000Z
---

# Privileged Remote Access Glossary

<details class="banner"><summary>Looking for new Jump terminology?  Click here!</summary>

This table identifies former **Jump** terms and what they are called today:

<HTMLBlock>{`
<table style="color: black !important">
<thead>
  <tr style="background: var(--bt-cloud) !important; color: black !important">
    <th style="width: 50%">Previous Term</th>
    <th style="width: 50%">New Term</th>    
  </tr>
</thead>
<tbody style="font-weight: 100 !important; background: var(--bt-cloud) !important">
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Jump Item</b></td>
    <td><b>Asset</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>External Jump Item</b></td>
    <td><b>External Asset</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Jump Group</b></td>
    <td><b>Asset Group</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Jump Policy</b></td>
    <td><b>Asset Policy</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Jump Item Role</b></td>
    <td><b>Asset Role</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Jumpoint</b></td>
    <td><b>Gateway</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Jump Session</b></td>
    <td><b>Session</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Jump Shortcut</b></td>
    <td><b>Asset</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Jump Zone Proxy</b></td>
    <td><b>Proxy</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Jump Method Types</b></td>
    <td><b>Replaced with the specific method type (e.g.; RDP, SSH, MySQL, TCP, etc)</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Jump Method</b></td>
    <td><b>Connection Type</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Shell Jump</b></td>
    <td><b>Shell</b></td>
  </tr>
  <tr style="background: var(--bt-cloud) !important">
    <td><b>Web Jump</b></td>
    <td><b>Website</b></td>
  </tr>
</tbody>
</table>
`}</HTMLBlock>

<Callout icon="ℹ️" theme="info">
  <span style="color:white">Jump Client remains as is. It is already a familiar and widely used term.</span>
</Callout>

</details>

The following is an alphabetical list of product-specific terms with their descriptions.

<Tabs>
  <Tab title="A - B">
    <table>
      <thead>
        <tr>
          <th>Term</th>
          <th>Definition</th>
        </tr>
      </thead>
      <tbody>    
        <tr>
          <td><b>Account Groups</b></td>
          <td>Logical groupings of accounts used to simplify permission assignment, policy enforcement, and access management.</td>
        </tr>
        <tr>
          <td><b>Account Policies</b></td>
          <td>Rules that govern how accounts are managed and accessed, including security requirements and usage constraints.</td>
        </tr>
        <tr>
          <td><b>Application Programming Interface (API)</b></td>
          <td>An <b>API</b> is a programming interface provided for automation tools and external applications.</td>
        </tr>
        <tr>
          <td><b>API Configuration</b></td>
          <td>Settings that enable and control access to the Remote Support API for integrations and automation.</td>
        </tr>
        <tr>
          <td><b>Appliance</b></td>
          <td>The BeyondTrust platform component (physical or virtual) that hosts and runs Remote Support services.</td>
        </tr>
        <tr>
          <td><b>Appliance Administration</b></td>
          <td>Administrative controls used to manage appliance-level settings, maintenance tasks, and operational status.</td>
        </tr>
        <tr>
          <td><b>Asset (formerly known as Jump Item)</b></td>
          <td>Individual systems or devices that are made available for remote access within an <b>Asset Group</b>, enabling administrators to organize and control access to remote systems in a secure manner.</td>
        </tr>
        <tr>
          <td><b>Asset Group (formerly known as Jump Group)</b></td>
          <td>A collection of Assets. Asset Groups can be used to organize Assets in any manner that works for your organization. For example, servers could be organized in geographic, departmental, or team Asset Groups. Asset Groups can also be used to manage access. For example, one set of Jump Clients could be accessible by the help desk team, while another set is accessible by the network team.</td>
        </tr>
        <tr>
          <td><b>Asset Policy (formerly known as Jump Policy)</b></td>
          <td>Used to control access to Assets. For example, access might be restricted to specific hours. Asset Policies can be applied to individual Assets or Asset Groups.</td>
        </tr>
        <tr>
          <td><b>Asset Reports</b></td>
          <td>Reports detailing usage, configuration, and activity related to Assets.</td>
        </tr>
        <tr>
          <td><b>Asset Role (formerly known as Jump Item Role)</b></td>
          <td>a predefined set of permissions regarding Asset management and usage. You assign users to an Asset or an Asset Group either through Group Policies or by adding individual users. You can set an individual user's permissions to specific Assets in a group, or the entire group.</td>
        </tr>
        <tr>
          <td><b>Atlas in the Cloud</b></td>
          <td><b>Atlas in the Cloud</b> is a cloud-based extension of BeyondTrust's Atlas technology designed for large enterprises needing more concurrent sessions than a single B Series Appliance can support. It distributes load across multiple appliances in different geographic locations.</td>
        </tr>
        <tr>
          <td><b>B Series Appliance</b></td>
          <td>A BeyondTrust hardware or virtual appliance that acts as the central communication point for secure remote access, handling session brokering, authentication, logging, auditing, and encryption for Privileged Remote Access deployments.</td>
        </tr>
        <tr>
          <td><b>B Series Appliance On-Premises Security</b></td>
          <td>The security model for B Series Appliances deployed in customer-controlled environments, including secure protocols, directory integration, session recording, auditing, and local data control.</td>
        </tr>
        <tr>
          <td><b>Base (Component of B Series Appliance)</b></td>
          <td>Firmware providing system-level configuration (IP addresses, certificates). Managed through the /appliance web interface.</td>
        </tr>
        <tr>
          <td><b>BeyondTrust Cloud Region Availability</b></td>
          <td>A listing of the geographic cloud regions where BeyondTrust cloud services can be deployed to meet data residency, compliance, and latency requirements.</td>
        </tr>
      </tbody>
    </table>
  </Tab>
  <Tab title="C - D">
    <table>
      <thead>
        <tr>
          <th>Term</th>
          <th>Definition</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td><b>Canned Scripts</b></td>
          <td>Predefined scripts that can be executed during remote sessions to automate common or repetitive tasks.</td>
        </tr>
        <tr>
          <td><b>Cloud Network Infrastructure</b></td>
          <td><b>Cloud Network Infrastructure</b> explains how BeyondTrust Secure Remote Access (SRA) operates within the SRA Cloud instance to ensure secure and efficient communication between application components. The cloud acts as the central routing point where all user and remote sessions occur through B Series Appliance server components.</td>
        </tr>
        <tr>
          <td><b>Compliance Reports</b></td>
          <td>Reports that provide audit-ready data to help demonstrate adherence to regulatory and security requirements.</td>
        </tr>
        <tr>
          <td><b>Connect to</b></td>
          <td><b>Connect to</b>, <b>Push and Start</b>, and <b>Pushed Sessions</b> refer to BeyondTrust sessions started from either Gateways or Local Jumps, without distinction. Thus, a pushed session can refer to either of these technologies but not to Jump Client sessions or pinned sessions. Similarly, Push and Start and connect to can refer to either connecting through a Gateway or a Local Jump but not to connecting to a Jump Client.</td>
        </tr>
        <tr>
          <td><b>Configuration</b></td>
          <td>Settings used to customize how Privileged Remote Access operates, including system behavior and feature enablement.</td>
        </tr>
        <tr>
          <td><b>Console Settings</b></td>
          <td>Configuration options that control the behavior and appearance of the Privileged Remote Access access console.</td>
        </tr>
        <tr>
          <td><b>Consoles &amp; Downloads</b></td>
          <td>A centralized area where users obtain access consoles, clients, and related software downloads.</td>
        </tr>
        <tr>
          <td><b>Credential Injection</b></td>
          <td>A built-in SRA feature for injecting credentials into systems without exposing passwords, compatible with third party vaults.</td>
        </tr>
        <tr>
          <td><b>Custom Fields</b></td>
          <td>User-defined metadata fields that extend standard objects for tracking additional information.</td>
        </tr>
        <tr>
          <td><b>Custom Links</b></td>
          <td>Administrator-defined links added to the console to provide quick access to external or internal resources.</td>
        </tr>
        <tr>
          <td><b>Discovery</b></td>
          <td>Processes used to identify systems, services, or credentials that can be managed by Privileged Remote Access.</td>
        </tr>
        <tr>
          <td><b>Drivers</b></td>
          <td>Software components required to support specific remote access or device communication functions.</td>
        </tr>
        <tr>
          <td><b>Duplicate Jump Clients Report</b></td>
          <td>A report that identifies multiple Jump Clients installed on the same endpoint.</td>
        </tr>
      </tbody>
    </table>
  </Tab>
  <Tab title="E - H">
    <table>
      <thead>
        <tr>
          <th>Term</th>
          <th>Definition</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td><b>Endpoint</b></td>
          <td>Any remote computer or device residing on a network. This can include: Windows desktops, laptops, and servers; MacOS and iOS devices; Linux systems; Android phones and tablets; Search- and Telnet-enabled devices such as Cisco switches or BeyondTrust B Series Appliances.</td>
        </tr>
        <tr>
          <td><b>Endpoint Automation</b></td>
          <td>Automation capabilities that allow predefined actions or scripts to run against managed endpoints.</td>
        </tr>
        <tr>
          <td><b>Endpoint Credential Manager (ECM)</b></td>
          <td>An ECM functions as the middleware for communication, and the ECM can be used to integrate SRA with password vaults.</td>
        </tr>
        <tr>
          <td><b>Entitle</b></td>
          <td><b>Entitle</b> is a solution that enables temporary provisioning of access to implement JIT access, reducing exposure from inactive but privileged accounts.</td>
        </tr>
        <tr>
          <td><b>Gateway (formerly known as Jumpoint)</b></td>
          <td>A secure connection point used in Remote Support to facilitate access to remote systems without requiring direct public internet exposure, enabling secure, controlled remote sessions. A Gateway allows administrators to securely manage remote connections through internal networks or firewalls, ensuring protected access to remote systems while maintaining network security. Users can access computers on a remote network without having to pre-install software on every machine. Install a single Gateway agent at any network location to gain unattended access to every PC within that network. Deploy a Gateway if you need: To troubleshoot all systems in a network without pre-deploying BeyondTrust clients on each system prior to connecting; Access to SSH, Telnet, or vPro systems on that network, like servers, routers, POS systems, or ATMs; To run Microsoft Remote Desktop Protocol sessions while maintaining a consistent audit trail.</td>
        </tr>
        <tr>
          <td><b>Group Policies</b></td>
          <td>Policies applied to groups to control access rights, session behavior, and security enforcement.</td>
        </tr>
        <tr>
          <td><b>Hosting Locations and Disaster Recovery</b></td>
          <td>Documentation describing where BeyondTrust cloud services are hosted and how redundancy, backups, and disaster recovery are implemented.</td>
        </tr>
      </tbody>
    </table>
  </Tab>
  <Tab title="I - L">
    <table>
      <thead>
        <tr>
          <th>Term</th>
          <th>Definition</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td><b>Insights</b></td>
          <td>A solution that increases visibility into identities holding potentially risky permissions. It continuously detects and evaluates these identities to provide clearer context on who has access to what, and why.</td>
        </tr>
        <tr>
          <td><b>Installed Patches</b></td>
          <td>A listing of patches currently applied to the Remote Support system.</td>
        </tr>
        <tr>
          <td><b>Jump</b></td>
          <td>Enables secure, unattended access to remote systems.</td>
        </tr>
        <tr>
          <td><b>Jump Client</b></td>
          <td>used to establish a one-to-one encrypted connection between a B Series Appliance and a remote Windows, Mac, Android, or Linux system. A Jump Client must be installed on each remote system you want to access. The installed Jump Clients to which a representative has permission are listed in the bottom pane of the representative console. Jump Clients are state-aware, which means they can determine if a user is present and interact accordingly. They can also be set to automatically uninstall, to meet compliance requirements. Deploy a Jump Client if you need: Attended or unattended access to computers and other devices, regardless of network location; Stronger management capacities and the control of installing a persistent and secure remote access client.</td>
        </tr>
        <tr>
          <td><b>Lightweight Directory Access Protocol (LDAP)</b></td>
          <td><b>LDAP</b> is an external user directory that SRA can connect to for secure user management.</td>
        </tr>
        <tr>
          <td><b>Local Jump (or Local Push)</b></td>
          <td>Connecting from the representative console using the local network. This allows a representative to initiate a BeyondTrust session with Windows systems on the same network segment as the representative console, without using a Gateway. The requirements on the endpoint being assessed and the functionality for Local Jumps are the same as for Remote Jumps with Gateways.</td>
        </tr>
        <tr>
          <td><b>Log Session ID (LSID)</b></td>
          <td>A 32 character GUID that uniquely identifies each SRA session log.</td>
        </tr>
      </tbody>
    </table>
  </Tab>
  <Tab title="M - P">
    <table>
      <thead>
        <tr>
          <th>Term</th>
          <th>Definition</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td><b>Modern Privileged Access Management (Modern PAM)</b></td>
          <td>BeyondTrust's approach to PAM that combines identity risk insights, automated least-privilege access, and secure remote access across hybrid and cloud environments.</td>
        </tr>
        <tr>
          <td><b>My Account</b></td>
          <td>User-specific settings related to profile information and personal preferences.</td>
        </tr>
        <tr>
          <td><b>Options</b></td>
          <td>General configuration settings that affect system behavior and feature availability.</td>
        </tr>
        <tr>
          <td><b>Outbound Events</b></td>
          <td>Events generated by the system and sent to external systems for monitoring or integration.</td>
        </tr>
        <tr>
          <td><b>Privileged Access Management (PAM)</b></td>
          <td><b>PAM</b> is the larger set of solutions under which PRA operates. While the document does not provide a full definition, it identifies PAM as the overarching suite that includes PRA.</td>
        </tr>
        <tr>
          <td><b>Primary Node</b></td>
          <td>A <b>Primary Node</b> is the main configuration point for an SRA site. It hosts the /login administrative interface, initiates sessions, and automatically pushes configuration settings to traffic nodes.</td>
        </tr>
        <tr>
          <td><b>Push and Start</b></td>
          <td><b>Connect to</b>, <b>Push and Start</b>, and <b>Pushed Sessions</b> refer to BeyondTrust sessions started from either Gateways or Local Jumps, without distinction. Thus, a pushed session can refer to either of these technologies but not to Jump Client sessions or pinned sessions. Similarly, Push and Start and connect to can refer to either connecting through a Gateway or a Local Jump but not to connecting to a Jump Client.</td>
        </tr>
        <tr>
          <td><b>Pushed Sessions</b></td>
          <td><b>Connect to</b>, <b>Push and Start</b>, and <b>Pushed Sessions</b> refer to BeyondTrust sessions started from either Gateways or Local Jumps, without distinction. Thus, a pushed session can refer to either of these technologies but not to Jump Client sessions or pinned sessions. Similarly, Push and Start and connect to can refer to either connecting through a Gateway or a Local Jump but not to connecting to a Jump Client.</td>
        </tr>
      </tbody>
    </table>
  </Tab>
  <Tab title="Q - T">
    <table>
      <thead>
        <tr>
          <th>Term</th>
          <th>Definition</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td><b>Reports</b></td>
          <td>A collection of reporting tools that provide visibility into system activity and usage.</td>
        </tr>
				<tr>
          <td><b>Representative Invite</b></td>
          <td>A mechanism used to invite users or external parties to access Remote Support with defined permissions and security controls.</td>
        </tr>
        <tr>
          <td><b>Secret Store</b></td>
          <td>A secure storage location for sensitive credentials and secrets managed by PRA.</td>
        </tr>
        <tr>
          <td><b>Security</b></td>
          <td>Controls and settings that protect access, sessions, and system integrity.</td>
        </tr>
        <tr>
          <td><b>Security Providers</b></td>
          <td>External services integrated to support authentication, authorization, or identity management.</td>
        </tr>
        <tr>
          <td><b>Services</b></td>
          <td>Managed services or service accounts available within Privileged Remote Access.</td>
        </tr>
        <tr>
          <td><b>Session Policies</b></td>
          <td>Rules that govern how remote sessions are conducted, including permissions and restrictions.</td>
        </tr>
        <tr>
          <td><b>Site Configuration</b></td>
          <td>Settings that define site-wide behavior and operational parameters.</td>
        </tr>
        <tr>
          <td><b>SSH Certificate Authority in Vault Accounts</b></td>
          <td>A capability that allows Vault to act as a certificate authority for SSH authentication.</td>
        </tr>
        <tr>
          <td><b>Status</b></td>
          <td>System health and operational indicators for Privileged Remote Access components.</td>
        </tr>
        <tr>
          <td><b>Syslog Reports</b></td>
          <td>Reports that capture and present system events forwarded via syslog.</td>
        </tr>
        <tr>
          <td><b>Teams</b></td>
          <td>Collections of users organized to simplify access control and responsibility assignment.</td>
        </tr>
        <tr>
          <td><b>TLS Configuration</b></td>
          <td>Settings that control Transport Layer Security behavior for encrypted communications.</td>
        </tr>
        <tr>
          <td><b>Secure Remote Access (SRA)</b></td>
          <td><strong>SRA</strong> is a secure access solution that lets organizations control access to critical systems without hindering privileged users. Allows defining how users connect, monitoring sessions in real time, and recording every session for detailed auditing.</td>
        </tr>
        <tr>
          <td><strong>Traffic Node</strong></td>
          <td>A node in a clustered SRA environment that handles session traffic. It cannot be added/edited/removed by the customer; it uses (customerID)-region.beyondtrustcloud.com for routing.</td>
        </tr>
      </tbody>
    </table>
  </Tab>
  <Tab title="U - Z">
    <table>
      <thead>
        <tr>
          <th>Term</th>
          <th>Definition</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td><b>Updates</b></td>
          <td>Processes used to apply software updates and enhancements to the system.</td>
        </tr>
        <tr>
          <td><b>Users</b></td>
          <td>Individuals or accounts authorized to access Privileged Remote Access.</td>
        </tr>
        <tr>
          <td><b>User Management</b></td>
          <td>Administrative functions for creating, modifying, and controlling user accounts.</td>
        </tr>
        <tr>
          <td><b>User Permissions</b></td>
          <td>Access rights assigned to users that determine what actions they can perform.</td>
        </tr>
        <tr>
          <td><b>Vault</b></td>
          <td>A secure credential management component used to store and control access to secrets.</td>
        </tr>
        <tr>
          <td><b>Vault Reports</b></td>
          <td>Reports focused on credential usage, access history, and Vault activity.</td>
        </tr>
        <tr>
          <td><b>Vendors</b></td>
          <td>External users or third parties granted controlled access through Privileged Remote Access.</td>
        </tr>
        <tr>
          <td><b>Vendor Reports</b></td>
          <td>Reports that track activity and access associated with vendor accounts.</td>
        </tr>
        <tr>
          <td><b>Video Session Recording</b></td>
          <td>Captures the visible endpoint screen for the duration of the session, including metadata on input control.</td>
        </tr>
        <tr>
          <td><strong>Vulnerability Scanning</strong></td>
          <td>Part of BeyondTrust's testing process to identify security vulnerabilities before release. Critical findings trigger maintenance releases; third party code review &amp; penetration testing validate controls.</td>
        </tr>
        <tr>
          <td><strong>Zero standing Access</strong></td>
          <td><strong>Zero standing Access</strong> is a security approach where permissions are automatically removed from accounts when not actively used, following just in time (JIT) access principles.</td>
        </tr>
      </tbody>
    </table>
  </Tab>
</Tabs>