Skip to content
SOC 2 Compliance Software

Home / Glossary / SOC 1 report

Glossary, read 12 Nov 2026

SOC 1 report in a SOC 2 examination, defined with a sourced example

All termsRead the guides

The definition of SOC 1 report

SOC 1 is about money, not security in general. If your product handles payments, payroll, billing calculations or anything a customer's financial statements depend on, that customer's auditor will ask for a SOC 1. Controls are written as control objectives tied to financial reporting, such as accurate processing of transactions, rather than the Trust Services Criteria categories.

Founders often assume a SOC 2 covers this request. It does not, because the two reports answer different questions for different readers. The first is aimed at the user entity's finance team and its external auditors, and the second at security and vendor risk teams. Ask the customer which report they mean before you scope anything.

An auditor testing a SOC 1 looks at the controls that feed the customer's ledger: who can change a pricing table, how a failed batch is caught, how reconciliations are signed off. Many companies need both reports, and the two examinations can share evidence, such as the access review, where the controls overlap.

A sourced example

AWS's SOC table says the SOC 1 audit is performed under "SSAE No. 18, Attestation Standards: Clarification and Recodification", which includes "AT-C section 320, Reporting on an Examination of Controls at a Service Organization Relevant to User Entities' Internal Control Over Financial Reporting". SOC 2 on the same table points to AT-C section 205 instead. AWS SOC compliance page, read 12 Nov 2026.

Sources

  1. AWS SOC compliance page, read 12 Nov 2026
  2. AICPA SOC 1 page, read 12 Nov 2026

Last reviewed 12 Nov 2026.