SOC 2: what it is, when you need it, what it is not
Not a certification. A report, over an observation period, with evidence sampled from it. What that means for planning.
SOC 2 usually turns up in the same sentence as an American customer asking “are you SOC 2?” and a one week deadline for the answer. It is worth being clear on what is being asked, because the correct answer is neither yes nor no, but “not yet, and the first useful report lands in month such and such”.
It is not a certification
ISO 27001 is certified: an accredited body audits you and issues a certificate. SOC 2 does not work that way. It is an attestation engagement performed by an accounting firm, which produces a report. There is no diploma and no public register you appear in. You get a document you send to the customer, usually under a confidentiality agreement.
Practical consequence: you cannot “be SOC 2 compliant”. You can hold a report, over a given period, against given criteria.
The criteria
The report is built on the Trust Services Criteria. Security is mandatory. On top of it you pick what is relevant to your service: availability, processing integrity, confidentiality, privacy.
The choice is not cosmetic. Every criterion added brings controls to demonstrate, and a criterion your customer never asked for is work nobody reads. The question to put to the customer before signing with an auditor is which criteria they need, not whether they need SOC 2.
Type I and Type II
| Type | What it says | When it makes sense |
|---|---|---|
| Type I | Controls are suitably designed, at a point in time | When you need something quickly and the customer accepts an interim step |
| Type II | Controls operated effectively over a period, typically three to twelve months | When the customer wants something they can rely on |
Almost every serious customer wants Type II. Type I is defensible as a stage, not as a destination.
The observation period
This is the concept that changes planning, and the one companies discover too late. In a Type II the auditor is not looking at how things stand on audit day. They look at the stated period and sample from it: access reviews, tickets, alerts handled, cases closed, approvals.
What did not happen during that period cannot be invented afterwards. If the quarterly access review did not run in two of the four quarters, the report will say so. Which yields the only useful planning rule: start the controls, then start the period.
How much of ISO 27001 carries over
A lot. If you run a working ISO 27001 management system, most of the controls a SOC 2 needs already exist, and the difference is in form: the auditor needs evidence that can be sampled across a period, not policies.
In Phalanx, some automated checks carry SOC 2 criteria references. In the compliance modules, evidence can be attached to the audit report as structured snapshots with its creation date.