SOC 1 vs SOC 2, and Type I vs Type II

SOC 1 is about controls that affect a customer's financial statements. SOC 2 is about security and the data you hold.

// FRAMEWORK

SOC 1

A SOC 1 report is for service companies whose systems feed into their customers' financial statements. Think payroll processors, billing platforms, payment processors, loan servicing and claims processing.

The reader is usually the customer's financial auditor. If a public company outsources payroll, its auditors need comfort that the payroll provider's controls are sound, because payroll costs land in the accounts.

SOC 2

A SOC 2 report is about security and the handling of data. The reader is the customer's security or procurement team. Most SaaS companies need SOC 2, not SOC 1.

A company can need both. A payroll SaaS might give SOC 1 to customers' financial auditors and SOC 2 to their security teams.

SOC 3

A SOC 3 is a short, general-use version of a SOC 2. It carries the auditor's opinion but none of the detail, so it can go on a website. Serious buyers still ask for the SOC 2.

Type I vs Type II

Both SOC 1 and SOC 2 come in two types.

Type I Type II
Tests Design Design and operation
Covers One date A period, often 6 or 12 months
Evidence Policies, configs, walkthroughs Samples across the whole period
Buyer trust A first step What most contracts require

A common path is a Type I first, to get something into buyers' hands quickly, followed by a Type II a few months later.

// REMEMBER THIS

SOC 1 follows the money. SOC 2 follows the data. Type I is a photo, Type II is a film.

// CHECK YOURSELF

1. A payroll provider's customers' financial auditors want assurance. Which report?

2. Which report can be posted publicly on a website?

3. A Type I report tells you...