Privileged Access & Governance

Unify access to all your infrastructure.

Speed that makes you more secure: one login for every server, cluster, and database, for every team. Developers stop juggling VPNs, keys, and kubeconfigs. Platform teams get one set of rules and one audit trail. Watch both sides.

WHAT THE NEW ENGINEER DOES

WHAT THE PLATFORM TEAM DOES

If the secure way is slow, people build their own.

When access takes days, engineers find another way in. None of it is approved, none of it is logged, and none of it goes away when they leave.

The fix isn’t more gates. It’s making the governed way the fastest way.

SHADOW ACCESS

A copied kubeconfig

No approval · No log

A personal SSH key on prod

No approval · No log

A tunnel to the database

No approval · No log

A shared admin password

No approval · No log

From a tangle to one door.

Every team and every resource type gets its own path in, until nobody can say how access works. With Teleport, every path goes through one door with one set of rules.

Example

14

separate ways in to maintain, in this example

1

way in, with Teleport

One door for every resource.

Examples below

Servers

a VPN, a bastion, and a shared SSH key

tsh ssh, with your SSO login

Kubernetes

kubeconfigs in a shared drive

tsh kube login, then kubectl as usual

Databases

passwords in a wiki or a vault

tsh db connect, as the right database user

Cloud consoles

an IAM user per person, per account

the right role, through your SSO

Internal apps

a dashboard exposed to the internet

behind Teleport, with no public endpoint

Windows desktops

an RDP jump box

in the browser, with every session recorded

Protect all your critical resources: Linux servers, Windows desktops, Kubernetes clusters, databases, AWS, Azure, and Google Cloud consoles, and internal web apps. See supported resources

Easier for them. Better for you.

The fast path is the secure path.

When the easiest way in is also the governed way in, nobody builds a workaround.

FOR DEVELOPERS

One login. The tools they already use.

  • Sign in once with your SSO and MFA

  • Keep ssh, kubectl, and psql, through tsh or the Teleport Connect desktop app

  • No VPN client, no keys or kubeconfigs to manage

  • New to a team? Their access is there on day one

FOR THE PLATFORM TEAM

One set of rules. One audit trail.

  • Define access once with roles and labels, mapped from your IdP groups

  • New clusters and databases pick up the right access from their labels

  • One audit log across servers, databases, Kubernetes, and clouds

  • Manage it as code with Terraform

What changes on day one

Today

With Teleport

Every team runs its own VPN, bastion, or scripts

Check.svg

One way in for every team and every resource

Kubeconfigs and passwords passed around

Check.svg

Credentials issued at login that expire on their own

New teams wait while access gets wired up by hand

Check.svg

Access follows labels and IdP groups

An audit means stitching logs from five systems

Check.svg

One audit trail across every resource type

Offboarding means hunting down every key

Check.svg

One lock, and their access is gone everywhere

80%

drop in time spent troubleshooting access issues

95%

reduction in exposed attack surface

Not another system to babysit

Your platform team already runs enough. Teleport is built to take work off their plate, not add to it.

Running in minutes

On a free trial, enroll a server and connect in under 20 minutes.

No inbound ports

Agents connect out to Teleport, so there are no firewall holes to open and no bastion to expose.

Updates itself

Agents keep themselves current with Teleport’s automatic updater.

Fully managed, or self-hosted

Let Teleport run the cluster for you on Teleport Cloud, or run it yourself, including air-gapped.

Managed as code

Roles, rules, and resources in Terraform, reviewed like the rest of your infrastructure.

Fits the IdP you already own

Okta, Microsoft Entra ID, Google Workspace, or any SAML or OIDC provider.

Background image
Speed is key to our business. But so is security. The Teleport Access Platform allows our engineers to securely access the infrastructure they need to do their jobs without getting in the way of productivity. Everybody wins.

Luke Christopherson


Details for your security team

How one way in works

SSO with Okta, Entra ID, and Google Workspace, and Access Requests, are part of Teleport Enterprise.

Identity

  • Users sign in through your identit yprovider with MFA

  • Teleport issues short-lived certificates at login, so there are no standing passwords or keys

  • Roles come from your IdP groups

  • Linux accounts are created automatically on first login

Access

  • One proxy for SSH, Kubernetes, databases, web apps, Windows desktops, and cloud consoles

  • Role- and label-based access control across every protocol

  • Just-in-time Access Requests for anything beyond everyday access

Audit

  • One audit log for logins, sessions, database queries, and Kubernetes requests

  • Session recordings for SSH, Kubernetes, and Windows desktops

  • Export events to your SIEM

Questions engineers ask

No. They keep ssh, kubectl, and psql. Teleport adds one sign-in step, through tsh or the Teleport Connect desktop app.

Through labels and roles. Tag a cluster or database, map your IdP groups to roles, and access follows the labels. Teleport can also discover cloud resources in AWS, Azure, and Google Cloud automatically.

SSO covers web apps. Servers, Kubernetes, and databases use their own protocols and credentials. Teleport extends your SSO to those protocols by issuing short-lived certificates at login.

It can. Engineers reach servers, clusters, databases, and apps through Teleport instead of a VPN. See Replace VPNs and Bastions.

Teleport runs as a managed cloud service or self-hosted, including air-gapped environments. On a free trial, you can enroll a server and connect in under 20 minutes.

Yes. Teleport Enterprise connects to Okta, Microsoft Entra ID, Google Workspace, and other SAML or OIDC providers.

Teleport adds its own layer on top of your IdP: phishing-resistant MFA on every session, no permanent admins for an attacker to target, and two-person approval for sensitive actions. In testing by security firm Doyensec, these settings held up against every IdP compromise scenario tested. Read the white paper.

Teleport maintains SOC 2 Type II, ISO 27001, and HIPAA Security Rule compliance. Reports and security documentation are in the Teleport Trust Center.