All pages
Powered by GitBook
1 of 2

Tunnels

Create a secure and encrypted TCP/IP connection to your target endpoint from your Vault

What are Keeper Tunnels?

How do Keeper Tunnels work?

When starting a tunnel, a local port is opened up on the local device running Keeper Desktop client. Native applications will communicate to the target from this local port. This is done by:

  1. The Desktop Vault Client communicating with the Keeper Gateway with the relevant connection info through a secure tunnel

  2. The Keeper Gateway then establishes a secure, encrypted TCP/IP connection to the target IP/Port found on the PAM Record

  3. Opening a local port on the local device running Keeper Desktop Client

  4. Native applications will connect to this local port to communicate with the target IP/Port

Why Use Keeper Tunnels?

A common challenge faced by IT Admins, DevOps and development teams is providing remote employees or contractors with access to internal company resources without exposing those resources to external networks. Additionally, remote employees may want to use their desired native applications to access these resources.

Keeper Tunnels solves the above solutions by:

  • Providing secure, encrypted connection from client to target resource

  • Allowing users to securely connect to target resource with the native application of choice

  • Simplifying Configuration - streamline setup and management of secure connection from PAM Record types

  • Access controls and compliance - centralized management of access controls, ensuring that all connections meet organizational security policies and compliance requirements

Loading...