11/16/2026 | Press release | Distributed by Public on 11/16/2026 13:44
The American Institute of Certified Public Accountants (AICPA) has released an exposure draft proposing significant revisions to the SOC 2 Trust Services Criteria (TSC), representing one of the framework's most substantial updates since 2017. The proposal aims to simplify the Common Criteria, improve reporting consistency, and modernize the framework to address evolving cybersecurity risks, third-party dependencies, and emerging technologies, including artificial intelligence (AI).
While the changes are not yet final, organizations should begin evaluating how existing SOC 2 controls align with the streamlined framework and its greater attention to emerging risks. For most, the transition should require reassessment rather than rebuilding from the ground up. If finalized, the revised criteria would become effective for engagements beginning on or after December 31, 2027, with early implementation permitted. The AICPA is accepting public comments through January 15, 2027.
Since the current Trust Services Criteria were introduced in 2017, cloud computing, outsourced technology services, automation, and AI have reshaped how organizations develop, operate, and secure information systems.
The proposed revisions address two primary objectives:
SOC 2 would remain principles-based, focusing on whether controls appropriately address an organization's risks, service commitments, and system requirements rather than prescribing specific technologies or security controls.
The proposal reorganizes the Common Criteria, which form the foundation of SOC 2 examinations, into eight areas:
| Proposed criteria | Focus area |
| CC1 | Control environment |
| CC2 | Information and communication |
| CC3 | Risk assessment |
| CC4 | Monitoring activities |
| CC5 | Logical and physical asset protection |
| CC6 | System operations |
| CC7 | System development and change management |
| CC8 | Vendor management |
The existing CC5 ("control activities") would no longer be a separate category. While many underlying expectations remain familiar, the proposal consolidates related requirements and reorganizes how organizations demonstrate compliance.
What this means for organizations: existing SOC 2 controls may not need replacement. However, organizations should review their control matrices, risk assessments, policies, and evidence collection procedures against the revised criteria. Those using automated compliance platforms may also need to update control mappings and evidence collection workflows.
The proposed criteria explicitly recognize AI and other emerging technologies, which can introduce risks involving autonomous decision-making, data quality, unpredictable outputs, monitoring and human oversight.
The revised points of focus introduce considerations relevant to:
What this means for organizations: companies using AI in service delivery, internal operations, or customer-facing applications should consider whether their risk assessments and controls adequately address those technologies. However, the revisions would not establish a separate AI certification requirement or mandate specific AI controls for every organization. Applicability depends on an organization's systems, risks, and service commitments.
The proposal expands on how organizations establish, document, and maintain risk management programs, with greater emphasis on:
What this means for organizations: a periodic risk assessment alone may not sufficiently demonstrate the broader risk management activities contemplated by the proposal. Organizations should consider how risk management is integrated into governance, decision-making, and ongoing monitoring. For smaller organizations, this does not necessarily require complex governance structures. Risk management practices should remain proportionate to the organization's size, complexity, and risk exposure.
Establishing "vendor management" as a distinct Common Criteria category, CC8, gives greater visibility to risks from cloud providers, managed service providers, outsourced software developers, and other third parties.
Organizations should consider whether their vendor management programs address:
What this means for organizations: organizations should review vendor inventories, third-party risk assessments, contractual commitments, and monitoring procedures, particularly for vendors performing activities or controls necessary to meet SOC 2 commitments. The revisions would not eliminate existing concepts of subservice organizations or complementary controls. Rather, they reinforce the importance of identifying and managing third-party dependencies.
The proposed framework places additional emphasis on accurate documentation of systems, information assets, and processes, including:
What this means for organizations: system descriptions, asset inventories, architecture diagrams, and data flow documentation should accurately reflect current operations and align with the activities and controls included in SOC 2 examinations. Accurate documentation provides the foundation for identifying risks, establishing controls, and determining examination scope.
The proposal also reorganizes expectations for system operations, security monitoring, system development, and change management to reflect greater reliance on cloud infrastructure, automated deployments, and third-party development.
What this means for organizations: existing controls may continue to satisfy the criteria, but organizations should reassess their design, documentation, and mapping, including which controls are performed internally and which depend on external providers.
Despite the restructuring, several fundamental aspects of SOC 2 would remain intact:
The objective remains demonstrating that controls are suitably designed and, for Type II examinations, operating effectively to meet applicable criteria.
Because the criteria remain proposed, organizations do not need to prematurely redesign their SOC 2 programs. They can, however, begin evaluating potential transition needs.
Consider these six steps:
SOC 2 compliance programs can become increasingly complex as organizations add controls, documentation and requirements. The result can be overlapping controls or administrative activities that contribute little additional risk reduction.
The proposed revisions create an opportunity to address that complexity. Organizations should not treat the transition as simply a control-renumbering exercise. Instead, they should evaluate whether existing controls remain relevant, documentation reflects current operations, and compliance activities align with business risks. Increased attention to vendor management, risk governance, system documentation, and emerging technologies reinforces the need for controls that accurately reflect how organizations operate.
For organizations with established SOC 2 programs, early planning may help minimize disruption to future examination and unnecessary duplication of effort. Those pursuing SOC 2 for the first time can use the proposed criteria to help build a more sustainable compliance program.
Sikich's Third-Party Risk Attestation professionals support organizations throughout the SOC 2 compliance lifecycle, from initial readiness assessments and control development through independent SOC 2 examinations. As the proposed framework moves toward finalization, Sikich can help organizations understand potential implications, evaluate existing controls against the revised criteria, and plan an efficient transition.
Contact us to discuss how the proposed 2027 SOC 2 revisions may affect your organization.
Source: AICPA Assurance Services Executive Committee, Proposed 2027 SOC 2 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy, Exposure Draft, October 27, 2026.
The proposed criteria remain subject to public comment and revision. The information in this advisory reflects the exposure draft and should not be interpreted as final requirements.
This publication contains general information only and Sikich is not, by means of this publication, rendering accounting, business, financial, investment, legal, tax, or any other professional advice or services. This publication is not a substitute for such professional advice or services, nor should you use it as a basis for any decision, action or omission that may affect you or your business. Before making any decision, taking any action or omitting an action that may affect you or your business, you should consult a qualified professional advisor. In addition, this publication may contain certain content generated by an artificial intelligence (AI) language model. You acknowledge that Sikich shall not be responsible for any loss sustained by you or any person who relies on this publication.