Sulat.com / Writing on AISaturday, November 21, 2026
Cloud Security/21 November 2026

Tailscale PAM puts session records and injected credentials on top of its VPN

Tailscale says its VPN gets you connected and Tailscale PAM gets you into databases and servers without shared passwords, with session records. PAM is in beta and has no published price.

Glossy 3D Tailscale logo of nine dots floating before a locked steel server-room door with a security camera above it

At a glance

  • Tailscale says its VPN secures connections between users, devices and apps, while Tailscale PAM controls and audits access to specific services such as SSH, databases and Kubernetes.
  • A PAM connector runs inside your network, and Tailscale says it can inject database credentials so nobody has to share a password.
  • PAM always logs identity, IP address, location, device, time and duration, and can record SSH replays and database query logs.
  • PAM is in beta, Tailscale's pricing page says to contact sales, and the company hasn't given a general availability date.

Tailscale says its VPN gets people connected, while Tailscale PAM, its privileged access management product, gets them into databases and servers without passing around passwords and keeps a record of who did what. The company posted the pitch on X on 20 November and linked a 26 October blog post by Tailscale writer Andrew Cunningham that explains where the two products divide.

Cunningham writes that the VPN secures connections between users, devices and apps, while PAM makes infrastructure access easier to set up and administer. His shorthand is that PAM is “the security camera for a door you’ve locked using Tailscale VPN”. Tailscale launched PAM in beta on 26 August, built from its earlier integration with Border0, and its docs still list the product as beta.

Side-by-side cards: Tailscale VPN gets you connected, like a lock; Tailscale PAM gets you inside and records who did what, like a camera
The VPN locks the door; PAM adds the camera and logs you in.

What the connector does

PAM needs at least one connector for every network you want to reach, Cunningham writes. A connector is software running on a device, server, container or virtual machine on the same network as the resource. Each user’s device talks to it over a WireGuard-encrypted tunnel, and the connector mediates access from there. Tailscale says you can run several connectors per network for redundancy, and that you don’t need the Tailscale client on every server you want to protect.

Tailscale VPNTailscale PAM
What it doesSecures connections between users, devices and appsControls and audits access to services such as SSH, databases, Kubernetes, remote desktop and web apps
How access is setGrants and ACLs say which users and devices reach whichGrants tied to a service, with permissions inside it, such as read-only database access
Where it runsPeer-to-peer mesh between devicesA connector inside your network brokers each session
Tailscale’s own split, from Cunningham’s blog post and the PAM docs.

Cunningham says PAM checks every connection from every user each time it happens, and can limit what someone does inside a service. His example is letting a user add to part of a database while blocking them from deleting existing data. Tailscale’s docs show read-only rules for one or all databases, and SSH permissions that switch shell, command execution, SFTP and TCP forwarding on or off separately.

Credentials and records

The connector can inject credentials and authentication tokens, so a database password doesn’t go to everyone who needs access. Tailscale says you can change the password in the admin console or an external secrets manager without redistributing it. People with the Tailscale client can open locally installed tools through the connector. Others can use a browser, though they still sign in, and a 29 September changelog entry says the browser client at my.tailscale.com reuses one sign-in across tabs.

Flow from a signed-in user through a PAM connector, which checks the rules and adds the password, to a database that keeps its own password
You sign in with Tailscale; the connector supplies the database password.

On records, Cunningham says PAM always logs the user’s identity, IP address, IP-derived location, device information, connection time and duration. Optional session recording goes further: a query log with error messages for databases, a text and video replay for SSH, and recordings for HTTP, Kubernetes and S3 sessions. Recordings sit in Tailscale-managed storage by default, and he writes that keeping them in your own Amazon S3 storage is a Premium plan feature.

Always logged: identity, IP address, location, device, time and duration. Optional recordings: SSH replay, database query log, web, Kubernetes and S3 sessions
Every session is logged; recordings of what happened inside are optional.

The August beta announcement, written by Smriti Sharma, adds just-in-time access. Users request a specific service and get approval through Slack, with access limited to a set period.

Availability

Tailscale points people to a waitlist for the beta. Its pricing page lists PAM under platform extensions with a contact-sales button and no published price. The docs list databases including PostgreSQL, MySQL, MongoDB, Microsoft SQL Server, Snowflake, Amazon RDS and Google Cloud SQL. Tailscale hasn’t given a date for general availability.


Discover more from Sulat AI & Tech News

Subscribe to get the latest posts sent to your email.