Key Takeaways:
- SOC 2 Trust Services Criteria are the standards an auditor uses to evaluate a company's controls in a SOC 2 examination.
- Security, covered by the Common Criteria, is the only category required in every SOC 2 report.
- The other four categories (Availability, Processing Integrity, Confidentiality, and Privacy) are optional and depend on the commitments a company makes to its customers.
- The AICPA defines criteria, not a controls list, so each company designs its own controls to meet them.
- Points of focus are guidance, and the AICPA doesn't require an assessment of each one.
- The AICPA updates the criteria periodically, so the auditor confirms which version applies to each report.
The SOC 2 Trust Services Criteria are the standards an auditor uses to evaluate a company's controls in a SOC 2 examination. They're published by the AICPA's Assurance Services Executive Committee (ASEC) and grouped into five categories: Security, Availability, Processing Integrity, Confidentiality, and Privacy.
Security is required in every report, and the other four categories are added when they match the commitments a company makes to its customers.
There's no official SOC 2 controls list: the criteria describe what a company must achieve, and the company decides which controls will achieve it. For a broader introduction, check our SOC 2 compliance guide.
The Five SOC 2 Trust Services Criteria Categories
Each category groups a set of criteria in the AICPA Trust Services Criteria, and Security holds most of them.
Categories, Criteria, Points of Focus, and Controls: What's the Difference?
Each of these terms means something different in a SOC 2 audit:
- Categories are the five areas listed above. They were formerly called the Trust Services Principles, which is why many guides still refer to SOC 2 principles.
- Criteria are the individual requirements inside each category. The auditor's opinion is based on whether a company's controls meet the criteria in scope.
- Points of focus are characteristics the AICPA lists under each criterion to help companies design and evaluate controls. According to the AICPA, using the criteria doesn't require an assessment of whether each point of focus is addressed.
- Controls are what the company actually does to meet a criterion, such as requiring multi-factor authentication. The company designs them, and the auditor tests them.
Security: The Common Criteria
Security is called the Common Criteria because its criteria apply to every SOC 2 report. The AICPA organizes them in numbered series, and the first series follows the components of internal control in the COSO framework, while the rest cover technology and security operations.
The table below summarizes each area. The example controls reflect common SaaS implementations and our experience with startups, and the criteria don't require any of them specifically.
The criteria don’t explicitly require penetration testing, but a pentest can support monitoring controls and vulnerability detection alongside regular vulnerability scanning. Check how auditors view it in our guide to SOC 2 penetration testing requirements.
Availability
Availability evaluates whether a system stays accessible and operational according to the commitments in the company's SLAs and contracts. The criteria don't set an uptime percentage, so the company's own commitments define what must be met. The Availability criteria cover capacity management, environmental protections, backups and recovery infrastructure, and testing of recovery plans.
Common SaaS controls include capacity monitoring, automated backups stored in a separate location, a disaster recovery plan, and recovery tests.
Processing Integrity
Processing Integrity evaluates whether system processing is complete, valid, accurate, timely, and authorized. It's most relevant for services that run transactions or transform data for customers, such as payments or payroll.
The criteria cover processing specifications, system inputs, processing, outputs, and storage of inputs and outputs. Common controls include input validation, reconciliation of processed records, monitoring for failed jobs, and QA testing before release.
Confidentiality
Confidentiality protects business information designated as confidential, usually by contract or NDA, such as client intellectual property, pricing, or business plans.
The criteria cover identifying and maintaining confidential information and disposing of it when it's no longer needed. Common controls include data classification, encryption at rest, access restricted by role, and documented retention and secure deletion.
Privacy
Privacy covers how a company collects, uses, retains, discloses, and disposes of personal information, in line with its privacy notice. It's the largest optional category and covers topics such as notice, choice and consent, collection, use and retention, access, disclosure and notification, quality, and monitoring and enforcement.
Common SaaS controls include a published privacy notice, consent management, a process for data subject requests, retention schedules, and breach notification procedures.
A Sample SOC 2 Controls List
The table below is an illustrative starting point based on our experience with SaaS startups, to adjust to each company's system, risks, and criteria in scope. One well-designed control often supports several criteria: a user access review, for example, can support several access criteria at the same time.
Policies serve as evidence for several of these controls, and our article on SOC 2 policies explains which ones auditors usually request.
The criteria don't set fixed review frequencies, so the auditor checks whether the frequency a company chooses fits its risks and is followed in practice. If a company already has some controls in place, a SOC 2 readiness assessment maps them to the criteria and shows where the gaps are.
How to Choose Which Criteria to Include
Criteria follow the commitments a company makes to its customers. If contracts promise uptime, Availability is relevant. If the product processes personal information for consumers or employees, Privacy may be expected, and if customers share confidential business data under an NDA, Confidentiality fits.
We recommend starting with Security only, unless a customer specifically requires another category, and adding categories in later periods. For the full scoping method, check how to approach scoping your SOC 2 audit.
How Auditors Use the Criteria
Both SOC 2 report types use the same criteria. In a Type 1 report, the auditor evaluates whether controls are suitably designed to meet the criteria at a point in time, and in a Type 2 report, the auditor also tests whether those controls operated effectively over an observation period.
Upcoming Changes to the Trust Services Criteria
In October 2026, the AICPA proposed an update to the SOC 2 Trust Services Criteria. The proposal restructures the criteria to consolidate duplicative concepts, removes some criteria, adds others, and includes considerations for artificial intelligence.
Until a new version is final and in effect, SOC 2 reports follow the current criteria. A company planning its first report should ask its auditor which version will apply.
SOC 2 and Other Frameworks
The Trust Services Criteria overlap with many ISO 27001 controls and can support parts of GDPR or HIPAA, but a SOC 2 report doesn't by itself demonstrate compliance with either. Check how SOC 2 compares with ISO 27001, or how SOC 2 and HIPAA work together.
Turn the Criteria Into Controls Your Team Can Run
The criteria are public, and a controls list is easy to copy. The hard part is deciding which criteria belong in scope, designing controls a small team will actually operate, and keeping evidence consistent across the observation period. In our experience, startups that adopt a compliance platform's full control library often end up with controls nobody owns and evidence gaps that surface during fieldwork.
At SecureLeap, our SOC 2 consulting helps SaaS startups turn the Trust Services Criteria into a right-sized control set. The work is led by Marçal Santos, who brings more than 20 years of cybersecurity leadership at companies such as Aircall, Citibank, and Talkdesk, and focuses on scoping, control design, and audit readiness.
The result is a defensible scope, fewer controls that nobody operates, organized evidence, less distraction for engineering, and fewer avoidable surprises during the audit.
Book a free 30-minute call to review your current controls and the criteria your customers expect.
FAQ: Frequently Asked Questions
Which SOC 2 Trust Services Criteria are mandatory?
Only Security is mandatory, and its Common Criteria are included in every SOC 2 report. Availability, Processing Integrity, Confidentiality, and Privacy are added when they match the commitments a company makes to its customers.
Which SOC 2 Trust Services Criteria does a SaaS startup need?
Every SOC 2 report must include Security. Startups should add Availability, Processing Integrity, Confidentiality, or Privacy only when they reflect the service commitments they make to customers, contractual requirements, or how the product handles data.
How many criteria are in SOC 2?
SOC 2 has five categories of Trust Services Criteria, and most individual criteria belong to Security. The exact number depends on the version of the AICPA document the auditor applies.
Is there an official SOC 2 controls list?
No, the AICPA publishes criteria, not controls. Each company designs its own controls, and sample lists like the one in this guide are starting points to adapt.
What are points of focus, and do we have to address all of them?
Points of focus are guidance the AICPA lists under each criterion. The AICPA doesn't require an assessment of each one, so a company can leave out points that don't fit its system.
What is the difference between Confidentiality and Privacy?
Confidentiality protects business information a company has agreed to keep confidential, such as a client's intellectual property. Privacy protects personal information about individuals, following the company's privacy notice.
How many controls does a startup need for SOC 2?
There's no specific required number. In our experience, lean SaaS teams do better with a smaller set of well-owned controls that each support several criteria than with a large library copied from a template.
Are the SOC 2 Trust Services Criteria changing?
The AICPA proposed updated criteria in October 2026. Until a new version is final and in effect, SOC 2 reports follow the current criteria, and the auditor confirms which version applies.


