Security
MandatoryThe only mandatory category, also called the Common Criteria. Protection of systems and data against unauthorised access, covering access controls, change management, and risk mitigation.
SOC 2 (System and Organization Controls 2) is an AICPA attestation that evaluates how a service organisation protects customer data against five Trust Services Criteria: Security, Availability, Processing Integrity, Confidentiality, and Privacy. A licensed CPA firm issues the report, and it is the default way SaaS and cloud providers prove their security to customers.
SOC 2 stands for System and Organization Controls 2. It is a framework from the American Institute of Certified Public Accountants (AICPA) for reporting on the controls a service organisation uses to protect customer data. A licensed CPA firm examines those controls against the Trust Services Criteria and issues a report with its opinion.
Unlike a certification, SOC 2 produces a detailed report rather than a certificate, and it is a restricted-use document shared with customers and prospects under NDA. For most SaaS and cloud businesses, a SOC 2 Type 2 has become the standard answer to the question every enterprise security team asks: "prove you protect our data."
"SOC 2 reports are designed to meet the needs of a broad range of users that need detailed information and assurance about the controls at a service organization."
SOC 2 is built on five Trust Services Criteria. Security is mandatory in every report; the other four are included only when they match the commitments you make to customers.
The only mandatory category, also called the Common Criteria. Protection of systems and data against unauthorised access, covering access controls, change management, and risk mitigation.
Whether the system is available for operation and use as committed. Relevant for organisations that make uptime or SLA commitments to customers.
Whether system processing is complete, valid, accurate, timely, and authorised. Relevant where the correctness of processing matters, such as transactions.
Protection of information designated as confidential, from collection through disposal. Relevant when you handle sensitive business data beyond personal information.
How personal information is collected, used, retained, disclosed, and disposed of, in line with your privacy notice and AICPA privacy criteria.
SOC 2 comes in two report types. The difference is time: design at a moment, versus operation over a period.
Assesses whether controls are suitably designed at a single point in time. Faster to obtain and useful to show intent, but it does not prove the controls actually operated.
Assesses whether controls operated effectively over a period, typically 3 to 12 months. Carries far more weight with customers because it proves the controls worked over time.
Many organisations get a Type 1 first to demonstrate progress, then complete a Type 2 over the following observation window. Most enterprise buyers ultimately want to see a current Type 2.
SOC 2 is one of three SOC reports. They answer different questions for different audiences.
| Report | Focus | Audience |
|---|---|---|
| SOC 1 | Controls relevant to financial reporting (ICFR) | Customers' auditors and finance teams |
| SOC 2 | Security and the other Trust Services Criteria | Customer security teams (under NDA) |
| SOC 3 | General-use summary of a SOC 2 | The public (marketing, websites) |
A SOC 2 report is a substantial document, not a one-page certificate. It typically contains the auditor's opinion, management's assertion, a description of the system, and, for a Type 2, the detailed tests the auditor performed and their results.
The two most common security assurances overlap heavily but differ in form. SOC 2 is an AICPA attestation report, strongest with North American and SaaS buyers. ISO 27001 is an internationally recognised, certifiable management-system standard.
SOC 2 gives customers a detailed report to review; ISO 27001 gives them a globally recognised certificate. Because their controls overlap, many organisations pursue both and reuse most of the same evidence. For the full breakdown, see ISO 27001 vs SOC 2 and our guide to what ISO 27001 is.
Six steps from scoping to a renewed report. Remember the report itself comes from a CPA firm; everything before it is the work of standing up and evidencing the controls.
Decide which Trust Services Criteria apply. Security is mandatory; add Availability, Processing Integrity, Confidentiality, or Privacy based on the commitments you make to customers.
Assess your current controls against the criteria, identify gaps, and decide whether to start with a Type 1 (point-in-time) or go straight for a Type 2 (over a period).
Implement the missing controls: access management, change management, monitoring, vendor management, and the policies that back them. Assign owners and close gaps to a plan.
For a Type 2, run the controls over the observation period (commonly 3 to 12 months) and collect the evidence that shows they operated consistently.
A licensed CPA firm performs the examination and issues the report. Only an AICPA-accredited auditor can produce a SOC 2 report; software prepares you for it, it does not issue it.
SOC 2 is not one-and-done. Most customers expect a current Type 2 each year, so keep controls operating and evidence flowing between audit periods.
RiskWatch maps the Trust Services Criteria to a shared control library, runs the readiness assessment, tracks remediation to closure, and keeps the evidence your CPA firm will ask for, with SOC 2 cross-mapped to ISO 27001 and your other frameworks.
The questions teams ask most on the road to their first report.
Trust Services Criteria mapped to a shared control library, a readiness assessment, remediation tracking, and the evidence your auditor expects. 30-day free trial, no credit card.
No credit card required · 30-day free trial · Cancel anytime