Privileged Access Management
Standing privileges expand your blast radius and enable lateral movement, increasing the surface area for compromise. Teleport replaces standing access with just-in-time privileges that expire automatically.
WHY STANDING PRIVILEGES KEEP SECURITY TEAMS UP AT NIGHT
Access requests used to be reserved for highly privileged actions, because managing them manually was too unwieldy. Now, just-in-time access can be delivered at speed and scale, enabling migration to a zero standing privileges (ZSP) posture.
Capability | ![]() | Without Teleport |
|---|---|---|
Default access | No standing access — all privileges are task-based and short-lived | Standing privileges granted at onboarding, rarely reviewed |
Approval workflow | Requests and approvals via Slack, PagerDuty, or Jira — seconds, not hours | Tickets routed through ITSM tools that move at business speed |
Service accounts | Machine identity with JIT privileges activated only when needed | High-privilege service accounts active 24/7 — easy targets |
Contractor access | Temporary access with hard expiry — automatically revoked, no cleanup | Manual deprovisioning required — often forgotten |
Blast radius | Short-lived privileges limit what an attacker can reach before expiry | Compromised account inherits all standing permissions |

OUTCOMES
End Credential Sprawl
95%
reduction in exposed credentials and standing privileges
0
shared secrets, static API keys, or vaults to maintain
Speed Up Engineers
10x
faster access provisioning vs. legacy workflows or ITSM tickets
0
hours waiting for approvals on routine infrastructure tasks
Simplify Compliance
100%
auditable sessions across SSH, Kubernetes, databases, and cloud
0
anonymous access events in your audit record
TASK-BASED SHORT-LIVED ACCESS
Teleport replaces standing privileges with fine-grained, task-based access controlled by short-lived certificates. Access is granted based on role, device trust, and context — and expires automatically when the task is complete.
Short-lived privileges reduce blast radius
Least-privileged access based on role, device, and task context
Automatic expiration — no manual revocation required
Access lists automate role management and inheritance
DEVELOPER-FRIENDLY APPROVAL WORKFLOWS
Engineers request access via CLI or web UI, through Slack, PagerDuty, Jira, and Microsoft Teams — not a separate portal. Access can be approved automatically for routine tasks, or require a session moderator or dual authorization for sensitive ones
Approvals via Slack, PagerDuty, Jira, Teams, Discord, and Mattermost
Automated grants by policy for routine role-based access
Dual authorization for sensitive operations — FedRAMP AC-3 compliant
Session moderation for high-privilege actions — requires approver to join live
MACHINE AND WORKLOAD GOVERNANCE
The same JIT model that governs human access applies to service accounts, CI/CD pipelines, and automated workflows. Machine identity replaces high-privilege service accounts with short-lived credentials — no more 24/7 standing access for automation.
Machine identity for CI/CD pipelines, service accounts, and automation
JIT credentials activated per job that expire automatically
Governs GitHub Actions, Terraform, Ansible, and IaC workflows
Unified audit trail for human and machine access