← Back to blog

65–75% Control Overlap: Pick SOC 2 or ISO 27001 Based on Buyer Demand

September 27, 2026
65–75% Control Overlap: Pick SOC 2 or ISO 27001 Based on Buyer Demand

ISO 27001 is a formal certification of an information security management system, audited by an accredited certification body and valid for three years. SOC 2 is an attestation report written by a CPA firm about specific service controls, issued as a Type I snapshot or a Type II period review. The rule of thumb: get whichever your buyers actually ask for first. Because the two frameworks share a large portion of their controls, adding the second one later costs far less than starting from scratch.


TL;DR:

  • Most organizations will find it more cost-effective to pursue both ISO 27001 and SOC 2 by mapping controls and evidence rather than conducting two separate audits from scratch.
  • SOC 2 Type II reports are preferred by enterprise buyers due to their demonstration of operational controls over a review period of six to twelve months, unlike the one-time snapshot of a Type I.
  • ISO 27001 certification is especially valuable for public sector, EU, UK, and regulated industry clients, as its certificate can be publicly shared and is widely recognized.
  • The decision to pursue either framework first should be guided by customer location, explicit deal requirements, and internal resources more than perceived rigor or prestige.
  • External costs include audit fees, but internal effort—such as policy development and evidence collection—often exceeds these expenses and affects the overall timeline.

Solusec
Build Buyer-Ready Cybersecurity Confidence
Solusec provides expert-led penetration testing and cybersecurity certification services with clear, actionable findings for growing organisations.
Explore Solusec’s services

Table of Contents

What ISO 27001 requires and why organisations get certified

ISO/IEC 27001 is the international standard for an information security management system, or ISMS. Rather than certifying a single product or service, it certifies how an organisation identifies risk, decides which controls address that risk, and keeps improving the system over time. The standard is deliberately broad: it covers governance, risk assessment, supplier management, incident handling, and dozens of other operational areas, and it applies to the whole organisation rather than one department or platform.

At the centre of certification sits the Statement of Applicability, a document that maps each of the 93 Annex A controls to whether it applies, why, and how it is implemented. Auditors use the SOA as their roadmap during assessment, and it becomes the reference point for every future audit cycle. This prescriptive structure is part of what makes ISO 27001 attractive to buyers who want to see a management system, not just a list of technical safeguards.

What ISO 27001 requires and why organisations get certified — overview diagram

Certification itself runs in two stages. Stage 1 is a documentation review, checking that policies, the SOA and risk assessments exist and are coherent. Stage 2 tests whether those documented controls actually operate in practice, through interviews, evidence sampling and site or system checks. Only an accredited certification body can issue the certificate, which is why ISO/IEC 27006 matters: it sets the competence and impartiality requirements those bodies must meet, which is part of why a published ISO 27001 certificate carries weight with procurement teams who have never met the auditor.

Once issued, the certificate is valid for three years, with annual surveillance audits in years one and two and a full recertification audit in year three.

  • ISO 27001 is commonly requested by public sector buyers, EU and UK enterprises, and organisations in regulated sectors that expect a recognised management-system certificate.
  • The certificate itself is public and can be shared freely with prospects, unlike an attestation report.
  • Readiness and the two audit stages typically take several months for organisations with no prior management system in place.

What SOC 2 requires and how its reports work

SOC 2 is not a certification. It is an attestation report, written by a licensed CPA firm, that describes the controls a service organisation has in place and gives an opinion on whether they meet the relevant Trust Services Criteria: security, availability, processing integrity, confidentiality and privacy. Every SOC 2 report addresses Security at minimum, and the organisation chooses which of the remaining criteria apply to its service.

The practical decision most companies face is Type I versus Type II. A Type I report assesses whether controls are suitably designed at a single point in time. A Type II report goes further, testing whether those controls operated effectively across a review period, typically 6 to 12 months. Type II is the report most enterprise buyers actually want, because it demonstrates sustained operation rather than a one-day snapshot.

Unlike an ISO 27001 certificate, a SOC 2 report is not published openly. It is a confidential document, usually shared under NDA with prospects or customers who specifically request it during procurement or vendor risk review. That confidentiality limits how a company can use it in marketing, but buyers in security-conscious sectors tend to prefer the detail a Type II report provides over a public certificate's summary assurance.

  • SOC 2 is the de facto requirement in North American enterprise and SaaS procurement, particularly for vendors handling customer data.
  • Type I reports suit companies that need to show something quickly; Type II is what most serious enterprise deals eventually require.
  • Because Type II requires an observation period rather than a one-off audit, the overall timeline is often driven more by the length of that window than by the audit itself.

Key similarities and differences security teams must brief stakeholders on

The two frameworks solve a similar problem through different mechanisms, and the distinction matters when a salesperson tells a prospect "we're SOC 2 compliant" or "we're ISO certified" without understanding what each phrase actually promises.

  • Certification versus attestation: ISO 27001 results in a certificate issued by an accredited body; SOC 2 results in a CPA firm's written opinion, not a certificate.
  • Scope: ISO 27001 certifies an ISMS across the organisation (or a clearly defined boundary within it); SOC 2 is scoped to a specific service or system and its supporting controls.
  • Control structure: ISO 27001 uses a prescriptive set of 93 Annex A controls; SOC 2 is principle-based against the Trust Services Criteria, giving organisations more latitude in how they satisfy each one.
  • Overlap: estimates put the shared control ground at roughly 65 to 75%, covering areas like access control, change management, incident response and vendor risk.
  • Market recognition: SOC 2 dominates North American procurement checklists; ISO 27001 is the preferred standard in the UK, EU and much of APAC.
  • Evidence sharing: the ISO certificate can be published on a website or sent to any prospect without friction; a SOC 2 report is confidential and typically only shared under NDA.
  • Maintenance cadence: ISO 27001 runs on a three-year certificate with annual surveillance audits; SOC 2 has no expiry date as such, but buyers expect a fresh Type II report roughly every 12 months to stay current.

None of this means one framework beats the other on merit. Neither is inherently superior, and the right choice depends on customer requirements and business objectives rather than on which sounds more rigorous. A company selling almost exclusively to US SaaS buyers will get more mileage from a SOC 2 Type II report than from an ISO certificate nobody in that pipeline asks about, and the reverse is just as true for a vendor selling into UK public sector frameworks. The overlap is what makes the eventual "both" decision less painful than it sounds: once one framework's controls are documented and evidenced, mapping them into the second is largely an exercise in translation rather than rebuilding a security programme from scratch.

Decision criteria: practical questions to decide which to pursue first

Before commissioning either audit, work through where the pressure is actually coming from. Certifications exist to unlock deals and satisfy procurement, so the decision should follow the money rather than a preference for one framework's aesthetics.

  1. Map your current pipeline and existing revenue by buyer geography: North American enterprise and SaaS deals tend to demand SOC 2; UK, EU and APAC deals, particularly public sector or regulated industries, tend to demand ISO 27001.
  2. Check whether any live deals or renewal contracts explicitly name a framework in their security questionnaire or procurement specification. An explicit request from a real deal outweighs any general market assumption.
  3. Consider regulatory context beyond direct customer demand. Sector rules or frameworks like NIS2 in the EU can push certain organisations toward ISO 27001 regardless of individual buyer preference.
  4. Estimate which credential unlocks revenue fastest. If a six-figure deal is stuck on "do you have SOC 2", that answer should outrank a longer-term ambition to get ISO certified.
  5. Weigh internal resourcing and cost against urgency. A lean security team may only be able to run one audit programme properly at a time, so sequencing matters as much as choice.
  6. Brief sales and procurement early so they stop overpromising a framework the security team hasn't started, and so contract language matches what will actually be delivered and when.

Pro Tip: Ask your three most recent lost deals what security credential they required, if any. That answer is usually a better guide than any industry benchmark.

How to get both efficiently: mapping, sequencing and audit scheduling

Most organisations that sell across regions end up needing both frameworks eventually, and the efficient path is to treat the second one as a mapping exercise rather than a second project from scratch.

  • Map your Statement of Applicability or Annex A controls directly against the Trust Services Criteria; because the overlap sits around 65 to 75%, most policies, risk assessments and technical controls transfer with light editing rather than a rewrite.
  • Reuse the same evidence base wherever possible: access logs, change tickets, vendor risk assessments and incident records satisfy requirements in both frameworks and shouldn't be collected twice in parallel systems.
  • Sequence by demand: start with the framework your current or most immediate pipeline requires, then add the second within roughly one to two years if you sell into both markets.
  • Some organisations run a combined engagement, assessing an ISMS against SOC 2 criteria in a single project to avoid duplicating evidence-gathering work across two separate audit cycles.
  • Where the timing allows, align your SOC 2 Type II observation window with the run-up to an ISO surveillance audit, so evidence collected for one naturally supports the other.
  • Assign a single owner for the mapped control set rather than splitting ownership between two teams working from two different spreadsheets.

Cloud-hosted services add a layer worth planning for early: where data is stored and processed affects what evidence is available for review, particularly when infrastructure spans multiple providers or regions.

Timeline and cost ranges: budgeting and resourcing expectations

Budgeting for either framework means planning for both the audit fee and the internal effort that precedes it, which is usually the larger cost.

For SOC 2, a Type I audit can often be completed once controls are documented and operating, while a Type II report requires an observation period of 6 to 12 months before the auditor can test anything, so the calendar time is driven by that window rather than the audit itself. For ISO 27001, expect a readiness phase to build the ISMS and SOA, followed by the Stage 1 documentation review and the Stage 2 operational audit, then annual surveillance audits and a full recertification every three years.

  • Consultancy and auditor fees vary by organisation size and scope, and are best quoted directly against your specific control environment rather than estimated generically.
  • Internal resource time, not just external fees, is usually the larger hidden cost: someone has to write policies, gather evidence and coordinate interviews.
  • Organisations with existing maturity, prior Cyber Essentials certification, or a documented risk register typically move through readiness faster than those starting with no formal security programme.
  • Remediation windows between Stage 1 and Stage 2, or between a failed control test and report issuance, should be budgeted as calendar time, not treated as a rounding error.

Adding a second framework after completing the first typically costs far less than starting from scratch, because the marginal effort for the second credential often runs at only 20 to 35% of the first. That gap is the strongest argument for planning both from the outset, even when only one is needed immediately.

Practitioner perspective and common pitfalls

Practitioner perspective and common pitfalls — overview diagram

The most common mistake is optimising for the framework that looks more impressive rather than the one buyers actually request. Teams chase ISO 27001 because it sounds authoritative, or default to SOC 2 because competitors have it, without checking where their own pipeline's pressure actually sits. The second most common mistake is under-resourcing evidence collection: audits fail on missing documentation and inconsistent logs far more often than on genuinely absent controls.

The fix is straightforward. Map your controls once, reuse that evidence across both frameworks, and get procurement and sales involved before the audit starts rather than after a deal stalls. Where scope allows, a combined engagement against both frameworks avoids duplicating work that a sequential approach repeats twice. This pattern is common across SME and education clients certified against Cyber Essentials and allied schemes, where the gap between "we have controls" and "we can evidence them" decides most audit outcomes.

— Solusec Admin

How Solusec can help with ISO 27001 and SOC 2 readiness

Solusec

Whichever framework your buyers are asking for, the groundwork is the same: know your current control gaps, fix them, and be able to prove it to an auditor. Solusec's SOC Consulting & Support service helps teams map existing controls against Trust Services Criteria and prepare the evidence a Type I or Type II report demands, while our gap analysis for Cyber Essentials gives smaller organisations a fixed-fee starting point before committing to a larger ISMS build. For teams that need technical evidence behind their controls, our CREST-accredited penetration testing generates the findings auditors expect to see referenced in vulnerability management records. A typical engagement starts with a gap analysis, moves to a scoped remediation plan, and ends with fixed-fee certification support rather than open-ended consultancy hours. Get in touch through Solusec to scope your next audit cycle.

Sources

FAQ

Is SOC 2 legally required?

No. SOC 2 is not a legal requirement in any jurisdiction; it is a voluntary attestation that customers request during procurement or vendor risk reviews, particularly in North American enterprise and SaaS sales. Some contracts make it a commercial requirement even though no law mandates it.

Is SOC 2 hard to get?

A SOC 2 report is achievable for most organisations with reasonably mature security practices, but the difficulty usually lies in evidence collection rather than the controls themselves. A Type II report adds a further hurdle: the auditor needs a review period of 6 to 12 months of operating evidence before issuing an opinion, which extends the timeline regardless of how prepared the organisation is.

What is SOC 1 and SOC 2 and SOC 3?

SOC 1 reports focus on controls relevant to a client's financial reporting, while SOC 2 covers the Trust Services Criteria (security, availability, processing integrity, confidentiality and privacy) for a service organisation. SOC 3 is a public-facing summary of a SOC 2 report, shareable without the confidentiality restrictions that apply to the full report.

What is the standard that is equivalent to SOC 2?

There is no exact one-to-one equivalent, but ISO 27001 is the closest comparable framework, since both address information security controls and are commonly requested in place of, or alongside, each other depending on the buyer's market. The two differ in mechanism, certification versus attestation, but cover similar ground in access control, incident response and risk management.

This article was created with assistance of AI. We never use AI with your data unless given explicit permission.