跳到正文
原文
Accounting Today(美国会计行业媒体)· Chris Gaetano·· 5 天前精选站内评分76

AICPA发布SOC 2框架修订征求意见稿,拟将共同标准由33项减至20项

AICPA proposal aims for SOC 2 reports people actually read

导读

AICPA发布SOC 2框架修订征求意见稿,拟将共同标准从33项减至20项,并与COSO标准脱钩,使报告更短、更便于阅读。草案将AI相关内容分散纳入各项标准,把变更管理拆分为基础设施、外购软件开发和内部软件开发三类;受访者认为审计测试实质不会减少,主要变化是控制重新映射与报告呈现。

推荐理由

草案将共同标准从33项减至20项,并拆分变更管理类别,为服务机构重新映射控制、优化报告呈现及调整审计工作提供直接对照。

正文
  • Key Insight: The real reason the AICPA is decoupling its security framework from COSO standards.
  • Forward Look: What's coming: The January 15, 2027 deadline for public comments on the exposure draft.

The AICPA has proposed a new, leaner SOC 2 framework that accounts for changing technology, especially AI, with an eye towards shorter, more useful reports people actually read versus skim for exceptions.

Processing Content

"The way organizations manage and process information and identify risk has changed substantially over the past decade," said Amy Pawlicki, the AICPA's vice president of assurance and advisory innovation in a statement. "These proposed revisions are intended to improve the usability of SOC 2 reports and refine criteria so they can adapt to rapidly evolving technologies."

Released late last month, the exposure draft proposes, among other things, reducing the number of common criteria from 33 to 20 as well as decoupling them from those of the Committee of Sponsoring Organizations of the Treadway Commission (COSO), which were incorporated into the framework in 2017. The proposed new common criteria are as follows: 

  1. CC1.1 — Integrity and Ethical Values. 
  2. CC1.2 — Commitment to Competence 
  3. CC2.1 — System Documentation 
  4. CC2.2 — Communication of Policies, System Components, and Responsibilities 
  5. CC3.1 — Establish and Structure the Risk Management Program 
  6. CC3.2 — Execute the Risk Management Program 
  7. CC3.3 — Monitor and Improve the Risk Management Program 
  8. CC4.1 — Monitoring and Communication of Deficiencies 
  9. CC5.1 — Logical Access Over System Resources 
  10. CC5.2 — Data Center and Facility Management 
  11. CC5.3 — Management of Information Technology Devices and Software 
  12. CC5.4 — Network Integrity and Boundary Protection 
  13. CC5.5 — Encryption of Data 
  14. CC5.6 — Vulnerability Identification and Management 
  15. CC6.1 — Monitoring and Operation of System Components 
  16. CC6.2 — Incident Response Programs 
  17. CC7.1 — Infrastructure Development & Change Management 
  18. CC7.2 — Acquired Software Development & Change Management 
  19. CC7.3 — Internally Developed Software Development & Change Management 
  20. CC8.1 — Vendor Management

Terry O'Brien, a SOC 2 specialist principal at top 50 firm Schellman who'd helped develop the exposure draft, said this was done to change how people engage with the SOC 2 report. The move to COSO, while well-intentioned, ultimately resulted in a lot of confusion and duplication as redundancies in the criteria meant reports were getting longer and longer and less and less useful as a result, according to O'Brien. People are increasingly hesitant to give detailed reading to such reports, which undermines the original intention of the framework. O'Brien said the AICPA intends, through these proposed changes, to bring the SOC 2 report closer to its original intended use. 

"It's all geared to making the SOC report a little more friendly to end users because right now if you're getting a report that's a couple hundred pages you're scanning it to just see whether there's exceptions in it. You're not necessarily using the report the way it is intended to be used," he said in an interview. 

Brad Barrett, national solution leader for strategic services and SOC services at Top 10 firm Grant Thornton, added that another intention was to widen its application to a broader group of companies. He noted that as the global economy becomes increasingly technological, IT security and controls have become even more important, and so too does the need for assurance around them. 

"As technology has evolved, as more and more companies have needed SOC 2s as they put more into the cloud and outsource more, the SOC 2 has become a staple in vendor management programs, and the more it gets used the more spotlight there is on it, the more scrutiny. So, how do we make this applicable to a larger group of companies?" he said in an interview. This in mind, the exposure draft also removed references to boards of directors, in favor of focusing more on the governance of specific systems and areas. Alongside a simpler SOC 2 report, these changes are meant to make the examination process more accessible to a wider range of companies who may not necessarily have the time or resources to take part today. 

"What the simplification and reduced duplication does is help focus. This doesn't have to be a Fortune 500 public company. … It's little changes like that to make it more clear for more types of companies and more sizes of companies to really lean in and understand how it applies to them," he said. 

He noted that while the exposure draft discords the COSO aspect of things, this makes room for other frameworks the company may embrace instead. "In the past, it was mapped to the COSO framework and they tried to mix that into the SOC 2 framework. They essentially pulled out the COSO piece and now organizations need to decide and determine ahead of time what is their framework. Are they still using COSO? Are they using a NIST framework? What are they using? … How does this layer into how we present and report on these controls in the SOC 2?" he said. 

The exposure draft also reorders certain sections to make them flow more logically and easily. O'Brien pointed to the risk assessment sections as a good example of this. 

"The risk assessment process, from identifying risks to mitigating the risks, and then monitoring those risks were split across three criteria that were out of order. It's like if you actually wanted to reflect that in the report correctly, the reader would have to know to go to CC three and then CC five and then CC two, which didn't make any sense at all. So, I think now, just having risk assessment all collapsed into one makes a whole heck of a lot more sense, and like you can understand that process more," he said. 

Despite AI being woven now throughout the global economy, the AICPA chose not to create a section dedicated specifically to the technology, instead opting to reference AI in various parts through the entire exposure draft. O'Brien said the question of whether or not to do so was a lengthy one but ultimately they decided that AI touches too many areas to isolate it to just one section and furthermore AI does not, itself, fundamentally change the need for controls. An access control is an access control, he said, it does not necessarily matter what technology is behind it, the important thing is to make sure the access is properly managed. 

"So, I think it's more of an effort between the organization, the auditor to include it in the report, but not necessarily a separate just add-on section," he said. 

One area that saw not a compression but an expansion was change management. While the current version had only one change management criteria to be applied in all cases, the exposure draft proposes three: one for infrastructure development, one for acquired software development and one for internal software development. Barrett said this acknowledges that the one-size-fits-all approach was not working, because different changes call for different responses. He noted that it might represent an adjustment for auditors. 

"Before it was one big change management conglomerate, where it just says all changes are done according to policy. Here it breaks that out and says there's multiple kinds of changes and you have to address each one separately: infrastructure changes, acquired software changes, and internally developed changes. I've got I have clients who approach that in different ways, and I think things like that, where it does sort of change how they've been doing things, either in practice or in reporting and auditing, are just going to cause a little bit adjustment, where they need to rethink why they're doing it, how they're doing it, how they're documenting it," Barrett said. 

While some of the particulars might change between the exposure draft and the final version, both O'Brien and Barrett said auditors will likely need to spend time not so much changing the controls themselves but remapping them to see which ones satisfy which criteria in the new framework. While this might not exactly be how an auditor wishes to spend their day, Barrett said ultimately it will lead them to reassess what controls do and do not work and rethink their clients' security and compliance posture, which will ultimately be a positive development. Sometimes, he said, there is a tendency "to just throw everything against the wall, see what sticks" which serves to duplicate controls multiple times, making the report longer and less useful at the same time. 

"As we do the remapping against the new criteria that should fall off some and I think it will just make it easier to see which points of focus truly haven't been addressed or truly haven't been considered in the latest wave of technology or the latest phase of the market and I think that will highlight gaps and opportunities to really improve people's security and compliance posture," he said. 

O'Brien noted that while the changes are great, the substantive reality of testing and examination has not changed. There's no reduction in testing, he said, just a remapping and presentation of things in a different way, one that is much more user-friendly than before. 

"I think how the reports are going to be, or how they're going to look after this, it's going to be so much easier to read, the end user will be able to look at it, understand it. It'll actually add a lot more value that way," he said. 

The AICPA's SOC 2 Working Group is seeking public comment on the exposure draft through Jan. 15, 2027. If approved next year, the proposed 2027 SOC 2 Trust Services Criteria would be effective for engagements beginning on or after Dec. 31, 2027, with early adoption permitted.

Introductory bullet points created by AI with editorial review.

Gaetano-Chris

Technology Editor

Chris Gaetano is the technology editor for Accounting Today. He brings with him more than a decade of experience covering the accounting profession... Read full bio

来源:Accounting Today(美国会计行业媒体) · accountingtoday.com

审计热点 是聚合摘要和阅读索引,原文版权归各来源所有,引用请以官方原文为准。如果你是来源方,希望更正、下架或调整展示方式,可以通过反馈页联系我们。

来自微信公众号的内容,本站仅呈现摘要与原文链接,不转载文章全文;文章权利归属原作者及原公众号

关于使用条款隐私信源