Glossary · SOC and attestation

Buyers use SOC 2 to judge your security without walking into your office.

A licensed CPA firm's examination of how a service organization's controls measure up to the AICPA's Trust Services Criteria, covering security plus as many as four further categories.

Back to the glossary

01 · In plain words

In plain words

A licensed CPA firm's examination of how a service organization's controls measure up to the AICPA's Trust Services Criteria, covering security plus as many as four further categories.

Customers need reassurance that their data is safe with you. A SOC 2 is what an outside auditor concludes after checking your controls against published criteria. You hand it to customers rather than answering the same questions over and over.

Spelled out: System and Organization Controls 2, an auditor's report on controls in the areas of security, availability, processing integrity, confidentiality or privacy.

02 · Why it matters

Why it matters

Who cares about this, and what depends on it.

Software companies that sell to other businesses usually meet SOC 2 when a buyer's security reviewer wants it on the table before a contract is signed. Security is always covered; a company can also opt for Availability, Processing Integrity, Confidentiality or Privacy where customers care about them. The report goes deep: your system description, your controls and, in a Type 2, the auditor's tests and any exceptions. That depth is both its strength and its limit. It is written for informed readers, so it travels under a non-disclosure agreement, and it describes a period that has already passed rather than promising the future.

03 · Where you meet it

Where you will meet it

The documents, meetings and reports where it appears.

An enterprise security questionnaire
Plenty of questions can be answered by citing the matching control in the report.
The procurement stage of a sale
The buyer's vendor risk team asks for your newest report and reads the opinion and any exceptions.
A trust centre or data room
Customers and prospects can download the report once they accept an NDA.
Master services agreements
Contract clauses frequently oblige the supplier to keep a valid SOC 2 report in place year after year.

04 · An example

A worked example

An illustration, not a real client.

Illustrative: an HR software company courting a private bank

A people-management SaaS company in Mumbai reaches the final stage with a private bank. The bank's vendor team sends a long questionnaire and requests a SOC 2 Type 2 report. The company has none yet, so it agrees a plan: a readiness review, then a first period, then the report from a CPA firm. Meanwhile it shares its policies and a letter describing the planned audit, careful not to claim a report it does not yet have.

05 · Easy to mix up

Easy to mix up with

Neighbouring terms that mean something different.

ISO 27001
ISO 27001 leads to a certificate from an accredited certification body for a management system. SOC 2 is an auditor's opinion, with no certificate.
SOC 3
A SOC 3 uses the same criteria but leaves out the detail, so it can be published openly.

06 · What to do

What to do with it

Practical steps, and the guides that go deeper.

  • Decide which categories beyond Security your customers really need.
  • Draw the system boundary: products, infrastructure, people and vendors in scope.
  • Run a readiness assessment before choosing the observation period.
  • Plan how you will share the report: NDA, trust centre, and who answers follow-up questions.

Sources: AICPA SSAE 18, AT-C section 105 and AT-C section 205; AICPA SOC 2 guide; AICPA TSP section 100, 2017 Trust Services Criteria (revised points of focus, 2022); DC 200 description criteria.

Questions about SOC 2

Is SOC 2 a certification?

No. It is an attestation report.

A licensed CPA firm gives an opinion on your controls. There is no certificate and no pass mark. Saying you are SOC 2 certified is inaccurate; say you have a SOC 2 report covering a stated period.

Is SOC 2 required by law?

No law requires it.

SOC 2 is voluntary. It is usually required by customer contracts or expected during procurement, not by a regulator.

Want this applied to your own systems?

Our team can walk through where this term touches your scope, your contracts and your evidence.