Allow SSH and RDP Access to Private Resources

👍

Secure Access Packages and Feature Availability

Not all of the features described here are available to all Secure Access packages. Information about your current package is listed on the Admin > Licensing page. For more information, see Determine Your Current Package. If you encounter a feature here that you do not have access to, contact your sales representative for more information about your current package. See also, Cisco Secure Access Packages

You can allow Zero Trust Access to private resources using SSH and Microsoft's Remote Desktop Protocol (RDP).

Table of Contents

• Clientless Browser-Based Zero Trust Access
  • Configuration overview: Browser-based zero trust access using SSH or RDP
  • Notes for browser-based SSH and RDP access
  • Supported options for SSH
• Client-Based Zero Trust Access

Clientless Browser-Based Zero Trust Access

Configuration overview: Browser-based zero trust access using SSH or RDP

To allow clientless browser-based Zero Trust Access to private resources using SSH or RDP:

1. If you are using older SSH servers, see Details: Supported options for SSH.
2. Configure your private resource:
   1. Allow access using the applicable protocol for the internally reachable address. See Add a Private Resource.

Note: The resource name will appear at the top of your users' SSH or RDP window.

3. In the Private Resource, enable Zero-trust connections, then enable and configure browser-based connections.
4. Follow the instructions for granting access to private destinations in Get Started With Private Access Rules.
5. If your environment has a web proxy or firewall between end user browsers and the Secure Access cloud, you must allow websocket access on port 443 from your users' browsers to Secure Access.
6. When you give users the applicable SSH or RDP credentials or private key for the resource, also provide the public URL for browser-based Zero Trust Access that you configured on the Private Resource page. Neither Secure Access nor the browser stores the credentials or private key.

Notes for browser-based SSH and RDP access

• For limits on the number of user sessions, see the Service Connections section in Limitations and Range Limits.
• The user experience will look like this:

• SSH and RDP users can paste text copied from their local machine by using the remote clipboard feature, shown in the image above.
• RDP users will not be able to upload files or images.

Supported options for SSH access

Most SSH connections will be successful. If you are using older SSH servers, the following options are supported.

Client-Based Zero Trust Access

Client-based SSH and RDP access does not require special configurations. No user experience specific to Secure Access is required.

Manage Branch Connections < Allow SSH and RDP Access to Private Resources > Manage the Access Policy