Remote access should be simple for the person connecting. They sign in, find the workstation or resource they need, and get to work.
But behind that simple experience, several important decisions need to happen. Who is the user? What are they authorized to access? How should the connection be established? And how does IT maintain visibility and control without giving users unnecessary access to the corporate network?
These are the challenges Leostream Cloud is designed to address.
Leostream Cloud provides a cloud-hosted management plane that connects authorized users to individual workstations and protected resources. It brings identity-based access control, resource assignments, and connection management together in one place.
To understand what that means in practice, let’s follow a typical remote employee through the connection process.
Step 1: The Employee Signs In
Imagine an engineer working from home who needs access to a powerful workstation located in the office.
The workstation has the applications, processing power, and data the engineer needs. There’s no reason to move those resources to a laptop or give the engineer broad connectivity to the corporate network.
Instead, the engineer opens the Leostream Cloud access portal and signs in.
Leostream Cloud supports integration with enterprise identity providers using SAML or OpenID Connect (OIDC). This allows organizations to use existing identity systems and multifactor authentication (MFA) to verify users.
From the employee’s perspective, the experience is familiar. They authenticate using the credentials and security requirements established by their organization.
For IT, this means remote access can work alongside existing identity management practices without requiring an entirely separate authentication process.
Step 2: Leostream Cloud Determines What the User Can Access
Once the engineer is authenticated, Leostream Cloud determines which resources they’re authorized to use.
This is where identity-based access control comes into play.
Rather than providing connectivity to an entire network, Leostream Cloud uses administrator-configured access rules and resource assignments to determine which workstations or protected resources are available to the user.
For example, the engineer may be authorized to access a specific GPU workstation in the office. A contractor working on the same project might have access to a different machine, while an IT administrator could have permission to connect to several systems.
Each user has access based on their assigned permissions.
This is an important distinction from traditional VPN-based access. The employee doesn’t need to connect to the corporate network and navigate to the appropriate machine. Leostream Cloud provides a direct path to the resources they’re permitted to use.
Step 3: The Employee Selects a Resource
After signing in, the engineer sees the resources available to them.
In our example, that might be a single engineering workstation. For another employee, it could be several authorized desktops or systems.
The user selects the resource they want to access.
The experience is straightforward because the complexity of managing resource access happens behind the scenes.
IT has already configured which users can connect to which resources, allowing employees to focus on their work rather than the underlying infrastructure.
And because access is managed centrally, administrators can adjust resource assignments as requirements change.
If an employee moves to a different project or a contractor’s assignment ends, IT can update their access without redesigning the network.
Step 4: Leostream Cloud Establishes the Connection
Once the engineer selects their workstation, Leostream Cloud facilitates the connection using the configured remote access technology.
Different workloads have different requirements, and the connection method matters.
A standard Windows desktop might use RDP, while a graphics-intensive workstation may benefit from Amazon DCV. Other environments may require SSH, VNC, Jump Desktop, or Sunshine/Moonlight.
Leostream Cloud supports these different connection technologies, giving organizations flexibility to use the method that fits their resources and workflows.
In our example, the engineer connects to the GPU workstation using the connection method configured by IT.
The applications and processing remain on the workstation. The employee interacts with the remote session from their local device.
The user gets access to the workstation they need without receiving general access to the surrounding network.
Step 5: The Connection Reaches the Protected Resource
One of the most important parts of Leostream Cloud is how it connects users to resources behind a firewall.
Organizations generally want to avoid exposing services such as RDP or SSH directly to the public internet. But making remote connections work across protected networks can introduce additional networking complexity.
Leostream Cloud addresses this through its Gateway and Agent architecture.
The Leostream Cloud Agent supports an outbound connectivity model, allowing protected resources to participate in remote connections through a customer-hosted Leostream Cloud Gateway without requiring inbound internet exposure of their remote access services.
This means an organization can keep workstations behind its existing firewall while providing authorized users with remote connectivity.
For the engineer, no VPN client is needed. For IT, there’s no VPN appliance to deploy or manage, and no need to open inbound connections to individual workstations. Leostream Cloud provides secure, resource-specific access without the additional complexity of traditional VPN infrastructure.
What Happens Behind the Scenes for IT?
The employee’s experience may involve only a few steps, but administrators need tools to manage the environment over time.
Leostream Cloud provides centralized management for several important parts of remote access.
Managing Users and Resource Assignments
Administrators determine which users can access which resources.
An organization might have separate groups of employees, contractors, and service providers, each with different access requirements.
As those requirements change, IT can update assignments and permissions centrally.
This makes it easier to give users access to the systems they need while limiting access to other resources.
Managing Connection Settings
Different workstations and workloads may use different remote access protocols.
Leostream Cloud allows organizations to configure the connection methods used for their resources, supporting a range of Windows, Linux, macOS, and specialized workstation environments.
This is particularly useful for organizations with mixed infrastructure or users who require high-performance remote access.
IT can support different connection technologies without requiring a separate access management approach for every workload.
Monitoring Connections and Session Activity
Administrators also need visibility into remote access activity.
Leostream Cloud provides centralized logging to help IT track access events and connection activity.
For applicable connections using its built-in HTML5 viewer, optional session recording provides additional visibility for auditing, troubleshooting, or oversight of third-party access.
This is especially valuable when external vendors or contractors connect to protected systems.
Rather than managing access and reviewing activity through disconnected tools, IT can maintain a more consistent view of remote connections.
A Simpler Approach to Remote Access
Now consider the entire experience from the engineer’s perspective.
They open Leostream Cloud, authenticate, select their assigned workstation, and connect.
They don’t need to establish a traditional VPN connection, navigate the corporate network, or understand how the workstation is connected behind the firewall.
Behind the scenes, Leostream Cloud handles identity integration, access permissions, resource selection, and connection orchestration.
IT maintains centralized control over who can connect, which resources are available, how connections are established, and what access activity is recorded.
This approach can be especially useful for organizations supporting remote employees, distributed workstations, contractors, and external service providers.
It also supports an important Zero Trust principle: access should be limited to the resources a user is authorized to use.
Leostream Cloud addresses this specific remote access requirement as part of a broader security strategy.
From Identity to Connection
The value of Leostream Cloud comes from bringing several parts of remote access into one controlled experience.
Identity establishes who the user is. Access rules determine which resources they can use. Connection settings define how they connect. Centralized management gives IT visibility and control.
For the employee, the result is a straightforward way to reach the workstation or resource they need.
For IT, it’s a more focused way to provide remote access without extending unnecessary network connectivity.
Leostream Cloud turns identity and access permissions into a simple, controlled connection to the right resource.
Learn more about Leostream Cloud and how it helps organizations provide secure, resource-specific remote access.