Most companies spend weeks choosing a compliance platform and an afternoon choosing their SOC 2 auditor. It should be the other way around. The auditor decides how long the audit takes, what it costs, how much of your team’s time it eats, and whether the report you get at the end is one your customers’ security teams actually trust.
This guide covers who is allowed to issue a SOC 2 report, the four kinds of firms you will be choosing between, the questions to ask on the scoping call, the red flags, and what a good auditor will ask you for, so you can have it ready.
Who can issue a SOC 2 report
A SOC 2 report is an attestation report under the AICPA’s attestation standards. Only a licensed CPA firm can sign one. Readiness consultants, compliance platforms and security firms can help you prepare, and many do excellent work, but none of them can issue the opinion. If a vendor says it will “give you a SOC 2,” ask which CPA firm signs it.
Two checks take ten minutes and are worth doing before the first call:
- The license. Look the firm up on CPAverify, the national database of licensed CPAs and firms, or with the state board of accountancy where it is based.
- Peer review. CPA firms that perform attestation work go through peer review, usually every three years, where another firm examines a sample of their engagements. The AICPA public file shows enrollment, and for many firms the rating. Ask the firm for its most recent peer review report. A good firm will send it without hesitation.
The four kinds of firms
Every licensed firm issues the same kind of report. What changes is the price, how the audit runs, and how much the name on the cover means to the people who will read it.
The cost ranges above come from our SOC 2 pricing breakdown, which covers the full first-year budget. The audit fee is rarely the largest line. Your own team’s time usually is, and the auditor has a lot of influence over how much of it gets used.
Bundled audits aren’t automatically a problem, but the profession is watching them closely. In April 2026 the AICPA’s ethics staff warned that a SOC tool provider’s relationships and marketing can threaten an auditor’s independence, and that any arrangement restricting the auditor’s ability to set scope and timing may create significant threats. In May the AICPA told peer reviewers to look hard at SOC 2 practices that lean on third-party platforms, flagging engagements with identical reports, risk assessments, sample sizes and testing across clients. If your bundled auditor’s report looks like every other client’s, your customers’ security teams may notice before the peer reviewers do.
Questions to ask on the scoping call
The scoping call is where you find out how the audit will actually run. Ask every firm on your shortlist the same questions, so you can compare the answers side by side.
- Which companies like ours have you audited? Industry matters less than architecture. A firm that audits cloud-native SaaS will understand your infrastructure-as-code and CI/CD controls. One that mostly audits data centers will ask for things that don’t fit.
- Who will actually do the fieldwork, and who signs? Meet the engagement lead. Ask how many engagements each person carries at once.
- How do you pick samples? For a Type II, ask how they choose sample sizes for daily, weekly, quarterly and annual controls, and whether they will share the sampling approach in advance.
- How do you want evidence delivered? Through your compliance platform, their own portal, or a shared folder? Do they test directly from system exports, or do they want screenshots?
- Type I first, or straight to Type II? A Type I tests design at a point in time. A Type II tests whether controls operated over a period, usually 3 to 12 months. Ask what they recommend for your buyers and your timeline, and why.
- What is the total cost? Get the fee in writing, including readiness work, travel, report issuance and what happens if fieldwork runs long. Ask what next year’s renewal usually costs.
- What happens when you find an exception? Ask how they communicate findings during fieldwork, and whether you will have a chance to respond before the report is drafted.
The best sign on a scoping call is the auditor asking you questions: how your system is built, where customer data lives, which vendors you rely on. A firm that quotes a price before it understands your system is quoting a template.
Red flags
- A guaranteed clean opinion. No auditor can promise one before testing your controls. The AICPA’s ethics staff named “clean audit” and “100% pass rate” promises as a concern in 2026.
- “AICPA-approved.” The AICPA doesn’t approve or certify SOC 2 auditors. The same guidance calls this a misstatement of credentials.
- A timeline that doesn’t add up. A Type II needs an observation period. A firm offering a Type II report in two weeks is either describing a short period or skipping work.
- An auditor who offers to fix your controls. Auditors can explain what the criteria require. If the same firm designs or runs your controls and then audits them, its independence is impaired, and so is your report.
- A price far below every other quote. Cheap audits usually get cheap by testing less, often by relying on your answers instead of checking your systems. The AICPA’s SOC 2 Working Group chair has warned that “fast and easy” may come at the expense of quality.
- No peer review report, or reluctance to share it.
What good auditors will ask you for
A rigorous auditor will ask for more than a weak one, and the extra requests are where your report gets its credibility. Having these ready shortens fieldwork and keeps your engineers out of the evidence-chasing loop.
- A clear system description: What's in scope: the product, the infrastructure it runs on, the people and processes that support it, and the vendors it depends on. This becomes section III of your report, so write it carefully.
- Complete populations: For every control the auditor samples, they need the full list of events to sample from: every new hire, every terminated employee, every production change, every access review. Pull these straight from the system of record, and keep the query you used.
- Evidence they can re-perform: A screenshot shows a setting at one moment. An export with timestamps, or read access to the system itself, lets the auditor check the control actually operated across the period. Good auditors prefer the second.
- Policies that match reality: The auditor will compare what your policies say against what your systems show. If the access policy says quarterly reviews and the records show two a year, that's an exception.
- Owners who can answer questions: Name one person for each control area who can walk the auditor through how it works. Route all requests through a single coordinator so engineers aren't interrupted ten times a day.
Making the choice
Shortlist two or three firms in the category that fits your buyers. Check the license and peer review, run the same scoping questions with each, and ask each for two client references at a company your size. Then pick the firm whose questions were best, not the one whose quote was lowest. Your SOC 2 report will be read by every enterprise security team that reviews you for the next year. It’s worth the extra hour.
Where vCISO Lite fits
vCISO Lite collects SOC 2 evidence continuously from the systems you already run, keeps complete populations with the query that produced them, and signs each piece of evidence so your auditor can see when it was collected and that it hasn’t changed since. Your auditor reviews it through read-only access, so the line between preparing for the audit and performing it stays clear. Book a SOC 2 readiness demo. If you run an audit firm, see vCISO Lite for Auditors.