Throughline.
    Insights
    Compliance Planning · Audit & Assurance

    SOC 2 for Enterprises: Timeline, Cost and What's Different at Scale

    SOC 2 for enterprises: typical USD costs, timelines and team hours, plus ISO 27001 reuse, multi-entity scope, vendors, procurement and customer deadlines.

    Paul Wenham
    2026-11-10

    A typical enterprise, with more than 1,000 staff, gets a SOC 2 Type 1 report in about 18 weeks and a first Type 2 in about 32 weeks. At the median, the audit costs about $18,000 for a Type 1 and $22,000 for a Type 2.

    Enterprises usually have most of the controls SOC 2 needs before they start. The extra time goes on governance, coordination and complexity. This guide covers what's different at enterprise scale; for how each stage works, see SOC 2 for startups. Figures come from our SOC 2 cost and timeline benchmarks.

    Which guide fits your company stage?

    Use the cost and timeline benchmarks for the cross-company comparison. This detailed guide explains the work behind the numbers.

    Compare stages: SOC 2 for startups, SOC 2 for mid-sized companies.

    All costs are indicative US-dollar market estimates, not Throughline quotes. For our own fixed annual fees, see Throughline SOC 2 pricing. These are practitioner planning medians with outliers removed, not a formal statistical survey. Type 2 medians assume an approximate three-month observation period; longer coverage changes the schedule.

    Type 2 periods typically run three to 12 months. Throughline recommends six to 12 months; three months may suit a specific accepted timing requirement when that is the maximum coverage available. Agree actual calendar dates and buyer acceptance with your auditor.

    How long does SOC 2 take for an enterprise?

    Figures are in weeks: the median, with the typical range in brackets.

    StageType 1Type 2
    Planning4 (3–14)4 (3–14)
    Readiness8 (3–24)10 (5–24)
    Observation periodNot applicable12 (12–24)
    Audit fieldwork4 (2–8)4 (2–10)
    Reporting2 (1–6)2 (1–6)
    End to end18 (9–52)32 (23–78)

    The ranges are far wider than for smaller companies. Planning alone can run to 14 weeks when procurement and approvals are involved. The Type 2 median uses a 3-month observation period for consistency across company sizes, but enterprises more often choose six months or more.

    How much does SOC 2 cost for an enterprise?

    The audit typically costs $11,000–$35,000 for a Type 1 (median $18,000) and $12,000–$50,000 for a Type 2 (median $22,000). It's priced to the finished report, not by stage; Big Four firms sit above these ranges.

    Related costs:

    CostMedianTypical range
    Compliance platform (annual)$60,000$40,000–$100,000
    Penetration test$40,000$20,000–$80,000
    Compliance consultant$90,000$50,000–$150,000
    Internal audit (outsourced)$20,000$10,000–$40,000
    Tool licensing upgrades$30,000$10,000–$100,000
    Availability or Confidentiality criteria (each)$1,000$0–$2,000
    Processing Integrity criteria$6,000$3,000–$12,000
    Privacy criteria$10,000$5,000–$20,000
    SOC 3 report$5,000$3,000–$10,000

    Many enterprises already pay for some of these, such as pen testing, core security tools or an internal audit function, so the new spend for SOC 2 is often lower than the full list suggests.

    How much internal team time does SOC 2 take for an enterprise?

    Roughly 150 to 2,460 hours across the journey, excluding normal operation of controls during an observation period.

    StageInternal hours
    Planning8–40
    Readiness80–2,000
    Audit fieldwork60–400
    Reporting2–20
    Total150–2,460

    Hours scale out because many parties are involved. Work is split across more people, and coordinating them makes it less efficient. But the timeline doesn't stretch in proportion: enterprise teams spend a larger share of their time on compliance, while at a startup the weeks drag because people wear many hats.

    Who runs SOC 2 at an enterprise?

    A formal GRC function usually leads it, but it's never a small group. Control owners sit across many teams, business units and sometimes locations, and approvals come from senior stakeholders who are busy with everything else in the business.

    That governance is a strength: it's why enterprises already have so much in place. It's also what slows SOC 2 down. Every decision passes through more people, and every stage has more availability to coordinate.

    How is SOC 2 different for an enterprise?

    The head start: most of it already exists

    Like a mid-sized company, an enterprise will already have most of what SOC 2 requires, even if it has never pursued a SOC 2 report. It may already hold an ISO 27001 certification, or have built controls in response to years of customer security questionnaires. That shortcuts how much needs implementing.

    The overhead: governance and coordination

    The flip side is overhead. More governance and more stakeholders naturally slow things down. Planning takes the biggest hit: procurement policies can mean RFPs, comparing several providers, and approvals from multiple busy stakeholders before anything starts.

    The complexity: more systems, more customers

    Enterprises have scaled to serve more enterprise customers, often with different support arrangements and system components for each. Scoping the audit means working carefully through which components belong in the report. Any implementation work tends to be more involved, because it has to fit a larger, more complex environment.

    If you already have ISO 27001, how much does it shortcut SOC 2?

    A lot: roughly 80% of the implementation work. The two overlap by about 90%. ISO 27001 is an information security management system, covering core security practices and how security is governed. SOC 2 is a little broader and more operational, including how the service supports customers and communicates with them.

    If you're ISO 27001 certified, you can be fairly confident you're already close to SOC 2 compliant. Most of the work is mapping your existing controls to the SOC 2 criteria and filling the operational gaps.

    The 80% implementation and 90% overlap figures are practitioner estimates, not a formal crosswalk or a guarantee. Scope, criteria, operating evidence and customer commitments determine the actual gaps.

    Can one audit cover both?

    Not really. The standards are written very differently and produce different outcomes: ISO 27001 a certification, SOC 2 an attestation report with 40 or more pages of detail. Forcing them into one audit process gets messy and serves neither goal well.

    What works is carrying the work over: much of the evidence from an ISO 27001 audit can be reused for SOC 2, or the other way round. Even with one audit team, it's usually still two audits.

    How is SOC 2 scope handled across multiple entities, regions or subsidiaries?

    Where entities operate very differently, separate reports can make sense. More often, one report covers them all:

    • The system description (Section 3 of the report) sets out the entities and operations in scope.
    • Shared controls with separate testing. Ideally, one control covers every region, with the auditor testing each region's version underneath it. A control might simply say that firewalls protect network traffic, while the auditor tests different firewalls in each region.
    • Separate controls where practice differs. Some controls genuinely vary. For example, background checks might apply to US employees while other regions use reference checks, so the report includes both controls. Different infrastructure with different configurations works the same way.

    The aim is a report that doesn't split everything out, keeping it readable, while testing reflects where regions actually differ in practice.

    When should a key vendor be included in your report rather than carved out?

    Usually only when the vendor has no SOC 2 report of its own and provides something nuanced or bespoke to you. The more tailored a vendor's service is to your environment, the stronger the case for including it.

    AWS is the classic carve-out. It's so mainstream that pulling it into every customer's report adds little; its own SOC 2 report is widely distributed and relied on by enterprises.

    A development shop that works only for you, or for you and a few others, is the opposite. If it has no SOC 2 report, leaving it out creates a real gap: your customers have no access to it and no assurance over what it does. Including it in your report closes that gap.

    What changes at each stage for an enterprise?

    • Planning. The longest and most variable stage at this size. Procurement, RFPs, comparing providers and sign-off from several stakeholders can stretch it from a few weeks to over three months.
    • Readiness. Mostly mapping what already exists, such as ISO 27001 controls and questionnaire-driven policies, to SOC 2. Gaps are fewer but harder to close, because changes touch more systems, teams and approvals.
    • Observation period. Enterprises usually choose six months or more for a first Type 2, since a 3-month report carries less weight with their own customers.
    • Audit fieldwork. More system components, larger samples and more control owners to schedule. The auditor needs to understand a complex environment to test it efficiently.
    • Reporting. More reviewers, and a more diverse customer base to satisfy. The report has to clearly describe a complex system, and what is and isn't covered, so it works for every customer relying on it.

    What's the fastest an enterprise can get SOC 2?

    Speed takes the same ingredients at any size: someone who knows compliance, SOC 2 as a top priority, the authority to act, and an auditor working at your pace. Enterprises usually have the expertise, but authority is spread across many people.

    Procurement, approvals and the number of parties involved set the floor. Even with everything aligned, the realistic fastest is about 9 weeks for a Type 1 and 23 weeks for a Type 2. When a customer needs assurance sooner, a Type 1 first can cover the gap.

    What if a customer needs a report before you can finish?

    When a renewal or a new deal needs a report soon but governance slows everything down, the options are:

    • A Type 1 first. Our usual recommendation for enterprises, given their long cycles. It gives the customer independent assurance while the Type 2 period runs.
    • A shorter Type 2 period. It can work, but a 3-month Type 2 lacks substance compared with six months or more.
    • More frequent reports. If you're on an annual Type 2 cycle and customers need assurance more regularly, you can issue reports twice a year or quarterly. Earlier evidence may be reused where relevant, but each report still needs testing supporting its own period.
    • A bridge letter. Useful as a formality, but it's a statement without proof behind it, much like answering a security questionnaire. It adds little real assurance.

    A refreshed report, whether Type 1, a shorter Type 2 or a more frequent cycle, carries far more substance than a bridge letter.

    What causes SOC 2 exceptions at an enterprise?

    The causes are the same at every size: missing documentation, informal processes, and gaps in access control and change control. At enterprise scale, they tend to surface where access and change processes differ across teams, systems or business units.

    What does year two look like for an enterprise?

    The audit fee usually holds steady. Audit firms invest more effort in year one expecting a renewal, and rarely reduce fees as their effort falls by about 20–30%. Your effort drops by about 40–50%. Planning falls close to zero, because providers and approvals are already in place. Readiness becomes a tidy-up and a stock-take of controls, and fieldwork and reporting take about 30% less effort. With hundreds of readiness hours in year one, the saving is substantial in absolute terms.

    What should an enterprise look for in a SOC 2 audit firm?

    At enterprise scale, the audit firm shapes the timeline as much as the internal team does. Look for a firm that:

    • understands complex environments, with many products, system components and support arrangements
    • works as a partner on scope, helping decide which components belong in the report and why
    • helps prepare a report that genuinely works for your customers, not a generic one
    • keeps experienced people on the engagement, so context isn't lost between stages

    For more on why the individual auditor matters, see choosing a SOC 2 auditor.

    Do you need an RFP to choose a SOC 2 audit firm?

    Usually not. Enterprise RFPs for audit firms tend to be overworked: pages of requirements, formal presentations and a long process, when every firm works to the same standards. Audit is a relationship, with the firm and with the individuals doing the work, and an RFP can over-formalize the decision and miss what matters most in practice.

    You still need to verify credentials and check that each firm meets your requirements. That can usually be done with three quotes and three meetings.

    The most useful question to ask is who the auditor will be. That person has the biggest bearing on your experience and on the audit's success. See also the questions to ask about an audit firm's credentials.

    How can Throughline help with your SOC 2 audit?

    Our SOC 2 audit services are calibrated to your stage, system scope, service commitments and compliance goals. Readiness is included free with every audit, and a Type 1 is included at no extra cost with every Type 2 engagement. Management owns control decisions and implementation.

    The audit fee is the unavoidable external cost of obtaining an independent report. Platforms, consultants and outsourced internal audits are optional; operating suitable controls may still require spending based on your risks and commitments. Throughline includes Availability and Confidentiality by default. The related-cost tables describe market arrangements, not Throughline add-on charges.

    Read all four guides: cost and timeline benchmarks, SOC 2 for startups, SOC 2 for mid-sized companies.

    Paul Wenham
    Written by
    Paul Wenham

    Former PwC manager, founder of AssuranceLab and former Sensiba partner and Chief Innovation Officer. Now founder of Throughline, focused on compliance and assurance for AI-native companies.

    More from Paul
    Compliance Planning · Audit & Assurance
    SOC 2 Cost and Timeline Benchmarks by Company Size

    Typical SOC 2 costs and timelines for startups, mid-sized companies and enterprises, by report type. Compare planning, readiness, observation, fieldwork and reporting, plus related costs in USD.

    Audit & Assurance
    How Australian Companies Should Choose a SOC 2 Audit Firm

    Australian companies need a SOC 2 report issued under the AICPA standards by a US-licensed CPA firm, delivered by a strong local team in Australian time zones. Here's how the provider options compare, and what to check.

    Compliance Planning · Audit & Assurance
    How Much Does SOC 2 Cost? The True All-In Cost, Category by Category

    A category-by-category SOC 2 budget in USD, covering audit fees, readiness, platforms, penetration testing, consultants, internal assessments and operational costs. Learn what is required, what is optional, and what a quote can leave out.

    Audit & Assurance
    SOC 2 Isn't Pass/Fail: What It's Really For

    SOC 2 is a risk report, not a certificate. Understand how enterprise customers use it, why having a report is only base camp, and how to turn your audit into a trust asset for growing revenue.

    Compliance Planning
    SOC 2 Readiness Assessments: Your Questions Answered

    What readiness should cover, when to involve your auditor, which gaps matter most, and how readiness, Type 1 and Type 2 can work as one continuous engagement. A practical guide to preparing for a report your customers can rely on.

    SOC 2
    What makes a SOC 2 report quality?

    Enterprise buyers use SOC 2 as an initial qualifier, then look deeper. A quality report is what carries you through that assessment and turns your compliance investment into real trust.

    SOC 2
    What makes a SOC 2 audit high quality

    Audit quality isn't service quality, and it isn't only professional standards. The real test is whether a reader of your report thinks: this tells me what I need to know.

    Audit & Assurance
    Getting Through Enterprise Security Reviews

    Enterprise security teams review you in the background and rarely give feedback. What they look at beyond SOC 2, what counts as a genuine pen test, and how a quality report does the heavy lifting.

    Agentic Compliance
    Agentic Compliance: AI-Native, Human-Led

    Compliance from first principles, the 95% problem, the compliance metadata AI needs, rethinking screenshots, spreadsheets and policies, and why audits should meet clients where they are.

    Last updated