How It Works

strongDM is a proxy that manages and audits access to databases, servers, clusters, and web apps. The strongDM network is comprised of a local client, gateway intermediary, and configuration layer.  

How strongDM manages and audits access to databases, servers, clusters and web apps
strongDM local client SSO

The Local Client

The local client tunnels requests from the user’s workstation to the gateway, through a single TLS 1.2-secured TCP connection. strongDM supports Mac, Windows, and Linux workstations.

To authenticate, users login to the local client; that call can be optionally redirected to your identity provider or SSO.

The local client consists of both graphical and command-line interfaces.

The Gateway

Gateways are the entry point to your network.  They can be deployed with a DNS entry, sit privately on the corporate network, and/or behind a VPN.

In the case of a flat network, it is the gateway that talks to the target systems.  If internal subnets disallow ingress, relays create a reverse tunnel to form connections to the gateway. All data routes through your network.

Gateways decrypt credentials on behalf of end users, and deconstruct requests for the purposes of auditing.

Gateways and relays are deployed in pairs, and scale horizontally.

Configuration Layer

The Admin UI houses configuration.  Users are assigned to roles, and roles are collections of permissions across servers, databases, clusters, and web apps.  Configuration is pushed down to the end user's local client, and updated in real-time.

"When strongDM said deployment would take an hour, I assumed they were full of it and blocked out a full day. We finished in 45 minutes." - Peter Tormey, Manager DataOps, SoFi
SSO Access Control