.png)
Connect Rippling to Kolide to automate device trust enrollment and ensure only compliant employee devices can access company resources.
The Rippling–Kolide integration connects Rippling's employee identity layer with Kolide's device trust and endpoint compliance platform. When employees are onboarded in Rippling, Kolide enrollment is triggered to verify that their devices meet security policy requirements before granting access to company resources.
Kolide integrates with identity providers to enforce device trust — blocking access from non-compliant devices even when credentials are valid. Connecting Kolide to Rippling ensures device enrollment follows the same hire lifecycle and that offboarded employees' devices are removed from the trusted device registry automatically.
IT teams using Kolide often enroll devices manually after hire, creating a window where new employees are accessing company resources from unverified devices. Triggering Kolide enrollment from Rippling's onboarding workflow closes this window and ensures compliance from day one.
thePeopleStack configures the Rippling–Kolide connection to trigger device enrollment as part of the IT onboarding sequence, and validates that offboarding removes the employee from Kolide's user directory. We coordinate the enrollment workflow with your IT team to confirm device check messaging is appropriate for your security policies.
Kolide integrations for thePeopleStack's Rippling clients are structured around US IT security and device compliance policies.
Canadian and cross-border operations: for Canadian employees, Kolide device enrollment follows the same Rippling-driven onboarding lifecycle, with PIPEDA considerations for device monitoring communicated to employees as part of the enrollment flow.
Kolide is a device trust and endpoint compliance platform that integrates with identity providers to enforce security policies at login. It checks device health — OS updates, disk encryption, screen lock — and blocks access from non-compliant devices before credentials are accepted.
Kolide integrates with SAML identity providers like Rippling to add device trust as a factor in the authentication flow. Employees must be in Rippling's user directory and on a compliant device to pass Kolide's check.
Yes. SOC 2 requires evidence of endpoint security controls. Kolide provides device compliance data that compliance platforms like Drata and Vanta can pull to satisfy endpoint security criteria.
The employee is removed from Kolide's user directory, which invalidates their device trust status and prevents further authentication through Kolide-protected applications.
Configuration takes 2–3 hours including Rippling identity connection, enrollment workflow setup, and offboarding trigger testing.
