Rippling Hardening Guide
Workforce platform security for app provisioning, device management, and SCIM controls
Overview
Rippling is a unified workforce platform managing HR, IT, payroll, and spend. REST API, SSO configurations, and deep SaaS integrations through device management access employee PII, financial data, and IT systems. Compromised access has cascading effects across multiple business functions.
Intended Audience
- Security engineers managing workforce platforms
- Rippling administrators
- GRC professionals assessing unified platform security
- Third-party risk managers evaluating HR/IT integrations
Table of Contents
1. Authentication & Access Controls
1.1 Configure SSO with MFA
Profile Level: L1 (Baseline) NIST 800-53: IA-2(1)
ClickOps Implementation
Step 1: Configure SSO
- Navigate to: Settings → Security → Single Sign-On
- Configure SAML IdP
- Enable SSO enforcement
Step 2: Enable MFA
- Navigate to: Settings → Security → Multi-Factor Authentication
- Require MFA for all users
- Configure phishing-resistant methods
1.2 Role-Based Access
Profile Level: L1 (Baseline) NIST 800-53: AC-3, AC-6
ClickOps Implementation
Step 1: Define Permission Sets
| Role | Permissions |
|---|---|
| Super Admin | Full access |
| HR Admin | HR/payroll functions |
| IT Admin | Device/app management |
| Finance Admin | Spend management |
| Manager | Team access |
| Employee | Self-service |
Step 2: Configure Custom Roles
- Navigate to: Settings → Permissions
- Create custom permission sets
- Apply least privilege
2. Integration Security
2.1 App Management Security
Profile Level: L1 (Baseline) NIST 800-53: CM-7
Description
Secure Rippling app integrations.
Rationale
Attack Scenario: Compromised Rippling admin provisions access to connected apps; single compromise cascades across all integrated SaaS.
ClickOps Implementation
Step 1: Review Connected Apps
- Navigate to: Apps → Installed Apps
- Audit all connected applications
- Remove unused integrations
Step 2: SCIM Security
- Review SCIM provisioning
- Limit auto-provisioning scope
- Audit deprovisioning
2.2 Device Management Security
Profile Level: L2 (Hardened) NIST 800-53: CM-7
ClickOps Implementation
Step 1: Device Policies
- Navigate to: IT → Device Management
- Configure security policies
- Require device enrollment
3. Data Security
3.1 Protect Employee Data
Profile Level: L1 (Baseline) NIST 800-53: SC-28
ClickOps Implementation
Step 1: Configure Field Access
- Limit visibility of sensitive fields
- Restrict SSN/bank account access
- Configure manager visibility
Step 2: Report Security
- Limit report access
- Restrict bulk exports
- Audit data access
3.2 Payroll Security
Profile Level: L1 (Baseline) NIST 800-53: SC-28
ClickOps Implementation
Step 1: Payroll Access
- Navigate to: Settings → Permissions
- Limit payroll admin access
- Require approval for changes
4. Monitoring & Detection
4.1 Audit Logs
Profile Level: L1 (Baseline) NIST 800-53: AU-2, AU-3
ClickOps Implementation
Step 1: Access Audit Logs
- Navigate to: Settings → Audit Logs
- Review admin activities
- Monitor configuration changes
Detection Focus
-- Detect bulk data access
SELECT admin_email, action, record_count
FROM rippling_audit_log
WHERE action LIKE '%export%'
AND record_count > 50
AND timestamp > NOW() - INTERVAL '24 hours';
-- Detect app provisioning changes
SELECT admin_email, app_name, action
FROM rippling_audit_log
WHERE action IN ('app.add_user', 'app.remove_user')
AND timestamp > NOW() - INTERVAL '7 days';
Appendix A: Feature Availability
| Control | Availability |
|---|---|
| SAML SSO | ✅ |
| MFA | ✅ |
| Custom Roles | ✅ |
| Audit Logs | ✅ |
| SCIM | ✅ |
Changelog
| Date | Version | Maturity | Changes | Author |
|---|---|---|---|---|
| 2025-12-14 | 0.1.0 | draft | Initial Rippling hardening guide | Claude Code (Opus 4.5) |