back

Your Next SOC 2 Audit Will Be Tougher, and That’s a Good Thing

I manage SOC 2 and HIPAA audits for numerous companies every year, and have for many years, as a fractional CISO for portfolio companies and clients. That gives me a good read on what a typical year looks like. This year was not typical: our own company’s SOC 2 audit took roughly five times as many auditor questions as the year before. Same controls, same team, same audit firm. What changed was the standard the auditor is now held to. If you’re a founder or CTO, plan on this being the new normal.

The cheap report caught up with the industry

For years, plenty of companies skipped a real audit and bought a fast, inexpensive SOC 2 report that looked nearly identical to the one issued to the company next door. The reports were real documents from licensed CPA firms, so they passed a glance, and most buyers never looked closer.

That ended this year. Earlier this year a well-funded compliance automation startup, Delve, was reported to have been linked to hundreds of near-identical SOC 2 reports: the same boilerplate, the same placeholder test values, and every Type 2 report claiming zero security incidents. The company disputes the allegations. But the episode became the example everyone points to when they talk about rubber-stamped audits, and buyers started asking a question they had stopped asking: did anyone actually test this company?

Auditors answer to auditors

SOC 2 auditors are CPAs, and CPA firms have their work reviewed by other CPA firms through the AICPA’s peer review program. In May 2026 the AICPA told those reviewers to look much harder at SOC 2 practices.

An engagement is now flagged as nonconforming when a firm’s SOC 2 work shares identical reports, risk assessments, sample sizes, and testing procedures across clients, because that means the audit never responded to the company’s actual risks. Reviewers pull several engagements from different partners and compare them to each other and to prior years, looking for copy and paste. Since June 1, AICPA staff have been running direct outreach to firms with SOC 2 practices.

The AICPA was direct about the reason. “Some firms are leaning too heavily on third-party SOC platforms without applying the professional judgment required by our standards,” said Carl Mayes, the AICPA’s vice president for ethics and firm quality.

For an audit firm, a nonconforming finding can mean a deficiency in its own peer review, which is serious enough to change how it works. So the firm that audits you now has to prove it really tested you: your samples, your evidence across the full observation period, your specific risks. Not a checklist carried over from the last client. That is where the extra questions come from.

More is coming

This is not going away. In February 2026 the AICPA’s Auditing Standards Board issued an exposure draft revising the attestation standards SOC 2 runs on, tightening how auditors evaluate evidence and how risk assessment accounts for fraud and noncompliance. If adopted, it takes effect in 2029, but the direction is clear. The Trust Services Criteria themselves haven’t changed since the 2022 update. What’s changing is how seriously they’re tested, and auditors are already pressing on areas the criteria barely address, especially AI use.

What this means for your company

  • Evidence has to exist all year. Auditors now sample across the full observation period. Assembling it the month before no longer works.
  • Your risk assessment has to be yours. Your threats, your systems, your decisions, in your own words. A generic one now stands out as a problem.
  • Budget real time for auditor requests. Larger samples, more follow-ups. Ours roughly quintupled, and we were ready for it.
  • Follow the processes you wrote down. A control that exists on paper but not in practice is exactly what a real audit finds.
  • A compliance platform is readiness, not the audit. It organizes evidence and tracks controls. It does not replace the auditor’s judgment, and the AICPA just said so. We use one and it helps, but it is not what gets you through the audit.
  • Choose an auditor with a reputable track record. Ask how long the firm has done SOC 2 work, who reviews its engagements, and whether each report is tailored to the client. A firm that promises a report in a few weeks for a low flat fee is exactly the kind of firm the AICPA is now looking at.
  • Put someone experienced in charge of the audit. A CISO, in-house or fractional, who has run successful SOC 2 and HIPAA audits many times knows what auditors ask for, how much evidence is enough, and where companies get tripped up. That experience is the difference between a long audit and a painful one.

Why “good”

The cheap report was never worth much. It just took the industry a while to admit it. Enterprise buyers and their security teams have learned to read a SOC 2, and a template reads like a template. A real audit, even one that costs you five times the questions, now does its job: it separates the companies that built security in from the ones that bought a document.

Key Takeaways

  • SOC 2 audits got materially harder in 2026, and the change is structural, not a one-off.
  • The AICPA’s peer review program now flags cookie-cutter SOC 2 engagements as nonconforming, so auditors must prove they tested each client specifically.
  • A proposed revision to the attestation standards points the same direction for 2029 and beyond.
  • Plan for year-round evidence, a company-specific risk assessment, and far more auditor requests.
  • Choose a reputable auditor and a CISO with a track record of successful audits. A compliance platform supports the audit; it is not a substitute for it.

Conclusion

If your audit felt tougher this year, that is not a sign something went wrong. It means the audit is finally doing its job. Build the evidence into how you operate, keep your risk assessment honest and specific, and treat every auditor question as practice for the enterprise buyer who will ask the same thing.