# SOC 2 Evidence from Rippling, Control by Control

> How Rippling HR, device and access records map to the SOC 2 Trust Services Criteria, what an auditor asks for, and what Rippling does not cover.

- Canonical: https://auditsuisse.com/rippling-soc-2-evidence-guide
- Language: en
- Author: Sébastien Ruosch, CPA — Director of Audits
- Published: 2026-11-15
- Updated: 2026-11-15

SOC 2 evidence

 The short answer

Where Rippling is your system of record, it holds the evidence for the people, device and access parts of a [SOC 2 examination](https://auditsuisse.com/soc-2): onboarding and background checks, security training, policy acknowledgements, offboarding, access provisioning and reviews, and device compliance. The table below maps each area to the Trust Services Criteria it supports and to the record an auditor asks for. Evidence for your cloud infrastructure, code changes, vulnerabilities, incidents, vendor reviews and risk assessment comes from other systems and documents.

## Key takeaways

- Rippling’s HR, device and identity data covers people, devices and access. It does not cover your cloud, code, vulnerabilities, incidents, vendor reviews or risk assessment.
- An auditor works from populations: the full list of joiners, leavers, devices or access changes for the period. Export each one from the system with its date and record count.
- For a Type II report the evidence has to cover the whole period, not only the day of the export.
- This evidence reaches an auditor through Rippling Automated Compliance’s audit portal or, without a compliance platform, as exports.

## Rippling SOC 2 compliance evidence, mapped to the Trust Services Criteria

Each row is an area where a company that runs HR, devices and identity on Rippling keeps its records there. The criteria are the common criteria of the [Trust Services Criteria](https://auditsuisse.com/soc-2-trust-services-criteria) that the area usually supports.

Areas of SOC 2 evidence held in Rippling, the Trust Services Criteria they support and the evidence an auditor asks for.

| Area | Criteria | Evidence an auditor asks for |
| --- | --- | --- |
| Onboarding and background checks | CC1.4 | New-hire population for the period, completed checks |
| Security awareness training | CC1.4, CC2.2 | Assignment and completion records |
| Policy acknowledgement | CC2.2, CC5.3 | Acknowledgement records per employee |
| Offboarding and access removal | CC6.2, CC6.3 | Termination population with dates, deprovisioning timestamps |
| Access provisioning and reviews | CC6.2, CC6.3 | Access requests and approvals, periodic review records |
| Device encryption, screen lock, OS updates | CC6.7, CC6.8 | Device inventory with compliance status |
| Device return and wipe | CC6.5 | Offboarding device records |

One control can support more than one criterion, and your auditor maps your own controls to the criteria in the report. For the full set, see the [SOC 2 controls list by Trust Services Criteria](https://auditsuisse.com/soc-2-controls-list-by-trust-services-criteria).

## How an auditor uses this evidence

For each area the auditor first obtains the population for the period, then selects items from it and inspects the record behind each one. For onboarding, that means the list of everyone hired in the period and, for the people selected, the completed background check and the signed policy acknowledgements. For offboarding, it means the list of leavers with their last day and, for those selected, the time at which each account was removed.

Access reviews work the same way: the auditor asks for the review itself, who performed it, what was changed as a result, and the list of accounts it was run against. The [user access review procedure for SOC 2](https://auditsuisse.com/soc-2-user-access-review) describes what that record should contain.

Auditsuisse audits companies that run on Rippling from this evidence. Those that run their SOC 2 on Rippling Automated Compliance pay a [lower fixed fee](https://auditsuisse.com/rippling-soc-2-audit).

## Evidence quality: populations with a date and a record count

A population is only useful if the auditor can tell that it is complete. Three habits make that possible:

- **Export from the system.** A list retyped into a spreadsheet cannot be traced back to its source.
- **Keep the date and time of the export and the number of records.** The auditor compares the count with the system and checks that the export covers the period.
- **Show the filters or parameters used.** A leaver list filtered to one department is not the leaver population.

Auditors call such lists information produced by the entity (IPE) and test that they are complete and accurate before relying on them. See [tests of controls, IPE and IUC](https://auditsuisse.com/tests-of-controls-ipe-iuc) and [audit evidence management best practices](https://auditsuisse.com/audit-evidence-management-best-practices).

## What Rippling’s HR, device and identity data does not cover

A SOC 2 examination against the Security criteria also needs controls and evidence that HR, device and identity records do not hold:

- **Cloud infrastructure configuration**: network rules, encryption, logging and backups in your cloud accounts. See [SOC 2 on AWS and Azure](https://auditsuisse.com/soc-2-on-aws-and-azure).
- **Code change management**: reviews, approvals and deployment records from your source control and pipeline. See the [change management findings](https://auditsuisse.com/soc-2-common-findings-and-how-to-fix-them#change-management) auditors report most often.
- **Vulnerability management and penetration testing**: scan results, remediation records and the test report. See [SOC 2 penetration testing requirements](https://auditsuisse.com/soc-2-penetration-testing-requirements).
- **Incident response**: the plan, the incident log and the records of each incident. See the [system operations criteria (CC7)](https://auditsuisse.com/soc-2-controls-list-by-trust-services-criteria#cc7).
- **Vendor risk**: your review of each vendor’s own report, and the follow-up, is a control you perform, wherever the vendor list is kept. See [vendor management for SOC 2](https://auditsuisse.com/vendor-management-for-soc-2-compliance).
- **Risk assessment**: the documented assessment and how its results drive your controls. See [SOC 2 risk assessment](https://auditsuisse.com/soc-2-risk-assessment).

Which of your systems fall inside the report is a scoping decision. [How to scope systems for SOC 2](https://auditsuisse.com/how-to-scope-systems-for-soc-2) explains it, and [Is Rippling enough for SOC 2?](https://auditsuisse.com/is-rippling-enough-for-soc-2) sets the covered and uncovered areas side by side.

## SOC 2 on Rippling Automated Compliance: fixed fee from $3,000, web app pen test included

Auditsuisse’s fixed fees for a SOC 2 audit of a US company that runs its SOC 2 program on Rippling Automated Compliance, by company headcount, against the Security criteria. A manual web application penetration test, worth $8,000, is included free with every engagement. The fees are not for companies that use Rippling without Automated Compliance.

Auditsuisse SOC 2 fees for companies on Rippling Automated Compliance (USD, fixed fee, Security Trust Services Category). The regular fee is struck through and the Rippling fee follows it. Offer ends January 31, 2027.

| Company headcount | SOC 2 Type I | SOC 2 Type II | Type I + Type II (combined) |
| --- | --- | --- | --- |
| 1–50 employees | Regular fee $4,000 Rippling fee $3,000 | Regular fee $5,000 Rippling fee $4,000 | Regular fee $7,000 Rippling fee $5,500 |
| 51–100 employees | Regular fee $5,000 Rippling fee $4,000 | Regular fee $7,500 Rippling fee $6,000 | Regular fee $10,000 Rippling fee $8,000 |
| 101–200 employees | Regular fee $7,000 Rippling fee $5,500 | Regular fee $10,000 Rippling fee $8,000 | Regular fee $15,000 Rippling fee $12,000 |
| More than 200 employees | [Talk to us](https://auditsuisse.com/rippling-soc-2-audit#scoping) |  |  |
| Manual web application penetration test | **Included free** with every engagement (list value $8,000) |  |  |

Fees as of November 14, 2026. Offer ends January 31, 2027.

[See the conditions and check your fee →](https://auditsuisse.com/rippling-soc-2-audit)

## Frequently asked questions

### Does Rippling evidence cover a whole SOC 2 audit?

No. Rippling’s HR, device and identity data covers the people, device and access controls. Your cloud configuration, code changes, vulnerability management, incident response, vendor reviews and risk assessment are evidenced from other systems and documents.

### Do I need Rippling Automated Compliance to give this evidence to an auditor?

No. The evidence can be exported from Rippling and shared with the audit team directly. Auditsuisse works in Rippling Automated Compliance or from exports. The Rippling fee is only for companies that use Automated Compliance; without it, our standard fee applies with another compliance platform, and our [fee for audits without a platform](https://auditsuisse.com/zero-platform-soc-2-audit) with none.

### How far back does the evidence need to go?

For a Type I report, the evidence shows the controls as of the report date. For a Type II report, each population covers the whole period, and the samples are drawn from across it. See [what a SOC 2 Type 2 report covers](https://auditsuisse.com/what-is-soc-2-type-2).

## Sources & further reading

AICPA, [2017 Trust Services Criteria with revised points of focus (2022)](https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022). Rippling, [Automated Compliance product page](https://www.rippling.com/products/it/automated-compliance), read on November 14, 2026.

**Related:** [What is SOC 2 Type 2?](https://auditsuisse.com/what-is-soc-2-type-2), [SOC 2 Trust Services Criteria](https://auditsuisse.com/soc-2-trust-services-criteria), [Glossary](https://auditsuisse.com/glossary).

---
Source: https://auditsuisse.com/rippling-soc-2-evidence-guide · This Markdown edition is generated from the same content as the HTML page.
