Privileged Access & Governance
Eliminate static credentials, for people and pipelines.
No SSH keys on laptops, no shared database passwords, no deploy keys in CI. People and pipelines get short-lived certificates that expire on their own. Watch Teleport replace four of them.
Every static credential is a breach waiting to be found.
They get copied, pasted, committed, and forgotten. Rotating them is a project nobody finishes, and when one leaks, nobody can say who used it.
The safest credential is the one that doesn’t exist.
STATIC CREDENTIALS
SSH keys on laptops
Expires: never
Database passwords in a vault
Expires: never
Cloud access keys in CI
Expires: never
Service account tokens in config files
Expires: never
Credentials spread like glitter.
Every copy and paste spreads a little more: into laptops, repos, CI settings, and config files. You can’t count it, you don’t know what each piece unlocks, and you’ll still be finding it years from now.
A vault stores and rotates long-lived secrets, but any copy that leaves it works for whoever holds it until the next rotation. Teleport has no shared secret to store: each person or machine authenticates as itself and gets a short-lived certificate bound to that identity and its roles, which your resources trust through Teleport’s certificate authority and which expires on its own.
Example
| Question | Today | With Teleport |
|---|---|---|
| How many? | Unknown | None stored |
| What does each one unlock? | Unknown | Each one scoped to a role |
| Who has copies? | Unknown | Gone on their own |
One identity model
The same rules for people and pipelines.
Humans and machines get the same short-lived certificates, the same roles, and the same audit trail.
FOR PEOPLE
Sign in once. Nothing to copy, rotate, or leak.
SSO and MFA issue a certificate that expires on its own/span>
No SSH keys on laptops and no shared database passwords
The same ssh, kubectl, and psql they use today
FOR PIPELINES AND SERVCICES
Machine ID, not secrets in CI.
Bots get short-lived certificates that renew automatically
Join using the platform’s own identity, like GitHub Actions, AWS, or Kubernetes, so there’s no stored secret
Every bot action is in the audit log, and bots show up in Identity Security like any user
What changes on day one
Today | With Teleport |
|---|---|
SSH keys copied to laptops and never removed | A certificate from SSO and MFA that expires on its own |
Database passwords shared through a vault or a wiki | Connect as the right database user, with no password |
Deploy keys and cloud keys stored in CI secrets | Pipelines get short-lived certificates from Machine ID |
Rotation projects that never finish | Nothing long-lived to rotate |
A leaked credential nobody can trace | Every session tied to a person or a named bot |
95%
reduction in exposed credentials and standing privileges
Get control over every identity, human or not.
Machine identities multiply faster than people. Every pipeline, service, cluster, and agent needs access to something. Teleport gives each one an identity, credentials that expire, and a place in the same audit trail.
CI/CD pipelines
GitHub Actions, GitLab, and Jenkins jobs get short-lived credentials per run instead of keys stored in CI settings.
Infrastructure as code
Terraform and Ansible runs get access for the length of the run, scoped by role.
Kubernetes workloads
Workloads running in your clusters get their own identities instead of long-lived tokens.
Service to service
Workload Identity issues services short-lived, SPIFFE-compatible identities for talking to each other.
AI agents
Agents and MCP tools get identities and scoped access, like any other workload.
One inventory
Identity Security lists bots alongside people, with what each one can reach.

SSO and RBAC support, in combination with Teleport’s unified access control, made secure infrastructure access for humans easy. Machine identity is helping us secure automation. Teleport is simply one of the best privileged access solutions for engineering environments out there.
Olga Daminova
Infrastructure Security Engineer, Rush Street interactive
Details for your security team
How the credentials go away
SSO with Okta, Entra ID, and Google Workspace, and Identity Security, are part of Teleport Enterprise.
People
Users sign in through your identity provider with MFA
Teleport issues short-lived certificates scoped to their roles
Database access uses certificates, so there are no shared database passwords
Machine ID
tbot gets a bot short-lived certificates and renews them automatically
Bots join with platform identity (for example GitHub Actions, AWS, or Kubernetes) or a single-use token
Bots get roles, like people, so their access is scoped and reviewable
Visibility
One audit log for people and bots, down to the commands a bot runs
Identity Security lists bots alongside users, with their standing privileges
Lock a person or a bot and their access ends everywhere
Questions engineers ask
Possibly, for application secrets like third-party API keys. Teleport removes the credentials people and pipelines use to reach your infrastructure: SSH keys, database passwords, kubeconfigs, and deploy keys.
Machine ID bots join using an identity the platform already provides, such as GitHub Actions or a cloud provider’s identity. Where that isn’t available, a single-use join token works once and is then useless.
People sign in again with SSO and MFA. Bots renew their certificates automatically while they run.
Yes. Bot sessions and the commands they run are in the same audit log as people’s, and Identity Security lists bots alongside users with their standing privileges.
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.

