The Proposed 2027 SOC 2 Trust Services Criteria: What's Changing and What It Means
Paul Wenham explains the proposed 2027 SOC 2 criteria, AI points of focus, governance and change management updates, transition effort and Throughline's approach to fees.
What's proposed: the AICPA has released an exposure draft of the 2027 SOC 2 Trust Services Criteria. Comments close January 15, 2027. If finalized, the criteria apply to engagements beginning on or after December 31, 2027, with early adoption permitted.
What changes: fewer, clearer criteria with short titles; governance language that reflects how companies actually operate; risk management treated as a full program; change management split into infrastructure, acquired software and in-house software; and AI risks addressed through points of focus rather than new criteria.
Our view: these are mostly practical, guidance-based updates, not new rules. Control mappings will change, but the substance of a good SOC 2 report largely won't. The draft makes explicit several areas many reports don't cover well today.
When to move: we expect clients to start transitioning within about three to six months, once the final criteria have bedded down. Enterprises are likely to favor reports on the new criteria.
Effort and fees: 0–20% extra effort for new companies, depending on the audit methodology, and 10–50% for companies transitioning. We don't expect our audit fees to change, and we'll absorb the transition effort for existing clients rather than charge for it.
What has the AICPA proposed?
In late October 2026, the AICPA's SOC 2 Working Group released an exposure draft of the proposed 2027 SOC 2 Trust Services Criteria, the first major update since 2017. It's open for public comment until January 15, 2027. If issued as final, the new criteria would apply to engagements beginning on or after December 31, 2027, and early adoption would be permitted.
The update has two aims:
To reduce complexity and make SOC 2 reports clearer and easier to use.
To modernize the criteria for emerging technologies such as AI and automation, while staying flexible enough for technologies still to come.
Each criterion has a short title stating its main objective
Control environment (CC1)
Five criteria, referring to the board of directors
Two criteria, referring to those charged with governance
Risk assessment (CC3)
Four criteria
Three: establish, execute, and monitor and improve the risk management program
Control activities (CC5)
Three criteria
Removed, as other criteria already cover them
Incident response (CC7.2–CC7.5)
Four criteria
One: CC6.2 Incident Response Programs
Change management (CC8)
One criterion
Three CC7 criteria: infrastructure, acquired software, and internally developed software
Availability (A1.2)
One criterion
Two: A1.2 Environmental Protections and A1.3 Resilience Capabilities
Confidentiality (C1.1)
One criterion
Two: C1.1 Classification and Inventory and C1.2 Maintenance of Confidential Data
Processing Integrity and Privacy
No change highlighted
Largely unchanged
AI
No AI-specific content
No new AI criteria; AI-specific points of focus added across the criteria
Does the update change what a SOC 2 report should cover?
Not materially, in our view. For the most part, these are practical, guidance-based updates rather than new rules.
The structure does change. Criteria are merged, split and renumbered, so the control lists and mappings in reports will change as companies move to the new criteria.
The substance of a good SOC 2 report largely stays the same. What the draft does is make explicit several areas that reports arguably should already cover, but often don't in practice.
What practical problems do the changes fix?
Governance that reflects how companies operate
The 2017 criteria spoke specifically about the board of directors. Plenty of companies have box-ticked a board control, even though many don't have a formal board, or their board plays no real role in security and risk management. Referring instead to ‘those charged with governance’ aligns the criteria with how governance actually works.
Less duplication
The 2017 criteria created a lot of duplication in practice. Consolidating the control environment, control activities and incident response criteria cuts repeated mappings and the admin of managing them, without losing substance.
Risk management as a living program
Risk management is fundamental to what SOC 2 is meant to be, yet it has often become a box-ticking exercise: an annual risk assessment, mapped to every risk criterion. Splitting it into establishing, executing, and monitoring and improving the program recognizes the governance behind it. Risk management should be a living part of the security program, not a once-a-year document.
How do the updates address AI?
There are no new AI-specific criteria. Instead, AI-specific points of focus are added across the criteria, including common criteria that apply to every SOC 2. One example asks organizations to consider risks introduced by AI components, such as:
manipulated training data, adversarial inputs and model misuse
unreliable, biased or unintended outputs
prompt manipulation and data poisoning
In our view, the existing criteria should already have covered much of this. Criteria on logical access and the security of data and technology were deliberately written to adapt to any technology, including AI tooling. In practice, though, few reports address AI. Making it explicit means every audit firm should now be considering it.
Change management splits into three types of change: software developed in-house, acquired third-party software, and infrastructure. Acquired software has never been explicitly called out before.
Infrastructure: closing a common gap
Many SOC 2 reports today focus on change management for in-house software. Yet many controls a report relies on, such as network and encryption settings, live in infrastructure. Without infrastructure change management, those controls could change during the period without adequate assurance over how. The new criteria close that gap.
Acquired software: a question of materiality
This is the change to watch. Most organizations use dozens or hundreds of third-party tools, and these rarely follow formal change management the way in-house software does.
The most likely approach is restricting admin access to authorized administrators, so only they can make changes. Depending on how far auditors take it in practice, though, testing across that many tools could become a large dependency.
When should you move to the new criteria, and how much effort is it?
When the 2017 criteria came out, many organizations adopted them early, especially new companies pursuing SOC 2 for the first time. It made more sense to start on the new criteria than to change later.
We expect the same pattern. The earliest adopters of a standard still in flux can end up with more headaches than it's worth. Once the final criteria are issued and bedded down, there's a real advantage to moving early. We expect clients to start transitioning within about three to six months.
How much extra effort is the transition?
For new companies pursuing SOC 2 for the first time on the new criteria, we expect 0–20% extra effort, depending on the audit methodology. The upper end applies mainly where audit firms follow thin templates that cover only the minimum today.
For companies transitioning from the 2017 criteria, we expect 10–50% extra effort. Where a company lands in that range depends on three things:
How embedded the current framework is. A control framework deeply built into a compliance platform and day-to-day operating practices, audited with a rigid platform or methodology established over years, sits towards the upper end.
How agile the company is. A smaller company without a platform, working with a flexible audit firm, sits at the lower end: a few added questions, and perhaps 5 to 10 new controls in scope that largely reflect what it already does.
Whether the new points of focus are net new. If existing audits already considered these risks, little changes. If not, there's added work to implement new controls and audit them for the first time.
At Throughline, we plan to absorb that transition effort within our current client fees, with no add-on projects or fees, to help our clients make the move at whatever point suits them.
Will enterprises favor reports on the new criteria?
We expect so. After the 2017 update, enterprises commonly asked not just whether a vendor had a SOC 2 report, but which criteria it was issued under. The newer criteria came to be seen much like a Type 2 compared with a Type 1: more substantial and more reliable.
That gave companies a reason to move early and avoid being seen as laggards. The same dynamic is likely once the 2027 criteria are final.
Will SOC 2 audit fees change?
We don't expect our audit fees to change, and we aren't planning to change them because of the updated criteria.
That includes the extra effort of transitioning existing clients, which we'll absorb within current fees rather than charge for as an add-on.
For firms whose audits already covered these areas thoroughly, the effort should change little. Others may need to adjust their pricing, as the draft makes some expectations more explicit.
We see that as a net positive for the industry. Clearer criteria should narrow the differences in rigor between firms, and raise the baseline every SOC 2 report is held to.
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.
Beyond credentials, frameworks and pricing, ask who will do the work, how offshore teams operate, when auditors are available, whether controls fit your business and what happens when plans change.
How certification bodies set ISO 42001 audit days under ISO/IEC 42006, how AI roles and in-scope headcount drive the price, and when scoping to engineering and product makes sense.
SOC 2 for startups, from planning to reporting: typical USD audit fees, timelines, internal team hours, AI-assisted readiness and keeping a first report on track.
SOC 2 for mid-sized companies: typical USD costs, timelines and team hours, plus existing controls, multiple products, regulatory drivers and auditor changes.
SOC 2 for enterprises: typical USD costs, timelines and team hours, plus ISO 27001 reuse, multi-entity scope, vendors, procurement and customer deadlines.
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.
Three worked SOC 2 examples: AI-written code, agent-led access reviews and agents changing customer data. Follow each risk through its control, audit test and evidence.
Build an AI management system around your real use cases: an agent register, risk and impact assessments, shared responsibilities, governance policy and Statement of Applicability.
How to cover production AI agents in SOC 2: governance, access, change management and monitoring, with indicative criteria mappings, customer responsibilities and practical audit expectations.
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.
Experienced CTOs don't choose a SOC 2 audit firm on price or speed. They look for tech stack expertise, a tailored approach, flexible scheduling, responsiveness and year-round partnership, because those factors decide how much time the audit really costs.
What Security, Availability, Confidentiality, Processing Integrity and Privacy each cover, how often they're included, and how to decide which belong in your SOC 2 report.
Which SOC 2 report should come first? Six client cases, practical decision tables and an illustrative 18-month cost comparison explain when to start with Type 1 and when to go straight to Type 2.
How long a SOC 2 Type 2 observation period should be, how to work backwards from a customer deadline, when auditors test, why reports run late and how much buffer to build in.
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.
Five signals of real quality in assurance and security, with practical guidance on building a compliance program that supports customer TPRM, repeatable enterprise reviews and revenue growth.
The person leading your SOC 2 audit is the most underrated factor in choosing an audit firm. Companies compare price, timelines and platform integrations, then barely ask who will actually do the work.
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.
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.
CPA firm registration, signing licenses and peer review are the starting point, not proof of quality. A practical guide to checking credentials and asking the questions that matter before choosing your SOC 2 auditor.
Neither is better for everyone. The right choice depends on your customers, how you run security and where you are headed. For AI-native and AI-centric companies, SOC 2's flexible criteria usually make it the stronger starting point.
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.
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.
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.
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.