# SOC 2 with Rippling and AI

> SOC 2 with Rippling and no compliance platform: people, device and access evidence, prepared with AI, and which offer applies. Audit from $4,400.

- Canonical: https://auditsuisse.com/soc-2-with-rippling-and-ai
- Language: en
- Author: Sébastien Ruosch, CPA — Director of Audits
- Published: 2026-11-15
- Updated: 2026-11-15
- Alternates: fr → https://auditsuisse.com/fr/soc-2-avec-rippling-et-l-ia, es → https://auditsuisse.com/es/soc-2-con-rippling-e-ia

SOC 2 on your stack

 The short answer

You can prepare the people, device and access evidence for SOC 2 from Rippling without a compliance platform: export each population, record its source, filter, date and count, have a person review it, and send it unedited. An AI assistant can help structure each package. Rippling’s HR, device and identity data does not cover cloud configuration, code changes, vulnerability management, incident response, reviews of vendors’ reports or the risk assessment. This route is audited on the Zero-Platform schedule. The [Rippling SOC 2 audit promo](https://auditsuisse.com/rippling-soc-2-audit) is a separate offer, for companies that run their SOC 2 on Rippling Automated Compliance.

## Key takeaways

- Where Rippling is your system of record, it holds the records for onboarding, training, policy acknowledgements, offboarding, access and devices.
- An auditor works from populations for the period. Export each one and keep its filter, date and record count with it.
- An assistant structures the package. A person reviews it. Nothing in an export is edited.
- Without a compliance platform, the Zero-Platform fee applies. The Rippling promo is for companies using Rippling Automated Compliance.

## What SOC 2 evidence can we export from Rippling without a compliance platform?

Each row is an area where a company that runs HR, devices and identity on Rippling keeps its records there. The [guide to SOC 2 evidence from Rippling](https://auditsuisse.com/rippling-soc-2-evidence-guide) maps each area to the Trust Services Criteria.

Evidence from Rippling by area: the artifact an auditor asks for and what to check before you send it.

| Area | Artifact an auditor asks for | Check before you send it |
| --- | --- | --- |
| Onboarding and background checks | The new-hire population for the period. For the people selected, the completed background check. | The date range covers the whole period, and contractors are included or listed separately. |
| Security training | Assignment and completion records for everyone in scope. | Late joiners and overdue people appear in the export. |
| Policy acknowledgements | Acknowledgement records per employee, for each policy. | The version acknowledged is the version in force. |
| Offboarding and access removal | The termination population with each last day. For the people selected, the time each account was removed. | Every employment type appears. Removals in systems outside Rippling are evidenced from those systems. |
| Access provisioning and reviews | Access requests and approvals. For each periodic review: who performed it, what changed, and the account list it ran against. | The account list is the one the reviewer worked from, with its export date. |
| Device inventory and compliance | The device inventory with compliance status (encryption, screen lock, OS updates), and return and wipe records for leavers’ devices. | Every device in use appears, including those out of compliance. |

For a Type II report, each population covers the whole period, not only the day of the export.

## How do we turn a Rippling export into an evidence package, and which prompts help?

A package is the export plus a cover note. The note records the source (the Rippling report or screen), the filter, the period covered, the date and time of the export and the record count. A named person reviews the package before it goes to the auditor. The export is never edited: if it shows a gap, such as an account removed late, the gap stays and you tell the auditor. 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).

HR exports contain personal data. The prompts below need only the report name, filter, counts and column headings. Read [is it safe to put security documents into ChatGPT or Claude](https://auditsuisse.com/is-it-safe-to-use-ai-for-soc-2) before you paste more.

### Prompt: cover note for a Rippling export

```
You are helping my team prepare a SOC 2 evidence package from an export we took from Rippling. I will give you the report name, the filter, the export date and time, the record count and the column headings, not the employee rows.

Ask me how this process works at our company today: who runs it, where each step is recorded, and who is in scope (employees, contractors, locations). Wait for my answers.

Then draft a one-page cover note with these fields: area, source, filter, period covered, export date and time, record count, exported by, reviewed by, review date. Leave the reviewer fields blank. Add the questions a reviewer should answer before signing, such as whether the filter leaves out anyone who belongs in the population.

Do not change any row or value in the export. Do not describe a control as working. Mark every assumption as [ASSUMPTION].
List anything you assumed that I need to verify.
```

### Prompt: compare leavers with access removals

```
I have two exports for our SOC 2 period: the people who left, from Rippling, and the account removals from our other systems.

Ask me which systems hold accounts for our people and how access is removed today, step by step, before you suggest anything.

First tell me what to note for each list: source, filter, export date and record count.

Then explain how a person can compare the two lists in a spreadsheet: the matching key, the columns needed, and the differences to look for (a leaver with no removal, a removal dated after the last day, an account that matches no person).

Do not fill in missing dates or values, and do not conclude whether access was removed on time; a person on my team decides. Mark every assumption as [ASSUMPTION].
List anything you assumed that I need to verify.
```

AI-written policies and descriptions are acceptable only if they describe what your company actually does. The audit tests how controls operate, not how documents read.

## What does Rippling data not cover for SOC 2?

Rippling’s HR, device and identity data covers people, devices and access. Evidence for the rest comes from other systems and documents:

- Cloud configuration: see SOC 2 with AI on [AWS](https://auditsuisse.com/soc-2-with-ai-on-aws), [Google Cloud](https://auditsuisse.com/soc-2-with-ai-on-google-cloud) or [Azure](https://auditsuisse.com/soc-2-with-ai-on-azure).
- Code changes and vulnerability management: your source control, pipeline and scanner. See [common SOC 2 findings](https://auditsuisse.com/soc-2-common-findings-and-how-to-fix-them).
- Incident response: the plan, the incident log and the record of each incident.
- Reviews of vendors’ reports: a control you perform, with Rippling among the vendors. See [vendor management for SOC 2](https://auditsuisse.com/vendor-management-for-soc-2-compliance).
- The risk assessment: see [SOC 2 risk assessment with AI](https://auditsuisse.com/soc-2-risk-assessment-with-ai).

The [guide to SOC 2 with AI](https://auditsuisse.com/soc-2-with-ai) covers the whole preparation.

## Which audit offer applies to a company on Rippling?

It depends on whether you run your SOC 2 on Rippling Automated Compliance, Rippling’s compliance platform.

- **With Rippling Automated Compliance:** the [Rippling SOC 2 audit promo](https://auditsuisse.com/rippling-soc-2-audit) applies, on the conditions stated on that page.
- **With Rippling and no compliance platform**, the route this guide describes: the [Zero-Platform SOC 2 audit](https://auditsuisse.com/zero-platform-soc-2-audit) applies. Using Rippling for HR, devices or identity does not qualify for the promo on its own.
- **With Rippling and another compliance platform:** our [standard fee](https://auditsuisse.com/soc-2-pricing) applies.

Rippling introduced Automated Compliance on April 28, 2026, starting with SOC 2. Its [product page](https://www.rippling.com/products/it/automated-compliance) describes a built-in audit portal and says that independent auditors determine scope, perform the audit and issue the report.

## Who does what

Auditsuisse explains the criteria and sends its evidence request list once engaged. Your management designs and operates the controls; the firm does not run your onboarding or offboarding, configure Rippling or choose your controls.

Who does what when you prepare SOC 2 evidence from Rippling.

| Task | Your team (with or without AI) | Your AI assistant | The auditor |
| --- | --- | --- | --- |
| Export the populations | Runs each export from Rippling and keeps the file as exported | Needs no access to Rippling | Requests each population for the period |
| Write the cover note | Fills in and verifies source, filter, date and count | Drafts the template and the reviewer’s questions | Compares the filter and the count with the export and the period |
| Review before sending | A named person reviews and signs each package | Suggests comparisons between lists | Tests each population for completeness and accuracy before relying on it |
| Operate the controls | Performs onboarding, training, offboarding and access reviews through the period | Explains a criterion or drafts a checklist for your team | Selects items from each population and inspects the record behind each one |

## Zero-Platform SOC 2 Audit: the fee

A Zero-Platform SOC 2 audit from Auditsuisse costs $4,400 for Type I and $5,500 for Type II for companies of up to 50 people, fixed fee, Security criteria.

No compliance platform is required, so you save the platform fees, which start at about $10,000 to $15,000 a year for a GRC platform (an illustrative figure, not any vendor’s price).

Zero-Platform SOC 2 Audit fees for companies with 1–50 employees (USD, fixed fee, Security Trust Services Category). Fees as of November 15, 2026.

| Company headcount | SOC 2 Type I | SOC 2 Type II | Type I + Type II (combined) |
| --- | --- | --- | --- |
| 1–50 employees | $4,400 | $5,500 | $7,700 |

[See all headcount tiers](https://auditsuisse.com/zero-platform-soc-2-audit#fees)

Fees as of November 15, 2026.

## Free kit: prepare for SOC 2 without a platform

The prompt library from these guides, a policy index, the gap-assessment scoring sheet, the risk register template and the cost worksheet, as CSV and Markdown, with a short guide to the workflow. Free to use with attribution; not a substitute for an examination. Our evidence request list is not part of the kit: you receive it once the engagement letter is signed.

## Frequently asked questions

### Do we need Rippling Automated Compliance or another compliance platform to send this evidence?

No. The evidence can be exported from Rippling and shared with the audit team directly. A compliance platform organizes evidence and reminders; it is not a requirement of the examination. See [compliance automation software for SOC 2](https://auditsuisse.com/compliance-automation-software-for-soc-2).

### Which fee applies if we are on Rippling and have no compliance platform?

The Zero-Platform fee. The Rippling promo is only for companies that run their SOC 2 on Rippling Automated Compliance.

### Can Rippling issue our SOC 2 report?

No. A SOC 2 report is issued by an independent licensed CPA firm after an examination. See [who can perform a SOC 2 audit](https://auditsuisse.com/who-can-perform-a-soc-2-audit).

## 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); SSAE No. 18, AT-C sections 105 and 205. Rippling, [“Introducing Rippling Automated Compliance, Starting with SOC 2”](https://www.rippling.com/blog/get-soc-2-ready-with-rippling-no-assembly-required) (April 28, 2026) and [Automated Compliance product page](https://www.rippling.com/products/it/automated-compliance), read on November 15, 2026.

**Related:** [SOC 2 evidence from Rippling, control by control](https://auditsuisse.com/rippling-soc-2-evidence-guide), [SOC 2 with AI](https://auditsuisse.com/soc-2-with-ai), [Collect SOC 2 evidence with an AI agent](https://auditsuisse.com/soc-2-evidence-collection-with-ai-agents).

Product names are trademarks of their owners. Auditsuisse is not affiliated with these vendors.

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