The question usually arrives as one line in a security questionnaire: “Does your organization hold a SOC 2 report or ISO 27001 certification?” For a small firm the accurate answer is often neither, and the follow-up question is which one to pursue.
Both are respected, both cover information security, and a well-run firm could satisfy either with largely the same controls. They differ in who issues them, what they prove, how they are shared and which customers expect them. Those differences should decide your choice.
The short version#
SOC 2 is an American attestation report. A licensed CPA firm examines your controls against the AICPA’s Trust Services Criteria and writes an opinion. Customers in the United States, especially software buyers, ask for it most.
ISO/IEC 27001 is an international standard for an information security management system (ISMS). An accredited certification body audits you and issues a certificate. Customers outside the United States, larger enterprises and public bodies ask for it most.
If your clients are mostly American companies buying a service that holds their data, SOC 2 is the usual expectation. If your clients are international or ask for a certificate by name, ISO 27001 fits better. If you are a small professional firm answering occasional questionnaires, you may not need either yet.
Side by side#
| SOC 2 | ISO/IEC 27001:2022 | |
|---|---|---|
| What it is | An attestation report on your controls | A certification of your management system |
| Who issues it | An independent CPA firm | An accredited certification body |
| What it measures | Controls against the Trust Services Criteria you choose | Whether your ISMS meets the standard’s requirements, with controls chosen through risk assessment |
| Scope options | Security is required; Availability, Processing Integrity, Confidentiality and Privacy are optional | You define the scope of the ISMS (sites, teams, services) |
| Main versions | Type I (design at a point in time) and Type II (operation over a period) | One certificate, maintained through yearly audits |
| Control set | Criteria-based; you describe your own controls | Annex A lists 93 controls in four themes; you justify each one’s use or exclusion |
| What customers receive | A detailed report, usually under NDA | A public certificate, plus your Statement of Applicability on request |
| How long it lasts | Each report covers one period; most firms renew yearly | Three years, with surveillance audits in years one and two |
| Where it’s expected | Mainly the United States | Worldwide |
How SOC 2 works#
SOC 2 comes from the American Institute of Certified Public Accountants. The examination tests your controls against the Trust Services Criteria. Security, often called the common criteria, is always in scope. You add Availability, Processing Integrity, Confidentiality or Privacy when your customers care about them.
There are two report types. A Type I report says your controls were suitably designed on a specific date. A Type II report says they operated effectively over an observation period, commonly somewhere between three and twelve months. Most customers who ask for SOC 2 want Type II, because it shows the controls work in practice and not only on paper.
The report itself is long and detailed. It describes your system, lists your controls, records the tests the auditor ran and notes any exceptions. Because it reveals how your security works, you normally share it under a nondisclosure agreement.
SOC 2 suits service organizations: software companies, managed IT providers, payroll processors, cloud document platforms and anyone else whose customers hand over data and need assurance about how it is handled.
How ISO 27001 works#
ISO/IEC 27001 is published by the International Organization for Standardization and the International Electrotechnical Commission. The current edition is ISO/IEC 27001:2022. The three-year transition from the 2013 edition ended on October 31, 2025, so 2013 certificates are no longer valid.
The standard has two parts. Clauses 4 to 10 set out how to run an ISMS: understanding your context, leadership commitment, risk assessment and treatment, support, operation, performance evaluation and improvement. These clauses are mandatory. Annex A then lists 93 controls grouped into four themes:
- Organizational (37 controls)
- People (8 controls)
- Physical (14 controls)
- Technological (34 controls)
You decide which Annex A controls apply based on your risk assessment, and you record the reasons in a Statement of Applicability. The 2022 edition added 11 controls that didn’t exist in 2013, including threat intelligence, cloud service security and data masking.
Certification takes two audit stages. Stage 1 reviews your documentation and readiness. Stage 2 checks that the ISMS operates as documented. If you pass, the certificate lasts three years, with surveillance audits in the first and second years and a recertification audit in the third.
ISO 27001 suits organizations with international customers, those selling to large enterprises or government bodies that require a certificate, and firms that want a management system they can grow into.
What the two have in common#
The overlap is large. Both expect you to:
- assess security risks and act on them
- control who can access systems and data, including MFA and prompt removal of leavers
- manage vendors and other third parties
- train staff
- log, monitor and respond to incidents
- back up data and plan for recovery
- manage changes to systems
- keep written policies and show they are followed
Firms that end up needing both usually build one control set and map it to each framework, so the second framework takes much less work than the first.
How they differ in practice#
The biggest practical difference is what the customer gets. A SOC 2 Type II report lets a customer’s security team read exactly what you do and how the auditor tested it. An ISO certificate tells them an accredited body found your management system meets the standard, and they can request your Statement of Applicability for detail.
The second difference is philosophy. SOC 2 asks whether your controls meet the criteria. ISO 27001 asks whether you run a management system that finds and treats risk, and keeps improving. ISO puts more weight on governance: management reviews, internal audits, documented risk treatment and corrective action.
The third is geography. American buyers, especially in software, default to SOC 2. Buyers in Europe, the United Kingdom, Africa, the Middle East and Asia more often ask for ISO 27001.
Which should a small firm choose?#
Answer these questions in order.
Has a customer asked for one by name?#
If a client or prospect requires SOC 2 or ISO 27001 in a contract, that settles it. Ask which version and scope they need before you start, because a SOC 2 Type I may satisfy a first-year contract while you work toward Type II.
Do you sell a service that holds customer data?#
Software products, hosted platforms and managed IT services face SOC 2 requests from American customers far more often than professional firms do.
Where are your customers?#
Mostly American suggests SOC 2. International suggests ISO 27001.
Are you a professional firm answering occasional questionnaires?#
Law firms, accounting practices and clinics are rarely required to hold either. What they need is a documented security program that can answer questionnaires, satisfy cyber insurers and meet regulatory duties such as HIPAA. Building that program on a framework like NIST CSF 2.0 gives you a structure that maps to both SOC 2 and ISO 27001 later.
A practical path for most small firms
Write your policies and controls once, against a recognized framework. Close the gaps your insurer and clients ask about first. When a customer requires SOC 2 or ISO 27001, you’ll be starting from a mapped program instead of from zero.
What gets small firms into trouble#
The most common mistake is buying policy templates, filling in the firm’s name and assuming the job is done. Auditors test whether you follow your policies, and a template that promises quarterly access reviews you never perform becomes a finding against you.
The second is choosing a scope that is too broad. For a first ISO 27001 certification or SOC 2 report, scope the service or team your customers care about. You can widen it later.
The third is underestimating the evidence. Both frameworks run on proof: access review records, training logs, incident tickets, vendor reviews and backup tests. Start collecting it the day you decide, because a Type II observation period or a Stage 2 audit will ask for months of history.
Checking your policies before an auditor does#
Before an auditor or a client’s security team reads your policies, it helps to know where they fall short. A policy can be silent on a required element, cover it partly, or contradict another document.
PolicyPilot reads policies against both frameworks. Its library checks 41 SOC 2 controls and 53 ISO 27001 controls, among others, and quotes the sentence behind each verdict. It reviews what your documents say, which is where every audit starts. It isn’t an audit, and covered controls still need evidence that they operate.
Questions people ask
Is SOC 2 a certification?
No. SOC 2 is an attestation report written by an independent CPA firm. There is no SOC 2 certificate. You receive a report that describes your controls and the auditor's opinion on them, and you share it with customers under a nondisclosure agreement.
How long is an ISO 27001 certificate valid?
Three years. The certification body runs a surveillance audit in each of the two years after certification and a full recertification audit in the third year.
Is my old ISO 27001:2013 certificate still valid?
No. The transition period to ISO/IEC 27001:2022 ended on October 31, 2025, and certificates issued against the 2013 edition are no longer valid. Organizations that missed the transition need a new certification against the 2022 edition.
Can one set of controls satisfy both?
Largely, yes. Most of the work, such as access control, risk assessment, incident response, vendor management and backups, serves both. Firms that plan for both usually build one control set and map it to each framework.
Do law firms and accounting firms need SOC 2?
Usually not by default. SOC 2 is designed for service organizations that hold or process customer data, such as software companies and managed IT providers. Professional firms are more often asked to complete a client security questionnaire, and some large clients ask for ISO 27001.
Sources
Keep reading
This guide is general information for small firms. It is not legal, insurance or compliance advice for your situation.