Proposed Updates to SOC 2 Trust Services Criteria

November 17, 2026 | AI, Compliance, Cybersecurity, Cybersecurity Consulting, SOC 2

The American Institute of CPAs (AICPA) has officially released an exposure draft proposing significant updates to the SOC 2 trust services criteria (TSC). Released on Oct. 28, 2026, this draft marks a pivotal modernization of the framework licensed CPAs use to assess internal controls across security, availability, processing integrity, confidentiality, and privacy. It is a proposal, not a final standard, and the current criteria remain in effect while the draft is under review.

As emerging technologies like artificial intelligence (AI) and automation redefine the operational and threat landscape, these proposed revisions aim to streamline compliance, reduce complexity, and keep SOC 2  reporting relevant for modern service organizations. In this blog, readers will learn:

  • The core drivers behind the AICPA’s structural reorganization of the criteria.
  • How the proposed updates incorporate targeted oversight for AI, automation, and modern threats.
  • Key changes across individual trust categories, adoption timelines, and strategic preparation steps.

A Streamlined, Modernized Structure

A central driver of the proposed revisions is to eliminate friction and redundancy within the existing standard. Over the past decade, rapid advancements in cloud architecture, DevOps pipelines, and decentralized systems have complicated traditional control mapping. In response, the AICPA’s Assurance Services Executive Committee (ASEC) SOC 2 Working Group has restructured the common and category-specific criteria.

Rather than imposing rigid, one-size-fits-all mandates, the framework retains an outcome-based design. The exposure draft consolidates overlapping concepts, removes obsolete requirements, clarifies ambiguous phrasing, and introduces targeted criteria to establish uniform expectations across all five trust services categories.

Structural Highlights Across the Common Criteria

The Common Criteria (CC series)—which serves as the mandatory baseline for every SOC 2 engagement evaluating security—has been refined across several critical domains. Key proposed changes include the following:

  • Risk Assessment (CC3 Series): Shifts to a structured three-pillar model covering the establishment, execution, and continuous monitoring of an entity’s risk management program. It places heightened emphasis on dynamic threat modeling, continuous recalibration, and formal risk registers.
  • Logical & Physical Asset Protection (CC5 Series, formally CC6): Modernizes logical and network controls by explicitly incorporating zero trust architectures, multifactor authentication (MFA), credential lifecycle management, and network segmentation.
  • System Operations (CC6 Series, formally CC7): Focuses heavily on anomaly detection, root-cause analysis, and end-to-end incident containment and recovery protocols.
  • System Development & Change Management (CC7 Series, formally CC8): Restructures change controls into dedicated paths for infrastructure (CC7.1), acquired software (CC7.2), and internally developed applications (CC7.3), reflecting modern CI/CD deployment pipelines, code repositories, and automated testing.
  • Vendor Management (CC8 Series, formally CC9.2): Consolidates oversight of vendors, business partners, and subservice organizations, and extends it to external components such as AI models, APIs, and plugins.

Control Activities (the current CC5 series) is removed, and the CC5 number is reused for asset protection. The business disruption criterion moves to availability.

Navigating the AI and Emerging Technology Frontier

The most substantial addition to the criteria focuses on modern technologies, particularly AI. Rather than creating an inflexible standard that risks fast obsolescence, the working group embedded specific points of focus throughout the criteria to address unique algorithmic risks. Key focal points include:

  • Governance and Transparency: Establishing clear management oversight, specialized technical competency training, and clear user notifications when outputs are AI-generated.
  • Adversarial Protections: Designing defenses against emerging attack vectors such as prompt manipulation, jailbreak chaining, and training data poisoning.
  • Data and Model Integrity: Implementing pre-deployment validation, bias testing, and drift detection to prevent performance degradation or unintended model behavior.

Category-Specific Updates: Availability, Processing Integrity, Confidentiality, and Privacy

Organizations that include additional categories in their SOC 2 reports will also encounter modern operational refinements:

  • Availability: Strengthens capacity forecasting and autoscaling while introducing explicit controls against resource-exhaustion attacks, such as abusive prompt or API floods. It also emphasizes immutable backups, air gaps, and resilience against ransomware.
  • Processing Integrity: Clarifies data lineage and provenance tracking, particularly for data ingested to train, fine-tune, or operate machine learning models.
  • Confidentiality: Reinforces explicit lifecycle rules from data classification through secure disposal, including field-level encryption and customer-managed keys.
  • Privacy: Enhances clarity around data controller versus data processor responsibilities, explicit consent mechanisms, data subject access requests, and privacy-by-design principles.

Timeline and Preparing for Transition

The AICPA has opened a public comment period for the exposure draft running through Jan. 15, 2027. If approved, the final 2027 SOC 2 trust services criteria will take effect for engagements beginning on or after Dec. 31, 2027. Early adoption will be permitted, offering forward-looking teams an opportunity to align their compliance posture ahead of schedule.

Transitioning to modernized compliance criteria requires thorough planning, gap assessments, and cross-functional collaboration between security, engineering, and compliance leaders. Whether your organization is deploying AI capabilities or preparing for your next audit cycle, proactive alignment is essential. 

Contact us today to learn how our experienced team can guide your organization through the proposed SOC 2 updates and help you build a resilient, forward-looking compliance roadmap.

Let's Talk