Sikich LLC

11/16/2026 | Press release | Distributed by Public on 11/16/2026 13:44

AICPA proposes major SOC 2 changes for 2027: how...

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.

Why is the AICPA updating SOC 2?

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:

  • Simplification and clarity: Consolidating overlapping criteria, removing unnecessary complexity, and improving consistency in how organizations and auditors interpret requirements
  • Modernization: Better addressing contemporary technologies, operating environments, and risks, particularly those associated with automation, AI, and third-party service providers

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 most significant proposed changes

A simplified and reorganized framework

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.

Greater recognition of AI and emerging technologies

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:

  • Identifying and assessing risks associated with AI-enabled systems
  • Establishing responsibilities and competencies for personnel overseeing emerging technologies
  • Communicating when system outputs are AI-generated and when human validation may be appropriate
  • Evaluating the security, reliability, and integrity of automated processing
  • Monitoring emerging technologies and addressing changes in associated risks

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.

Increased emphasis on risk management and governance

The proposal expands on how organizations establish, document, and maintain risk management programs, with greater emphasis on:

  • Establishing a documented risk management strategy
  • Defining the program's scope and boundaries
  • Identifying and evaluating risks relevant to in-scope systems and services
  • Establishing organizational risk appetite and tolerance
  • Assigning accountability and allocating appropriate resources
  • Evaluating risks associated with operational changes and emerging technologies

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.

More explicit vendor management expectations

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:

  • Vendors supporting critical services and systems
  • Security and operational risks associated with third parties
  • Due diligence and ongoing vendor monitoring
  • Responsibilities for controls performed by outsourced providers
  • Changes in vendor relationships and associated risk exposure

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.

Stronger focus on system documentation and information flows

The proposed framework places additional emphasis on accurate documentation of systems, information assets, and processes, including:

  • Infrastructure, software, and other relevant system components
  • Internal and external information assets
  • Data flows and system dependencies
  • Policies and procedures supporting the control environment
  • Responsibilities for operating and maintaining the system

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.

Modernized system operations and change management

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.

What is not changing

Despite the restructuring, several fundamental aspects of SOC 2 would remain intact:

  • SOC 2 would remain an independent CPA attestation examination.
  • Organizations could continue obtaining Type I or Type II reports.
  • The five Trust Services Categories would remain: Security, Availability, Processing Integrity, Confidentiality, and Privacy.
  • Security would continue to be addressed through the Common Criteria, with category-specific criteria applying when other categories are included.
  • Organizations would retain flexibility in determining which controls are appropriate for their systems and risks.
  • Points of focus would not function as a mandatory checklist or require a separate control for every point.

The objective remains demonstrating that controls are suitably designed and, for Type II examinations, operating effectively to meet applicable criteria.

How organizations should prepare

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:

  1. Evaluate existing control mappings. Compare current SOC 2 controls with the proposed criteria and identify where documentation, responsibilities, or control activities may require adjustment.
  2. Revisit risk assessments. Determine whether existing risk management activities appropriately address emerging technologies, outsourced services, and changes in the operating environment.
  3. Review third-party dependencies. Confirm that critical vendors, outsourced processes, and related responsibilities are appropriately identified, assessed, and monitored.
  4. Validate system documentation. Ensure system descriptions, asset inventories, data flows, and supporting policies accurately reflect the current environment.
  5. Assess AI-related risks where applicable. Organizations using AI should evaluate whether appropriate governance, monitoring, and operational controls exist for relevant AI-enabled processes.
  6. Coordinate with the SOC 2 auditor. Discuss the proposed changes with your auditor to understand potential implications for examination scope, control mapping, evidence requirements, and future reporting periods.

Sikich's perspective: an opportunity to improve SOC 2 efficiency

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.

How Sikich can help

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.

Sikich LLC published this content on November 16, 2026, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on November 16, 2026 at 19:44 UTC. If you believe the information included in the content is inaccurate or outdated and requires editing or removal, please contact us at [email protected]