Customer-hosted Private Cloud Remote Access Options

The Managed Private Cloud requires regular access by our Managed Services Engineering team to install patches, updates, and upgrades, troubleshoot and fix issues, and optimize security and performance.

JumpHost

A Jumphost is a security-hardened virtual machine (VM) that acts as a secure communication relay using SSH. The Jumphost initiates the connection from an Auth0 (using a whitelisted IP address) to the Managed Private Cloud VMs. (You would open access to the Jumphost to allow Auth0 access when necessary).

Auth0's connections originate from a VPN-secured network using public key access to your Jumphost so that only authorized Managed Service Engineers can access connect to your environment.

In this configuration, an external Auth0-managed Jumphost is permitted sole SSH management access to the Managed Private Cloud.

Private Cloud Remote Access Jumphost + Firewall Whitelist

The benefits of this option are:

Jumphost provides a single point of access and auditing
Auth0 handles tasks related to auditing, session recording, VPN access to Jumphost, and Identity Management
Access could be disabled via firewall rules or security groups

Similar to option 1, this configuration permits an external Auth0 Jumphost to connect via firewall whitelist to an internal, customer-managed Jumphost. This second Jumphost then provides actual access to the Managed Private Cloud nodes.

Private Cloud Remote Access Two Jumphosts

The benefits of this option are:

Jumphost provides a single point of access and auditing
Auth0 handles tasks related to auditing, session recording, VPN access to Jumphost, and Identity Management
Disabling Auth0 access is as simple as shutting down a server
Can be installed in DMZ (if necessary)

There is one concern with this option, however: An additional virtual Jumphost required in your infrastructure.

Auth0 does not support other remote access options, such as VDI or Screen Sharing mechanisms. The alternative options introduce compliance concerns, including (but not limited to):

Not being able to internally audit connections and SSH sessions
Not being able to enforce identity management on Auth0 employee accounts
Potential exposure to untrusted systems running non-standard software (from where the connections are generated to Auth0 VMs)
Inability to verify the identity of participants on the other end

Docs