GOVERNATLAS / PRODUCT DOSSIER

Teleport

Teleport’s version 18.x documentation describes temporary role and resource Access Requests with configurable approvers, and states that users cannot approve their own requests. The reviewed page states that Identity Governance requires Teleport Enterprise and distinguishes temporary Access Requests from longer-lived Access Lists.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

Where it fits

Confirm the edition and choose the right access object.

The decision to make

Confirm the edition and choose the right access object. A temporary role elevation, temporary access to a particular resource and membership in a longer-lived Access List are different operating decisions. Specify the approval count, requested duration and exception path before measuring access latency. Keep automatic review policy visible when the demonstration does not require a person.

What this record does not establish

The page’s compliance-control positioning is not a GovernAtlas compliance determination. Version and Enterprise entitlement are material. No universal session-termination, integration coverage or current commercial price is inferred.

1 current source · 2 published assertions
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗
A

A test worth running

Use a disposable resource and a synthetic engineer. Require two authorized approvals, attempt self-approval, then request a bounded resource grant. Observe permissions before approval, during the grant and after expiry using both a new connection and an existing session. Retain a denied request and compare its record with a successfully expired grant.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. A version/edition/request-type manifest with reviewer authority and expiry policy.
  2. Approval, denial and expiry evidence, distinguishing fresh connections from existing sessions.

THE OPERATING DETAIL

Follow the decision into the enforcing system.

GovernAtlas analysis: practical review considerations, not findings from a product test.

Set the operating boundary

A temporary role elevation, temporary access to a particular resource and membership in a longer-lived Access List are different operating decisions. Specify the approval count, requested duration and exception path before measuring access latency. Keep automatic review policy visible when the demonstration does not require a person.

A proposed buyer demonstration

Use a disposable resource and a synthetic engineer. Require two authorized approvals, attempt self-approval, then request a bounded resource grant. Observe permissions before approval, during the grant and after expiry using both a new connection and an existing session. Retain a denied request and compare its record with a successfully expired grant.

What the evidence does not establish

The page’s compliance-control positioning is not a GovernAtlas compliance determination. Version and Enterprise entitlement are material. No universal session-termination, integration coverage or current commercial price is inferred.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

01
first party asserted

The reviewed page states that Identity Governance requires Teleport Enterprise and distinguishes temporary Access Requests from longer-lived Access Lists.

Source, dates & preserved provenanceTeleport — current primary scope ↗

Authority: first party
Observed 2026-10-18 · Reviewed 2026-10-18 · current until 2026-11-17

Artifact SHA-256: 6e71e4ace567931771c67172d16119f8356e4aa5e3ecc79b1164cd2296f89feb

The hash identifies the preserved capture. The live source may have changed.

02
first party asserted

Teleport’s version 18.x documentation describes temporary role and resource Access Requests with configurable approvers, and states that users cannot approve their own requests.

Source, dates & preserved provenanceTeleport — current primary scope ↗

Authority: first party
Observed 2026-10-18 · Reviewed 2026-10-18 · current until 2026-11-17

Artifact SHA-256: 6e71e4ace567931771c67172d16119f8356e4aa5e3ecc79b1164cd2296f89feb

The hash identifies the preserved capture. The live source may have changed.

Source register

Teleport — current primary scope ↗first party · captured 2026-10-18
Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

01

Can you demonstrate and export: A version/edition/request-type manifest with reviewer authority and expiry policy.

02

Can you demonstrate and export: Approval, denial and expiry evidence, distinguishing fresh connections from existing sessions.

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

COMPLIANCE / CLAIMS, SCOPE & GAPS

Start with the requirement.
Inspect the support.

Prepare your vendor review ↗

These labels describe this dossier’s current evidence coverage. A published mention may be a framework mapping, a qualified assertion or a limitation; it is not a compliance finding.

For HIPAA-regulated use, request service-specific BAA eligibility, processing scope and responsibility details. Missing evidence here does not establish noncompliance. Payment cannot alter these evidence labels.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗