ISO 27001 and SOC 2 answer the same buyer question, "can we trust you with our data?", in two different ways. ISO 27001 is a certificate that your information security management system meets an international standard; SOC 2 is a CPA firm's report on whether your controls meet the AICPA Trust Services Criteria. For most Canadian companies the choice comes down to who your buyers are, and many end up doing both from one control set.
This guide compares the two, explains the Canadian standards behind SOC reports, and sets out how to decide. For depth on SOC 2 itself, see what a SOC 2 report is and our SOC 2 readiness guide for Canadian SaaS.
What Each One Actually Is
ISO/IEC 27001:2022: A Certification of Your Management System
ISO/IEC 27001 sets requirements for an information security management system (ISMS): how you assess information risk, choose controls, run them and improve them. The current edition was published on October 25, 2022 (SGS, 2024). Its Annex A references the 93 controls of ISO/IEC 27002:2022, grouped in four clauses, down from 114 in the 2013 edition. The International Accreditation Forum set a 36-month transition: certification bodies had to transition certified clients by October 31, 2025, and all certifications based on the 2013 edition expire or are withdrawn at the end of that period (International Accreditation Forum, 2023). So as of November 16, 2026, any current certificate you are shown should reference the 2022 edition.
You do not have to implement every Annex A control. You document which ones apply, and why, in a Statement of Applicability tied to your risk treatment plan (Cloud Security Alliance, 2023). A certification body audits you and, if you conform, issues a certificate, normally valid for three years with surveillance audits in between (SGS, 2024). In Canada, the Standards Council of Canada accredits ISMS certification bodies against ISO/IEC 17021-1 and the ISO/IEC 27006 series (Standards Council of Canada, 2024). Check that your certification body is accredited by an accreditation body your buyers recognize.
SOC 2: An Attestation Report, Not a Certificate
SOC 2 is an examination by a CPA firm of a service organization's system and controls relevant to security, availability, processing integrity, confidentiality or privacy (AICPA, 2022). The criteria used are the AICPA's 2017 Trust Services Criteria with revised points of focus from 2022 (AICPA, 2023). The output is an auditor's opinion and a detailed report, not a certificate.
There are two types. A Type 1 report covers the description of your system and whether controls are suitably designed as of a specified date; a Type 2 also covers whether they operated effectively throughout a specified period (CPABC, 2021). Microsoft's own SOC 2 Type 2 page describes the same test: controls "operating effectively over a specified time period" (Microsoft Learn, 2025). In practice, most enterprise buyers ask for Type 2.
A SOC 2 report is detailed and written for informed users. The AICPA's lighter SOC 3 is the general-use version (AICPA, 2022). In practice, most companies share SOC 2 reports only under a non-disclosure agreement.
One change to watch: on October 26, 2026 the AICPA issued exposure drafts of proposed 2027 Trust Services Criteria (AICPA, 2026). As of November 16, 2026 they are proposals, not final criteria: comments are open until January 15, 2027, and if approved they would apply to engagements beginning on or after December 31, 2027, with early adoption permitted (AICPA, 2026). The 2017 criteria remain the ones in use.
How SOC Reports Work in Canada
"SOC" is an AICPA term. Canadian standards describe the work as reporting on controls at a service organization. CSAE 3416 is the Canadian standard most similar to SOC 1 (controls relevant to customers' financial reporting), and, as of CPABC's March 2021 guidance, Canadian standards did not have a dedicated SOC 2 equivalent, although an engagement under CSAE 3000 "could accomplish the same" (CPABC, 2021). These standards are published by CPA Canada, and CPABC states that a practitioner issuing a CSAE 3416 report in British Columbia must hold a public practice licence in the audit category.
So a Canadian company can get a SOC 2 style report from a Canadian CPA firm under CSAE 3000, or a SOC 2 report under AICPA standards from a firm that reports under them. Ask which standard the report will be issued under, and confirm your US customers will accept it.
Implement once, satisfy four frameworks
42 controls mapped to 236 requirements
MFA for remote and admin access
14 evidence items, auto-collected
Quarterly user access reviews
4 evidence items
Patching within defined SLAs
26 evidence items
Backups encrypted and restore-tested
6 evidence items
Security awareness training
9 evidence items
Incident response plan tested
3 evidence items
Side by Side
| ISO/IEC 27001 | SOC 2 | |
|---|---|---|
| What you get | Certificate stating scope | Auditor's opinion and detailed report |
| Issued by | Accredited certification body | CPA firm |
| Measured against | ISMS requirements plus Annex A controls you select | Trust Services Criteria (security always, others optional) |
| Time dimension | Certificate cycle with surveillance audits | Type 1 at a date; Type 2 over a period |
| Typical audience | International and global buyers | US buyers and their auditors |
| Shared how | Certificate is usually shareable | Report usually under NDA |
Who Asks for Which
In practice the pattern is simple: US enterprise buyers default to SOC 2, while European and other international buyers tend to expect ISO 27001. This reflects where each scheme comes from (an American accounting body versus an international standards body), not any rule.
Canadian buyers vary. The Canadian Centre for Cyber Security's cloud assessment process for federal departments listed both AICPA SOC 2 Type II reports and ISO/IEC 27001 reports among the third-party attestations it had compared against Government of Canada requirements (Canadian Centre for Cyber Security, 2018). That document dates from 2018, so treat it as evidence that both are recognized rather than as current procurement rules. If you sell mainly to Canadian SMBs, CyberSecure Canada may be a lighter and more relevant first step.
How Much the Two Overlap
A lot. Both expect risk assessment, policies, access control, logging and monitoring, change management, vendor management, incident response and business continuity. The differences are in emphasis. ISO 27001 puts more weight on the management system: scope, leadership, internal audit and management review. SOC 2 puts more weight on evidence that each control operated across the Type 2 period.
The AICPA publishes a spreadsheet mapping the Trust Services Criteria to ISO 27001 (AICPA, 2018). Two cautions. It is dated May 4, 2018 and is available to AICPA and CIMA members only. Because it predates the 2022 edition, it does not reflect the new Annex A numbering. We could not confirm that the AICPA has published an updated mapping for ISO/IEC 27001:2022 as of November 16, 2026. Many compliance platforms ship their own crosswalks; treat those as a starting point, not as the AICPA's view, and have your auditor agree the mapping you rely on.
Effort and Cost Drivers
We do not publish market prices because they are rarely comparable. These are the factors that move effort and fees:
- Scope. For ISO 27001, certification bodies start audit time from the number of people working under your control within the ISMS scope (European co-operation for Accreditation, 2018). For SOC 2, scope is the systems, people and locations behind the service described in the report.
- Criteria. Each Trust Services Criteria category beyond security adds testing.
- Report type and period. A SOC 2 Type 2 involves testing across a period, so longer periods mean more samples.
- Starting maturity. In practice, teams with SSO, MFA, central logging and ticketed changes already in place spend far less on remediation.
- Internal time. Policy writing, evidence collection and interviews fall on your staff; in practice this is often the largest hidden cost.
- Outside help and tooling. Readiness consultants, a vCISO and compliance platforms trade money for staff time.
- Recurring cycle. ISO 27001 has surveillance audits and recertification; SOC 2 Type 2 reports are, in practice, usually renewed each year.
Be wary of the cheapest, fastest audit. The AICPA's Peer Review Board is now looking more closely at SOC 2 practices, including identical reports across clients, heavy reliance on compliance tools and unreasonable engagement timelines (Journal of Accountancy, 2026). A report a buyer's auditor doubts is worth little.
How to Choose, or Do Both
Start with demand, not preference.
- Mostly US enterprise buyersstart with SOC 2, usually Type 1 and then Type 2.
- Mostly European or global buyersstart with ISO 27001.
- A mix, or regulated Canadian buyersask your three largest prospects what they accept. In practice, many will take either.
- Both demandedbuild one control set, map it to both, and line up audit timing so evidence is collected once. You still need two separate assessments.
What to Do Now
- List the security questionnaires and contract clauses from the last 12 months and note which framework each named.
- Ask your top prospects, in writing, which report or certificate they will accept and by when.
- Define a scope you can defend: one product or service, its systems, people and suppliers.
- Run a gap assessment against ISO 27001 requirements and the Trust Services Criteria together. Our article on which framework a small business should use helps if neither is required yet.
- Fix identity, logging, change management and vendor review first; they appear in both.
- Get quotes from at least two certification bodies or CPA firms against the same written scope, and ask about accreditation, reporting standard and timeline.
How Cyberphore Can Help
Our compliance readiness service covers gap assessment, remediation, evidence collection and audit support for ISO 27001 and SOC 2; the certificate or report itself always comes from an independent certification body or CPA firm. Pricing is quote-only after a free scoping call.


