This is a sequencing decision, not a comparison. In almost every real case the answer is set by your pipeline rather than by the frameworks: whichever standard is named in the deal that is currently blocked goes first, because the second one is always cheaper once the first exists.
They are different species. SOC 2 is an attestation examination performed by a licensed CPA firm under AT-C sections 105 and 205 (as revised by SSAE 21). ISO/IEC 27001 is a certification issued by an accredited certification body operating under ISO/IEC 17021-1. One produces a restricted-use report on a stated period, the other a publishable certificate covering a three-year cycle. Neither statement contains the other.
Decision guide · AT-C 205 attestation vs ISO/IEC 17021-1 certification · Last reviewed August 2026
Do the one your blocked deal is asking for. If a US enterprise buyer’s security review is holding a contract, start with SOC 2. If a UK, EU, Gulf or Indian tender names ISO/IEC 27001 — or the buyer is public sector — start with ISO 27001. If nothing is blocked, choose the one your next four quarters of pipeline will ask for, and design the control set so the other becomes a wrapper rather than a rebuild. Everything else — cost, elegance, which standard is “more respected” — is second order. The two overlap heavily at the control layer and not at all at the machinery layer, which is why the sequence matters less to your total cost than teams expect, and why the order in which you meet buyers matters more. For a feature-by-feature view, read SOC 2 vs ISO 27001. This page assumes you already know you need one and are deciding which comes first.
Key Takeaways
- The sequencing question is answered by your pipeline, not by the frameworks: whichever standard is named in the deal that is currently blocked goes first, because the second is materially cheaper once the first control set runs.
- They signal to different buyers. SOC 2 is the language of US enterprise procurement and its vendor-risk questionnaires. ISO/IEC 27001 is the language of UK, EU, Gulf and Indian tenders and a scored line item in public-sector evaluation matrices.
- They also behave differently once you hold them: the certificate is a public artefact you can publish and a buyer can verify on a register, while a SOC 2 report is restricted-use, goes out under NDA, and does its work one deal at a time.
- Most technical control work transfers — risk assessment, access control, change management, vendor management, incident response, logging — because one implementation satisfies Annex A of ISO/IEC 27001:2022 and the 2017 trust services criteria (with revised points of focus, 2022) at the same time.
- The machinery does not transfer in either direction: the clause 4.3 scope statement, the clause 6.1.3(d) Statement of Applicability, the clause 9.1 monitoring definition, the clause 9.2 internal audit programme and the clause 9.3 management review have no SOC 2 analogue — and the DC 200 system description, management’s assertion, complementary user entity controls, subservice-organization treatment and the evidence-population discipline behind Type 2 testing have no ISO equivalent.
- Maintenance differs in shape, not only in size. SOC 2 means a fresh examination of a fresh period every year. ISO 27001 means a three-year certificate with surveillance audits — but internal audit and management review recur annually regardless.
The question behind the question
Teams arrive asking which framework is better, or more rigorous, or more respected. None of those questions survives contact with a procurement portal. Three others decide it.
Which deal is blocked?
Not which market you would like to serve — which specific opportunity has a security review or a tender requirement standing between you and signature. If nothing is blocked, you are making a strategic choice rather than an urgent one, and the calculus changes.
When does it close?
A SOC 2 Type 1 can be produced within weeks of controls being in place, because it reports on design as of a single date. ISO 27001 cannot be accelerated the same way: Stage 2 requires evidence the management system has operated, including a completed internal audit and a held management review.
What does the buyer’s policy actually name?
Send exactly two questions: “Which clause of your third-party risk policy names the requirement?” and “Does that policy have an alternative-assurance provision, and who approves exceptions to it?” A named clause with no alternative-assurance provision means build the artefact it names and stop deliberating. A named clause with a provision means the sequencing is negotiable and the exception approver is the person to reach. No clause at all usually means the reviewer is working from a template — in which case the requirement is whatever satisfies them, and a certificate plus a mapped questionnaire often does.
Be precise about what each produces, because the vocabulary confusion drives a surprising amount of bad sequencing. A SOC 2 engagement produces a report, not a certificate — signed by a licensed CPA firm, covering either a point in time (Type 1) or a stated period (Type 2). ISO 27001 produces a certificate with a number, a scope statement and an expiry date, issued by a body that is itself accredited. That structural difference is why a portal with a “certificate number” field cannot absorb a report, and why a US vendor-risk analyst reading a one-page certificate asks what was actually tested.
The examination itself runs under AT-C sections 105 and 205 — AT-C 205 as revised by SSAE 21, and amended by SSAE 23, whose quality-management requirements are effective for engagements beginning on or after 15 December 2025. That is not trivia for a sequencing page: the same standard governs when a report may be dated and against which criteria the controls are evaluated, which is what makes the abutting-periods manoeuvre later in this page work. Controls are evaluated against the 2017 trust services criteria, with the revised points of focus published in 2022.
What each one signals, and to whom
Observed market practice across enterprise vendor-risk reviews and tender documentation, not a rule set by either standards body. Buyers vary, and the fastest way to resolve any row is to ask the buyer to quote their own policy.
US enterprise & mid-market SaaS procurement
A SOC 2 Type 2 report — Security at minimum, plus Availability or Confidentiality where the buyer depends on your uptime or hands you their data.
An ISO 27001 certificate is accepted as supporting evidence and almost never as the answer. What you get instead is the long security questionnaire the report would have short-circuited.
US regulated buyers — healthcare, financial services, federal supply chain
SOC 2 plus the sector programme: a signed BAA and HIPAA safeguards, GLBA obligations, or a FedRAMP authorisation, depending on the buyer.
Neither standard substitutes for the sector requirement. This is the expensive version of the mistake — two quarters spent on the wrong artefact while the real blocker was a contract term.
UK & EU enterprise and public sector
ISO/IEC 27001 certification from an accredited body, frequently named by number, with form fields for the certificate number, scope statement and expiry date.
A SOC 2 report is respected by technical reviewers and invisible to a portal with no field for it. Some frameworks permit “equivalent assurance”. Few define it, and the evaluator rarely has authority to decide.
Gulf — UAE & Saudi Arabia
ISO 27001 as the baseline, usually alongside a national or sector framework such as ADHICS in Abu Dhabi healthcare or the Saudi financial-sector cyber requirements.
SOC 2 registers with multinationals in the region and carries little weight in a government evaluation matrix. Certify first, then treat the local framework as an overlay on the same controls.
India — domestic enterprise, PSU and government tenders
ISO 27001, named in the RFP, with sector regulators layering their own frameworks on top in banking, capital markets and insurance.
SOC 2 carries weight with Indian companies selling to US buyers and close to none inside a domestic tender matrix, where a certificate number is a scored line item.
Keyed to buyer geography and deal urgency
Find the row that matches. Where two apply, the one with a fixed external date wins.
A US enterprise deal is in security review right now
SOC 2 — Type 1 immediately, Type 2 period starting the same week
A Type 1 is the fastest credible artefact once controls exist, because it reports on design as of a single date and needs no observation period. ISO 27001 cannot meet this timeline at any price: Stage 2 requires an internal audit and a management review to have actually happened.
US pipeline building, nothing formally blocked yet
SOC 2 — skip the Type 1, go straight to a three-month first Type 2
You avoid a second audit fee and land a real operating-effectiveness report roughly when the pipeline matures. Start the next period the day the first one ends so the reports abut.
A UK or EU tender names ISO/IEC 27001 with a submission date
ISO 27001 — but read the tender wording before anything else
Check whether a certificate is required at submission or a signed contract with a certification body is accepted. That one sentence decides whether this cycle is winnable. If it is not, bid the next one and start now.
European enterprise buyers, privacy-led due diligence, no tender
ISO 27001, with the privacy question answered separately
The certificate satisfies the security line. If the real concern is personal data, the answer is a privacy information management system or a documented GDPR position — not a wider SOC 2 scope. Adding the Privacy category is a poor proxy for a GDPR answer.
Gulf public-sector or regulated buyer
ISO 27001, then the local framework as an overlay
National and sector frameworks are control catalogues that map onto an ISMS you already run. Build the management system first and the overlay becomes a mapping exercise rather than a second programme.
Split pipeline — mostly US, with one large EU tender
Whichever one has the immovable date
Deadlines beat volume. US enterprise reviews accept a credible date for a report in progress far more often than a procurement portal accepts a document it has no field for.
Nothing blocked — board, investor or insurer is driving
ISO 27001 if you sell globally or expect tenders, or SOC 2 if your ICP is US SaaS buyers
This is the only case where the frameworks themselves get a vote, and the only case where running both together is genuinely economic — you can design one control set against both instead of retrofitting the second.
What genuinely transfers
The overlap is real and large, and it lives entirely in the control layer. Mappings of this kind are planning aids: no crosswalk relieves either auditor of testing the control in front of them, and no certification body accepts a SOC 2 report as evidence of conformity to a clause.
Risk assessment
Clauses 6.1.2, 6.1.3 — defined process, criteria, risk owners, treatment plan
The CC3 risk-assessment series
The register and the analysis transfer. What does not is ISO’s demand that the process itself be defined and repeatable against stated criteria, and that its output drive the Statement of Applicability.
Access control
A.5.15 access control, A.5.16 identity management, A.5.17 authentication information, A.5.18 access rights, A.8.2 privileged access, A.8.3 information access restriction
CC6.1, CC6.2, CC6.3
The same controls satisfy both. The difference is testing depth: a Type 2 needs the complete population of joiners, movers and leavers across the period, reconciled to a source system, and samples from it.
Change management
A.8.32 change management, A.8.31 separation of environments, A.8.25 secure development life cycle
CC8.1
Almost nothing new to build. What catches ISO-certified teams is that the SOC 2 population is every production change in the period — emergency and infrastructure changes included — exported so the auditor can tie the count to the tool.
Vendor and supplier management
A.5.19 to A.5.22 — supplier relationships, agreements, ICT supply chain, monitoring and review
CC9.2
The vendor register, risk tiering and annual reviews carry across intact. SOC 2 then adds what ISO has no equivalent for: a carve-out or inclusive decision for every subservice organization, and the complementary user entity controls your own customers must operate.
Incident response
A.5.24 to A.5.28 — preparation, assessment and decision, response, learning, evidence collection
CC7.3, CC7.4, CC7.5
The process, severity model and post-incident review transfer directly. The reporting posture does not: a Type 2 asks for the population of incidents and will test the ones you would rather not discuss.
Logging and monitoring
A.8.15 logging, A.8.16 monitoring activities
CC7.1, CC7.2
Same tooling, same configuration. The new work is proving triage happened — alert volumes with dispositions across the period, not a dashboard screenshot taken during fieldwork.
Availability and recovery
A.5.29 security during disruption, A.5.30 ICT readiness for continuity, A.8.13 backup, A.8.14 redundancy
A1.1, A1.2, A1.3 — only if Availability is in scope
Worth nothing in a Security-only SOC 2. Where Availability is in scope, the restore test behind A1.3 must have been performed inside the period, not merely scheduled.
Read down the right-hand column and the pattern emerges: the controls are the same, the proof standard is not. ISO 27001 asks whether a control exists, operates and is being improved, sampling lightly across a very wide surface — the applicable Annex A controls plus every clause from 4 to 10, across a three-year cycle. A Type 2 asks whether a narrower set of controls operated on every occasion it should have, over a stated period, and samples from complete populations to find out. That single difference is most of the cost of going from ISO to SOC 2. Catalogues: Annex A controls and the trust services criteria.
What does not transfer in either direction
This is where budgets get missed. Each framework carries machinery the other has no concept of, and neither can be satisfied by pointing at the other deliverable.
ISO 27001 only
- Clause 4.3 — a written ISMS scope statement, printed on the certificate and read by buyers.
- Clause 6.1.3(d) — the Statement of Applicability: all 93 Annex A controls, with justification for each inclusion and exclusion.
- Clause 6.2 — measurable information security objectives, with plans to achieve them.
- Clauses 7.2 and 7.5 — competence records and controlled documented information.
- Clause 9.1 — defined monitoring and measurement: what is measured, by what method, when, by whom, and how the results are evaluated. There is no SOC 2 analogue at all, and it is among the most commonly raised nonconformities.
- Clause 9.2 — an internal audit programme covering the whole ISMS, performed independently of the area audited.
- Clause 9.3 — a management review with defined inputs and documented outputs, held by top management.
- Clause 10.2 — nonconformity and corrective action records, including root cause.
- Amendment 1:2024 — clause 4.1 now requires a determination of whether climate change is a relevant issue, and clause 4.2 carries a note that interested parties can have climate-related requirements. The standard says determine, not document. Certification bodies nonetheless look for the determination in writing at the next surveillance or recertification audit.
SOC 2 only
- The Section 3 system description, written by management against the DC section 200 description criteria and evaluated by the auditor as fairly presented.
- Management’s written assertion in Section 2 — a claim your own leadership signs.
- Complementary user entity controls: what your customers must operate for your objectives to be met.
- Subservice organizations: a carve-out or inclusive decision for each, plus complementary subservice organization controls.
- Category selection beyond Security — Availability, Confidentiality, Processing Integrity, Privacy — each adding criteria and evidence.
- The observation period, and the evidence-population discipline that supports operating-effectiveness testing across it.
- The opinion itself, and exceptions written into Section 4 for every reader to see.
- The restricted-use paragraph naming the intended users of the report — a distribution limit an ISO certificate does not have and cannot express.
- Section 5 other information provided by management, which sits outside the scope of the auditor’s opinion and is labelled as such.
“An ISO 27001 certificate says a management system exists, is scoped, and is being maintained. A SOC 2 Type 2 report says these specific controls operated over these specific months, and here is what the auditor found when they tested them.”
Realistic effort and elapsed time
Ranges observed on TCSA engagements for organisations with a working control set and a named owner. They are not requirements of either standard, and a team without a dedicated owner should expect the upper end.
You have SOC 2. Adding ISO 27001.
The technical control set almost entirely, the policy library, the vendor register, access reviews, the incident process and logging. Controls are usually stronger than a first-time implementer’s because a CPA firm has already tested them.
The management-system layer: a clause 4.3 scope statement, a risk methodology with stated criteria, measurable objectives under 6.2, a Statement of Applicability covering all 93 Annex A controls with justification for each inclusion and exclusion, competence records, a full internal audit pass, a minuted management review, and a corrective-action process.
Little of this is difficult, but much of it is calendar-bound. The internal audit and management review must precede Stage 2 and cannot be back-dated. Teams that discover this in month four lose a quarter.
Decide early who performs the clause 9.2 internal audit. Nobody who built the ISMS can audit it — clause 9.2.2 requires auditors selected so the objectivity and impartiality of the audit process are ensured — so the person who wrote your Statement of Applicability cannot be the person who audits against it. At 40 to 60 people that independence usually has to be bought in or borrowed from another function, and booking it late is what pushes Stage 2 into the next quarter.
You have ISO 27001. Adding SOC 2.
Nearly all control implementation, the policy set, the risk register, supplier management, and the discipline of running an audit programme. Mapping Annex A to the trust services criteria is a desk exercise, not a build.
A system description written to the DC 200 description criteria, management’s written assertion, complementary user entity controls, a carve-out or inclusive decision for each subservice organization, category selection beyond Security, and — the real time sink — evidence populations complete enough to sample from.
The evidence model, not the controls. ISO surveillance rarely forces you to keep a defensible population of every change and every access grant for twelve months. A Type 2 does, retrospectively, and that gap cannot be filled after the period closes.
Check which edition your certificate names before you commit the quarter. The transition window for ISO/IEC 27001:2013 closed on 31 October 2025, so a 2013-edition certificate no longer counts and the re-audit to the 2022 edition is a certification-body engagement in its own right. A company running that transition and a first SOC 2 readiness in the same quarter has one compliance owner serving two audit calendars — name the conflict before it becomes a slipped date.
One cost does not shrink in either direction: the auditor’s. Certification-body audit duration is derived from the table in ISO/IEC 27006-1:2024, keyed to the effective number of people performing work within the ISMS scope — and since that edition, the count includes people who are not employees, such as in-scope contractors. It is not a negotiation. A CPA firm’s fee likewise reflects the criteria in scope and the testing required, not how tidy your evidence is. Good preparation buys shorter fieldwork and fewer exceptions, not a discount.
What each one costs, and what recurs
“It depends on scope and headcount” is true and useless. What you can know before any quote arrives is the shape: which cost driver scales with what, and which lines come back every year. No fee figures appear below, because both audit fees are set by firms other than us — but the shape is the same everywhere, and it is what makes one framework front-loaded and the other annual.
CPA firm examination fee
With the trust services categories in scope and the number of controls to be tested. Security alone is the floor. Each added category — Availability, Confidentiality, Processing Integrity, Privacy — brings its own criteria and its own populations. Type 2 costs more than Type 1 because operating effectiveness must be tested across a period, not assessed at a date.
In full, every year. Nothing renews and nothing carries forward: each period is a new examination with new fieldwork and a new opinion. There is no cheaper “surveillance” version of a SOC 2.
Year-one double engagement
A Type 1 followed by a Type 2 in the same year means two engagements and two fees. Going straight to a short first Type 2 avoids the second fee, at the cost of having no artefact at all until the period closes and the report is issued.
Once. From year two onward there is one examination a year, which is why the Type 1 decision is a cash-flow question as much as a sales one.
Evidence operation
With the number of controls tested and how often they run. This is internal cost, not fee: someone must keep populations complete and reconcilable for every month of the period, because a gap cannot be reconstructed after the period closes.
Continuously. It is the only line here that cannot be deferred to the quarter before the audit.
Certification body audit duration
From the audit-time table in ISO/IEC 27006-1:2024, keyed to the effective number of personnel performing work within the ISMS scope — a count that since that edition includes people who are not employees, such as in-scope contractors. The table is banded, so duration steps up in increments and rises far more slowly than headcount. The body may adjust within permitted limits for factors such as a single site or a highly automated environment. Ask for the audit-day derivation in writing before you sign — it is a calculation, not a quote.
Across a three-year cycle rather than annually. In practice certification bodies plan each surveillance visit at roughly a third of the initial certification audit time and recertification at roughly two thirds, so the audit spend is front-loaded into year one.
Stage 1 and Stage 2 as separate visits
Both fall in year one and both draw on the same audit-time allocation. Stage 1 is short and documentary, while Stage 2 carries most of the duration. A failed Stage 1 does not usually add fee, but it moves Stage 2 — which moves the certificate, which moves the deal.
Once per certification cycle. Recertification does not repeat a full Stage 1 for an ISMS that has been under surveillance.
ISMS governance cadence
With the breadth of the scope, not the headcount. Internal audit, management review, risk reassessment and corrective-action closure are the recurring cost, and the internal audit is the one line most organisations have to buy independence for.
Every year, including the two years when the only external visit is a short surveillance audit.
Read the two right-hand columns together and the planning consequence is obvious. ISO 27001 concentrates external audit spend in year one and then charges you two lighter years. SOC 2 charges roughly the same amount every year forever, and charges it again if you add a category. A three-year budget built on year-one figures will be right for ISO and wrong for SOC 2. TCSA’s SOC 2 fee is fixed and quoted after scoping, from $2,500 for a Type 1 and $3,000–$10,000 for a Type 2, all-in, including the independent CPA attestation. For ISO 27001, the certification body’s audit fee is separate and billed by that body directly.
One is public. The other is not.
This is a sequencing input, not a footnote, and it is one of the few a team cannot guess. The two deliverables are not merely different documents — they have different permitted audiences, which changes what each one does for the business after you have paid for it.
The ISO 27001 certificate
- Carries a certificate number, the certified scope statement, the issuing body and accreditation mark, and an expiry date.
- Can be published on your website, put in a pitch deck, and pasted into the certificate-number field of a tender portal.
- Can be verified by the buyer without involving you, on the certification body’s public register and the accreditation body’s directory.
- Says nothing about what was tested or what the auditor found — which is why a technical reviewer reads it in ten seconds and then sends the questionnaire.
The SOC 2 report
- Carries a paragraph restricting use to specified parties — management, user entities during the period, and their auditors and other parties with sufficient knowledge of the system and the criteria.
- The restriction exists because the criteria and the description are meaningful only to a reader who understands the system: an AT-C 205 examination reports to intended users, not to the public.
- Cannot be published. It goes out under an NDA, usually through a gated trust centre with a request-and-approve step, and is tracked so you know who holds which version.
- Does its work per deal, in depth — which is precisely why it displaces the long security questionnaire the certificate does not.
Draw the consequence out, because it changes the plan. An ISO certificate does marketing work continuously and unattended: it sits on the site, clears the portal field and gets verified by people you never speak to. A SOC 2 report does deal work, per deal, and only if you build the distribution machinery around it — an NDA template someone can sign the same day, a gate with an owner, a bridge letter for the months between the period end and the next report, and a record of who received what. Teams that budget for the examination and not for the distribution process discover in the first week that the report is sitting in a drive folder while sales asks who is allowed to send it. If you are weighing which artefact your go-to-market actually needs, that asymmetry belongs in the decision alongside the audit fee.
When running them together is actually cheaper
Parallel is genuinely cheaper in one circumstance: nothing is blocked, you know both are coming, and you have not built the control set yet. The saving is not vague goodwill — it is a specific list of artefacts that serve both audits if you build each one to the stricter of the two standards the first time. Calendar overlap is the second saving: the months in which your ISMS must be seen to operate before Stage 2 can be the same months as your SOC 2 observation period. Neither saving touches the two audit fees, because the certification body and the CPA firm are separate organisations that must both remain independent. This is the build list.
Risk assessment and treatment plan
Clauses 6.1.2 and 6.1.3 — and the output that drives the Statement of Applicability
The CC3 risk-assessment series
ISO is stricter here. Add stated risk criteria, a named owner per risk, and a documented method, because SOC 2 will accept a register that ISO will raise a nonconformity against.
Policy library
Clause 5.2 policy, clause 7.5 controlled documented information, and the policy-related Annex A controls
The CC1 and CC5 control-environment criteria
ISO is stricter on control of the documents themselves — version, approval, review date, distribution. Add that layer once and both auditors are satisfied by the same library.
Asset inventory
A.5.9 inventory of information and other associated assets, A.5.10 acceptable use
CC6.1 and the system description boundary
SOC 2 is stricter in a way ISO is not: the inventory must agree with the Section 3 system description, and an asset present in reality but absent from the description is a description problem, not an inventory problem.
Vendor register
A.5.19 to A.5.22 — supplier relationships, agreements, ICT supply chain, monitoring
CC9.2
SOC 2 adds work ISO has no equivalent for: a carve-out or inclusive decision for every subservice organization, and the complementary subservice organization controls that go with it. Build the register with that column from the start.
Access-review cadence
A.5.18 access rights, A.8.2 privileged access rights
CC6.1, CC6.2, CC6.3
SOC 2 is materially stricter. The review must have happened inside the period, on the stated cadence, with a dated sign-off and evidence that every removal it identified was actioned. Miss one quarter and there is no way to make it up later.
Incident log
A.5.24 to A.5.28 — preparation through evidence collection
CC7.3, CC7.4, CC7.5
SOC 2 is stricter on completeness: the population is every incident at every severity, and the auditor will reconcile it against your alerting. Log the small ones from day one — a log that starts three months into the period is worse than no log.
Penetration test
A.8.8 management of technical vulnerabilities, A.8.29 security testing in development and acceptance
CC4.1 and CC7.1
Neither standard mandates an annual external test by name, but both auditors and every buyer expect one. Scope it to the environment named in the ISMS scope statement and the system description so a single test serves both, and keep the remediation evidence — that is what gets tested, not the report.
Evidence pipeline
Clause 9.1 monitoring and measurement, clause 9.2 internal audit inputs
The whole of Type 2 operating-effectiveness testing
SOC 2 by a wide margin, and this is the one to build to the stricter standard first. Populations must be complete, reconcilable to a source system, and retained past period end. An ISMS can be evidenced from what exists today. A Type 2 cannot.
- A deal is blocked now. Two parallel tracks reach the first usable artefact later than one focused track — and the artefact is what unblocks the deal.
- Fewer than roughly fifteen people and no dedicated compliance owner. The ISMS cadence alone — internal audit, management review, corrective actions — is a recurring load on someone senior.
- Controls are immature. Running both means failing an internal audit and generating exceptions in an observation period at the same time, with no slack to fix either.
- The budget cannot carry two audit fees in one financial year. Sequencing spreads them across two, but parallel does not.
One company, eleven months
An illustrative sequence, not a client account: a 45-person B2B data-platform company selling into US enterprise, with one UK public-sector opportunity on the horizon and a single compliance owner.
- 3 Sep 2026
The blocker appears
A US enterprise vendor-risk team requests a SOC 2 Type 2. The contract is worth more than the UK opportunity and has a 30 October decision date. Sequence resolved in one meeting.
45 effective personnel, including 4 in-scope contractors — the same count both auditors will work from.
- Sep – Oct 2026
Readiness
Scope and system boundary defined, Security plus Confidentiality selected, controls brought to a testable state, evidence capture switched on first so populations accumulate from day one.
58 controls in scope: 22 system-enforced and continuous, 21 event-driven, 9 monthly, 4 quarterly, 2 annual. The frequency split is what sets every sample size six months later.
- 31 Oct 2026
Type 1 “as of” date
The CPA firm examines control design as of this date. Report issued 20 November. Enough for the buyer to close on a design opinion plus a committed period.
Design of all 58 controls examined as of a single date. No populations, no sampling, no operating-effectiveness testing — which is exactly why a Type 1 can be produced in weeks.
- 1 Nov 2026 – 30 Apr 2027
Type 2 observation period
Six months, beginning the day after the Type 1 date so no month is uncovered. Availability was not selected, so the restore test run on 19 February served ISO A.5.30 and A.8.13 and never entered a SOC 2 population.
Populations handed over at period close: 412 production changes (9 of them emergency), 11 joiners, 7 leavers including 2 contractors, 2 completed quarterly access reviews (15 December and 16 March), 6 security incidents across all severities, 1 external penetration test.
- Jan – Mar 2027
The ISMS wrapper starts
Scope statement, risk methodology, objectives, and a Statement of Applicability across all 93 Annex A controls. The controls already run — this is governance, not implementation.
79 of the 93 Annex A controls applicable, 14 excluded with a written justification for each. 26 risks in the register, every one with a named owner. 4 measurable objectives set under clause 6.2.
- 5 – 6 Apr 2027
Internal audit
A full pass over the ISMS by someone independent of the areas audited — bought in, because everyone internal had helped build it. Two minor nonconformities raised, with corrective actions and owners.
2 days on site. 2 minor nonconformities, 3 opportunities for improvement, 0 majors. Both nonconformities closed with a recorded root cause and an effectiveness check before Stage 2.
- 23 Apr 2027
Management review
Held by top management with the defined inputs and minuted decisions. The item most often discovered too late.
Every clause 9.3 input on the agenda, including the two internal-audit nonconformities, performance against the 4 objectives, the status of the risk treatment plan, and feedback from interested parties.
- 18 – 19 May 2027
Stage 1
Documentation and readiness reviewed: scope statement, Statement of Applicability, risk assessment and treatment plan, and confirmation that internal audit and management review were complete.
1 documentation finding — an SoA justification that named a customer requirement rather than a risk. Cleared in 9 days.
- 11 Jun 2027
Type 2 report issued
Issued while the certification audit was still running, because the two calendars are independent. One exception in Section 4, under an unmodified opinion.
The exception: 1 deviation in a sample of 40 drawn from the population of 412 changes — an emergency fix deployed on 22 December and approved retrospectively the next morning. Compensating control: next-day review of every emergency deployment, evidenced in the ticket. Remediated with a pre-deployment break-glass approval step from 15 January.
- 22 – 24 Jun 2027
Stage 2
Implementation and effectiveness audited across the clauses and the applicable Annex A controls. Duration derived from the ISO/IEC 27006-1:2024 audit-time table on 45 effective personnel, quoted in writing before the contract was signed — not chosen and not negotiated.
1 minor nonconformity: clause 9.1 monitoring defined for three of the four objectives but not the fourth. Corrective action accepted with a closure date.
- 23 Jul 2027
Certification decision
Certificate issued covering a three-year cycle. First surveillance audit due within twelve months of this decision, surveillance at least yearly thereafter, recertification before expiry in 2030.
The total: two audit fees, one calendar, one evidence pipeline. Eleven months from the blocker to holding both artefacts.
Three things are worth extracting. The ISO work started in month five and still finished inside the year, because the controls were already operating and had been tested by someone else — the new work was governance, which people who know the environment can produce quickly. The binding constraint was never effort: it was the internal audit and the management review, which must happen, be minuted, and precede Stage 2. And the numbers column is the part teams underestimate — 412 changes and 6 incidents had to exist as complete, exportable populations on 30 April, which meant deciding how to capture them on 1 November, before there was any audit to prepare for.
What the CPA firm actually requests
This is what ISO-certified teams underestimate, and the single largest reason a first SOC 2 slips. A service auditor does not ask to see your access-control process. They ask you to define a population, satisfy themselves it is complete, and then select from it. Sample sizes come from the service auditor’s judgement based on control frequency, risk and expected deviations — the AICPA publishes no fixed numbers — but the ranges below are what teams commonly meet.
Access provisioning
Every user granted access to in-scope systems during the period, from an HR joiner list reconciled to the identity provider — not a list assembled by hand.
25–40 where the population is large, all of it where it is small
A ticket showing approval by the correct approver dated before the grant, alongside the system record of the grant date. The two dates are the test.
A screenshot of today’s user list. Approvals dated after provisioning. A spreadsheet with no source system behind it. Contractors and service accounts quietly missing from the population.
Access removal
Every leaver in the period from the HR system, including contractors and role changes that should have removed entitlements.
25–40, or the full population where smaller
Termination date plus deactivation timestamps in each in-scope system, including those outside single sign-on.
“It is all behind SSO, so it is automatic” with no de-provisioning record. A leaver list that will not reconcile to payroll. Systems with local accounts left out of the description but present in reality.
User access reviews
The reviews that occurred in the period — four if the control says quarterly.
Usually all of them
The review export, the reviewer’s dated sign-off, and evidence that every removal the review identified was actioned, with the removal timestamp.
A review completed after period end that claims to cover the period. A review with no findings and no artefact showing anyone examined anything. Findings raised and never closed.
Change management
All production changes in the period, exported from the pipeline or repository with a count the auditor can tie back to the tool — emergency and infrastructure changes included.
25–40 selections across the period
The change record showing review and approval by someone other than the author before merge, test evidence, and the deployment record.
An export pre-filtered to changes that already have approvals. Self-approved merges with no compensating detective control. A separate emergency process nobody disclosed until the auditor found the deployments.
Incident response
All security incidents in the period, at every severity — not the ones with a tidy narrative.
Usually the full population
The incident record with detection, escalation and containment timestamps, decisions taken, notifications where applicable, and a post-incident review.
“No incidents this period” where the alerting evidence shows triaged security events. A post-incident review written the day the auditor asked for it.
Backup and recovery
Backup jobs across the period, and every restore test performed.
A few backup cycles and all restore tests
A restore test record with date, systems in scope, who performed it, the result and any follow-up actions.
A backup-success dashboard with no restore evidence. A test scheduled inside the period but performed after it closed. A test of a system outside the described boundary.
Selection scales with how often the control runs: an annual control has a population of one and is tested once, a quarterly control gives up two of its four instances, a monthly control two to four, a weekly control five to nine, and a daily or event-driven control somewhere between twenty-five and forty. Those ranges, and what happens to them when a deviation is found, are set out in full in SOC 2 sampling and sample sizes. Completeness matters far more than the number. An auditor who cannot tie your export to a system-generated source will expand testing or record a scope limitation, and both cost more than the export would have.
What the certification body actually requests
Same four questions, different auditor. Stage 1 is a documentation and readiness review: scope statement, Statement of Applicability, risk assessment and treatment plan, the policy set, and confirmation that internal audit and management review are planned or performed — both must be complete before Stage 2 proceeds. Stage 2 tests implementation and effectiveness across the clauses and applicable Annex A controls, sampling lightly but very broadly. Findings are graded by the certification body — in practice majors close before a certificate is issued, minors carry a corrective-action plan verified at the next visit.
Statement of Applicability
The current SoA covering all 93 Annex A controls, with the applicability decision, the justification, the implementation status and the link back to the risk treatment plan for each one.
Read in full at Stage 1, then tested against reality on a sampled basis at Stage 2
A justification per control that names why it applies — a risk, a legal obligation, a contractual commitment — and an exclusion justification that says why the risk does not exist here, not merely that the control was not implemented.
All 93 controls marked applicable with the justification column left empty, which tells the auditor no determination was made. Exclusions justified as “not required by our customers”. An SoA whose control list no longer matches the risk treatment plan after a scope change.
Risk assessment and treatment
The documented risk methodology, the risk register produced by it, the treatment plan, and the records of risk acceptance by the people entitled to accept.
The method reviewed in full, and individual risks traced from register to treatment to SoA
Stated criteria for accepting risk and for performing assessments, a named risk owner per risk, consistent and repeatable results, and treatment decisions that lead somewhere — a control, a date, an owner.
A register with no named risk owners and no stated acceptance criteria, so no one can say why a risk was closed. Scores assigned with no method behind them. A treatment plan with no completion dates. A register last updated before the last significant change to the environment.
Internal audit programme
The audit programme covering the whole ISMS, the plans and reports for audits performed in the cycle, auditor competence records, and the findings raised.
The programme in full, and individual audit reports and their findings traced to closure
A programme that reaches every clause and every applicable control across the cycle, auditors selected so objectivity and impartiality are ensured, reports that state what was examined and against what, and findings tracked to closure.
An internal audit performed by the ISMS manager over their own ISMS, which is an independence nonconformity under clause 9.2 regardless of how good the report is. An audit that examined documents only and never tested whether the control operated. A programme that covers the same easy areas every year.
Management review
Minutes and supporting packs for the reviews held, plus the decisions and actions they produced.
Usually all reviews held in the cycle
Minutes showing top management present, every required input considered, and outputs recorded as decisions with owners — including decisions about continual improvement and any change needed to the ISMS.
Minutes missing the required inputs: internal and external audit results, nonconformity and corrective-action status, performance against the information security objectives, feedback from interested parties, the status of the risk treatment plan and opportunities for improvement. A review attended only by the security team is a second finding on the same document.
Nonconformity and corrective action
Every nonconformity raised in the cycle — internal audit, external audit, incidents, and self-identified.
Usually the full population, with recent closures examined in detail
The record of what happened, the correction taken, an analysis of the cause, the action taken to stop recurrence, and evidence that the action was reviewed for effectiveness afterwards.
Corrective actions closed with a fix but no recorded root cause, so the same finding returns at the next surveillance visit. “Retrained the individual” as the action for a systemic control failure. A closure date with nothing showing anyone checked the action worked.
Competence
The people performing work under the ISMS that affects information security performance, and the basis on which each is competent.
Sampled across roles, weighted to ISMS-critical and privileged roles
A determination of the competence each role needs, plus education, training or experience records against it, and evidence that action taken to acquire competence was evaluated for effect.
Competence claimed by job title with no training or evaluation record behind it. An awareness deck circulated with no record of who read it. A named internal auditor with no auditor training and no explanation of why they are competent to audit.
The CPA firm asks for populations and draws samples from them, while the certification body asks for the management system and tests whether it is real. An ISO auditor may look at three access requests and be satisfied the control works, while a service auditor asks for every access request in the period and selects from it. Neither is more rigorous in the abstract — they test different assertions, and the second demands records the first never forced you to keep.
Which is why the preparation cost runs in opposite directions. Coming from ISO, the new work is the evidence pipeline and it must exist before the period starts. Coming from SOC 2, the new work sits in the second table — and almost every rejection column there describes a document that could have been written correctly the first time.
What each one costs you every year after
SOC 2
Nothing renews, because nothing expires. What recurs is the examination: a new observation period, a new evidence collection across it, fresh fieldwork and a new opinion. Evidence must be captured continuously, since a gap in a population cannot be reconstructed once the period closes.
Between reports you will field bridge-letter requests, and a report much past twelve months from its period end is generally treated as stale.
ISO 27001
The certificate is issued for a three-year cycle under IAF accreditation practice. The first surveillance audit falls due within twelve months of the certification decision, surveillance follows at least once each calendar year, and recertification must complete before expiry. Surveillance visits are shorter than Stage 2 and cover a sampled subset plus the mandatory clauses.
The audit calendar is lighter, but the internal calendar is not. Internal audit, management review, risk reassessment and corrective-action closure recur annually whether or not an auditor visits, and an ISMS that wakes up only before surveillance produces nonconformities.
Teams holding both converge on one quarterly cadence — access reviews, risk review, vendor review, management review inputs — feeding both machines from a single set of records.
Where this gets contested
The clean cases are decided by the matrix above. These generate the real questions.
The certificate scope does not cover the product
A certificate reading “provision of corporate IT services to internal users” does not cover the SaaS platform your customer is buying, and buyers read the scope line — several tender portals require it pasted verbatim. The SOC 2 equivalent is a system description whose boundary excludes the environment the customer actually uses.
The certification body is not accredited
A certificate from a body outside the IAF multilateral recognition arrangement is worth whatever the buyer decides, which is often nothing. Check the accreditation mark and the entry on the body’s public register. The SOC 2 parallel is confirming the opinion is signed by a CPA firm licensed in a US jurisdiction and enrolled in an AICPA-approved peer review programme — firm licensure, not an individual’s credential — because anyone can produce a PDF with a logo on it.
Your certificate is against the 2013 edition
The edition is printed on the certificate face, next to the scope statement and the expiry date, so a buyer sees it without asking. The transition window for ISO/IEC 27001:2013 closed on 31 October 2025: a certificate still naming the 2013 edition no longer counts, whatever date sits in its expiry field. The path back is a transition audit against the 2022 edition — commonly run at a surveillance or recertification visit, or as a standalone visit where the cycle does not line up — which needs the Annex A structure remapped, the Statement of Applicability rewritten to the 93 controls, and the climate-change determination added. Book it before you start a SOC 2, not alongside one.
Group certificate, subsidiary contract
The certified organisation may be the parent while the entity signing the customer contract sits outside the certificate scope. Vendor-risk teams increasingly check the legal-entity name against the master services agreement. The same applies to a SOC 2 system description, which names the service organization it describes.
Expiry lands mid-contract
A certificate is issued for a three-year cycle under IAF accreditation practice, with the first surveillance audit due within twelve months of the certification decision and surveillance at least once each calendar year thereafter. Surveillance is not a re-issue, and recertification must complete before expiry. Buyers ask what happens at expiry. The answer is a booked date, not an assurance.
Both are demanded, with no relief on timing
The workable sequence is a Type 1 to unblock the commercial conversation, a Type 2 period running from that date, and the ISMS layer built in parallel so Stage 2 lands inside the same year. What does not work is two full readiness programmes from a standing start with one compliance owner.
Independence cuts both ways
The impartiality requirements in clause 5.2 of ISO/IEC 17021-1 bar a certification body — or any part of the same legal entity — from providing management-system consultancy and then certifying that same system, and bar it from certifying a management system for which it provided the internal audits within the preceding two years. On the CPA side the nonattest-services provisions of the AICPA Code of Professional Conduct bar the practitioner from performing management responsibilities or designing and implementing the controls it later examines. A single vendor offering to “get you certified” for both is describing something the rules do not permit. TCSA does readiness, control implementation, evidence preparation and audit coordination — the certificate comes from an accredited certification body and the opinion from an independent licensed CPA firm. TCSA never certifies, attests, audits or signs.
Neither one is the actual blocker
Sometimes the requirement behind “send us your SOC 2” is a business associate agreement, a PCI DSS attestation, a FedRAMP authorisation or a regulator-specific framework. Ask the buyer to point at the clause in their policy before you commit a quarter to the wrong artefact.
Two of those rows turn on the same question — who is allowed to sign the thing you are buying. On the ISO side it is accreditation, checkable on a public register. On the SOC 2 side it is firm licensure and peer review rather than an individual’s letters, which is the distinction behind the question teams outside the United States ask most often: can an Indian CA sign a SOC 2 report. The short answer is that the report must come from a CPA firm licensed in a US jurisdiction, whatever other qualifications sit around the engagement.
What the buyer’s security team will say
Whichever one you did first, you will meet a reviewer who wanted the other. Five pushbacks worth rehearsing.
“Our policy only accepts SOC 2 reports.”
Do not argue equivalence — the reviewer usually has no authority to grant it. Ask whether the policy has an alternative-assurance clause and who approves exceptions, then supply what the report would have: the certificate, the Statement of Applicability mapped to their questionnaire, the latest surveillance outcome, a current penetration test, and a dated commitment to an observation period. Most exceptions turn on the date, not the argument.
“Your ISO certificate does not mention the product we are buying.”
Usually a fair objection. Give them the scope statement as it stands, explain what sits inside and outside it, and commit to a date for the scope extension — normally at the next surveillance audit, which certification bodies can accommodate. Never paraphrase the scope to sound broader. The buyer is holding the certificate.
“Your SOC 2 covers only three months.”
Accurate, and the answer is the calendar rather than a defence. A short first period is a legitimate way to get a tested report into a sales cycle, and becomes a problem only when presented as though it were twelve months of coverage. Show the next period already running from the day the first one closed, and the date the report is expected.
“There are exceptions in Section 4 of your report.”
Exceptions appear under unmodified opinions routinely, and a twelve-month report with none at all invites its own questions. Under AT-C section 205 the practitioner modifies the opinion only where a deviation means the controls did not operate effectively to meet the criteria — an identified deviation reported in Section 4 with an unmodified opinion above it is the standard working as designed. Walk the reviewer through each: what the control is, what the deviation was, how many instances out of what population, what compensating control existed, and what changed afterwards. A named remediation with a date closes this, but silence does not.
“Why can your consultant not simply certify you?”
Because the rules that make the certificate and the report worth anything are exactly the rules that forbid it. The separation is the product. What a readiness partner does instead is help build the control set, prepare evidence, ready the internal audit programme, and manage the auditor relationship so fieldwork does not stall. TCSA never certifies, attests, audits or signs.
One pattern runs through all five: reviewers accept dates far more readily than arguments. “Our observation period runs to 30 April and the report is expected in June” moves a review forward, but “ISO 27001 is broadly equivalent” does not. If you are mid-programme, there is a right way to describe an audit in progress that keeps deals moving without overstating what you have.
Frequently Asked Questions
Should we do SOC 2 or ISO 27001 first?
Does an ISO 27001 certificate satisfy a US customer asking for SOC 2?
Does a SOC 2 report satisfy an ISO 27001 requirement in a tender?
How much of the work actually overlaps?
How long does the second framework take?
Is it cheaper to do both at the same time?
What is the ongoing maintenance for each one?
Can the same firm do the readiness work and the audit?
Can we publish our SOC 2 report on our website?
Can we publish the ISO 27001 certificate?
We are early stage with no customers asking yet. Should we do either?
Which one costs more?
Related Reading
SOC 2 vs ISO 27001
The decision guide for US-bound vs global-bound trust evidence.
Read moreISO 27001 Overview
The ISMS standard, and the baseline certificate global buyers ask for.
Read moreWhat Is SOC 2?
The AICPA attestation explained: five categories, Type 1 vs Type 2, report not certificate.
Read moreChoosing Your Trust Services Criteria
Security is mandatory. The other four are driven by commitments you actually made, and Privacy costs more than teams expect.
Read moreSOC 2 Knowledge Hub
Every SOC 2 guide: Type 1 vs Type 2, criteria, timelines and audit prep.
Read moreISO 27001 Knowledge Hub
All 93 Annex A controls, all clauses, every guide in the cluster.
Read more