Schellman总裁Avani M. Desai解析AICPA 2027年SOC 2信任服务准则草案七项调整
SOC 2 is in our DNA: Why the 2027 Trust Services Criteria matter
Schellman & Co. Inc.总裁Avani M. Desai认为,AICPA 2027年SOC 2信任服务准则草案应以清晰、灵活的控制要求回应云环境、自动化及AI带来的风险变化。
文章逐项拆解SOC 2准则草案在治理、风险、事件响应、变更管理及AI方面的调整,可供服务机构评估准则衔接与业务影响。

Masha Stock - stock.adobe.com
I wrote my first SAS 70 report in 2002.
Processing Content
Back then, nobody talked about "trust" as a market. There was no cloud as we know it. A data center was a room down the hall with a lock on the door, and a service auditor's report was something only a handful of controllers ever asked for.
I fell in love with the work anyway. I loved sitting across from a team that ran critical systems for other companies and helping them prove, with evidence, that they did it well.
Before we were Schellman, and before we were BrightLine, we were SAS 70 Solutions. Yes, we actually named the company after an auditing standard. A lesson I've shared many times since: never name your company after a standard that might eventually be replaced! But that's where this firm started. Long before SOC 2 had a name, our team was in server rooms, testing change management, reading access logs and asking, "Show me." So when I say SOC 2 is in our DNA, I mean it literally. It's the fabric this firm was woven from.
I've watched this framework grow up. I watched SAS 70 get stretched far beyond what it was built for, as companies used a financial reporting standard to answer security questions it was never designed to answer. I watched the profession respond with SSAE 16 and the SOC reports in 2011, and SOC 2 finally gave security, availability, processing integrity, confidentiality and privacy a framework of their own. I watched the 2017 Trust Services Criteria turn SOC 2 into the report every SaaS buyer asks for by name.
And this week, I watched the next chapter begin.
The AICPA has released its exposure draft of the proposed 2027 SOC 2 Trust Services Criteria. If finalized as proposed, the revised criteria would apply to engagements beginning on or after December 31, 2027. Early adoption would be allowed, and comments are due January 15, 2027.
Technology Moves Faster Than Frameworks
That's not a criticism. It's just the truth of our world.
When the current criteria came out in 2017, many companies were still in the middle of moving to the cloud. Releases happened on a schedule. A change ticket, an approval and a deployment window were the heartbeat of change management.
Look at the companies we audit today. Infrastructure is code. Teams ship to production dozens of times a day. A typical company runs on a stack of SaaS vendors it doesn't control. And now AI systems can evolve as models, data and configurations change, while agents can make decisions and take actions autonomously.
The 2017 criteria were written as principles, which is why they've held up as well as they have. But every year, auditors and companies have had to stretch them further to fit a world they weren't written for. When a framework has to be interpreted that much, two auditors can reach two different answers, and that's bad for trust.
Here's what the proposed changes do, and why I think we need them.
1. Plain language instead of a COSO translation. The 2017 criteria were organized around the COSO internal control principles, which come from the world of financial reporting. It worked, but it often felt like reading accounting translated into security. The draft removes the COSO reference and gives every criterion a short title that says what it's for. An engineer should be able to read a criterion and know what it's asking. That's a big deal.
2. Governance that fits real companies. The control environment goes from five criteria to two, and language about a "Board of Directors" becomes "Those Charged with Governance." Plenty of the companies that need a SOC 2 are fast-growing startups without a traditional board. The criteria should fit how they're actually governed.
3. Risk management as a living program. Risk assessment is broken into three steps: establish the risk management program, execute it and monitor and improve it. Risk isn't a spreadsheet you update once a year before the auditor shows up. It's a cycle, and now the criteria say so.
4. Less duplication, more substance. The existing control activities criteria (CC5) are removed because the rest of the criteria already cover them. Less overlap means less time mapping the same control three times and more time on the risks that matter.
5. Incident response as one lifecycle. What used to be spread across CC7.2 to CC7.5 is reorganized into a more integrated approach to incident response and recovery. Detecting, responding, recovering and learning are connected activities, and the revised structure better reflects how companies actually manage incidents.
6. Change management that matches how software is built. The current change management criterion becomes three: infrastructure, software you acquire and software you build yourself. A company that runs on infrastructure as code, a dozen SaaS vendors and its own product faces very different risks in each. Treating them the same never made sense.
7. AI, finally named. The draft adds AI-related points of focus across existing criteria to help companies and auditors evaluate the data, monitoring and autonomous decision-making challenges of AI. Our clients have been asking us for two years how SOC 2 applies to their models. Until now, every firm answered that a little differently. A common language means consistency, and consistency means trust.
And maybe the most important design choice: the revised criteria are meant to be flexible enough to accommodate future technologies. We can't rewrite the framework every time technology takes a leap. The goal is criteria that absorb the next leap, whatever it turns out to be.
The CPA Is the Owner of Trust
There are more tools than ever promising to make you "compliant." Dashboards, automation platforms, checklists. Many of them are genuinely helpful, and we work with them every day.
But a tool can't own trust. Trust is earned when an independent professional examines the evidence, applies professional judgment and puts their license and their name on an opinion. That's what a CPA does. The profession has carried that responsibility for more than a century, from financial statements to SAS 70 to SOC 2.
That's why it matters that the AICPA is the one modernizing this framework. The standard for trust should be set by the profession that is accountable for it. And it's why I want to say thank you to the AICPA, to its Assurance Services Executive Committee and to every firm that gave its time and expertise to this work. I'm especially proud of our own team, who were part of the effort. Standards like this don't write themselves. They're built by practitioners who care about getting it right.
Over two decades, I'd like to think I've learned a lot. I've learned that while frameworks change, trust doesn't: the criteria have evolved from SAS 70 to SOC 2 to whatever comes next, but the core question hasn't moved an inch: can your customers rely on you? I've learned that every big shift felt scary at the time: the jump from SAS 70 to SOC 2 felt huge in 2011. Today it's hard to imagine buying software without one. If adopted, the 2027 criteria will feel the same way. Start early, and it will feel like an upgrade, not a fire drill. And I've learned that AI is the next "show me:" twenty years ago it was the server room. Today it's the model, the data it learned from and the decisions it makes.
As for what to do now, first of all, don't panic. Nothing changes for your current audits. The 2017 criteria still apply. Next, it would help to read the draft and start mapping. Fewer criteria doesn't mean fewer controls. It means rethinking how your controls line up. You might also look hard at how you govern AI in your product, before an auditor asks. And, of course, have your say: send the AICPA your comments by January 15, 2027. This is our profession's chance to shape the framework we'll all live with for the next decade.
I've been doing this since 2002, and I'm more excited about SOC 2 today than I was that first year. Twenty-plus years in, the work still comes down to the same two words I learned in my very first audit: Show me.
President
Avani M. Desai is president at Top 100 Firm Schellman & Co. Inc., and a member of the ISACA. Read full bio
来源:Accounting Today(美国会计行业媒体) · accountingtoday.com