.png)
Connect Rippling to Teleport so infrastructure access — servers, databases, Kubernetes clusters, and cloud consoles — is provisioned at hire for engineering and DevOps teams and revoked completely at offboarding without manual credential cleanup.
thePeopleStack configures the Rippling–Teleport integration with RBAC role mapping that reflects your actual infrastructure ownership structure — ensuring backend engineers, DevOps engineers, SREs, and security teams each receive certificate-based access to their specific infrastructure scope from day one. We build the offboarding workflow to trigger Teleport deprovisioning as an immediate action at termination, before lower-priority offboarding steps.
For clients pursuing SOC 2 or ISO 27001, we advise on configuring Teleport's session recording and audit log retention to produce compliance evidence for infrastructure access controls — with user-level attribution tied to Rippling's employee identity record for clean audit trails.
Teleport infrastructure access management is deployed by thePeopleStack's Rippling clients primarily for US engineering and DevOps teams managing cloud and on-premises infrastructure, with RBAC policies and audit log configuration aligned to US security compliance frameworks including SOC 2 and FedRAMP.
Canadian and cross-border operations: Canadian engineers are provisioned into Teleport through the same Rippling lifecycle sync, with thePeopleStack confirming that cross-border infrastructure access data handling and PIPEDA considerations are addressed for clients with engineering teams distributed across US and Canadian locations.
Teleport replaces static SSH keys with short-lived certificates issued based on the engineer's verified Rippling identity. New hires receive Teleport certificates scoped to their infrastructure access role on their start date; certificates expire automatically; and Rippling offboarding deactivates the user, preventing certificate renewal and immediately ending infrastructure access without manual key cleanup.
Yes. Rippling job title, department, and team fields map to Teleport RBAC roles — scoping each engineer's infrastructure access to the servers, databases, and Kubernetes clusters their role actually requires. Backend engineers, DevOps teams, SREs, and security engineers each receive a different Teleport role reflecting their infrastructure responsibilities.
Employee termination in Rippling deactivates the Teleport user account, invalidating all associated certificates and terminating active sessions. Without Rippling-driven automation, departing engineers' infrastructure access persists until an IT admin manually removes their Teleport account — a gap that can span days for production system access.
Yes. Teleport's session recording captures every infrastructure access session with user identity, timestamp, and full session playback. When the recording user identity is anchored to Rippling's employee record, this produces audit-ready evidence for SOC 2 Type II infrastructure access controls with clean user-level attribution.
A standard configuration covering RBAC role mapping from Rippling data, certificate-based provisioning, and offboarding deprovisioning typically takes 4–6 hours. Migrating from SSH key-based access to Teleport certificate-based access for an existing engineering team is a separate, larger-scope project.
