Last updated: November 7, 2026
Reviewed by an information security professional (CISSP) on November 11, 2026.
A SOC 2 compliance checklist only helps if it lines up with what the auditor really tests: the AICPA’s Trust Services Criteria. Most free SOC 2 checklists online are vendor lead magnets built around tools. This one lays out the criteria, the controls teams usually rely on to meet them and the evidence a CPA firm will want to see.
Short answer: A SOC 2 compliance checklist has nine steps: pick the report you need, define the system in scope, choose your Trust Services Categories, run a gap assessment, write policies, put controls in place, gather evidence, engage an independent CPA firm and complete the audit period. Security is always in scope, and it includes 33 common criteria.
Key takeaways
- SOC 2 is an attestation report from an independent CPA firm, not a certification, and no law demands it; customers do.
- Security is required and spans 33 common criteria across nine series, CC1 to CC9. Availability, processing integrity, confidentiality and privacy are optional extras.
- The criteria don’t dictate tools. The AICPA says applying them doesn’t require checking whether every point of focus is addressed.
- In October 2026 the AICPA proposed revised criteria, with comments due January 15, 2027, for engagements starting on or after December 31, 2027.
- First audits usually slip on evidence. Set up a monthly and quarterly evidence calendar before the audit period begins, not partway through.
Table of Contents
What SOC 2 compliance actually requires
In practice, SOC 2 compliance means a clean examination of a service organization’s controls, reported against the AICPA’s 2017 Trust Services Criteria (with points of focus revised in 2022). An independent CPA firm carries it out and issues a report containing an opinion. No certificate is issued, and no government agency grants “SOC 2 compliance.”
That leads to two practical consequences for SOC 2 compliance:
- The requirements are the criteria, not a list of controls. Each criterion sets an objective, like restricting logical access or responding to security incidents. You choose the controls that meet it, and the auditor tests whether they work.
- Points of focus are guidance only. The AICPA’s criteria document says applying the criteria “does not require an assessment of whether each point of focus is addressed.” They help you design controls; they aren’t a checklist you have to complete line by line.
The five Trust Services Categories
| Category | What it means (AICPA definition, paraphrased) | Required? |
|---|---|---|
| Security | Information and systems are protected against unauthorized access and disclosure, and against damage | Always |
| Availability | Systems are available for operation and use to meet the company’s objectives | Optional |
| Processing integrity | System processing is complete, valid, accurate, timely and authorized | Optional |
| Confidentiality | Information designated as confidential is protected | Optional |
| Privacy | Personal information is collected, used, retained, disclosed and disposed of to meet objectives | Optional |
Security also goes by the name common criteria, since every SOC 2 report includes it. Add other categories only when customer contracts or your own commitments make them relevant. An uptime SLA is a solid reason to add availability; a vague feeling that “more is better” isn’t.
If you haven’t chosen a report type yet, start with our guide to SOC 2 Type 1 vs Type 2. The checklist below works for either, but a Type 2 report requires controls that operate consistently across a full period. If a customer asked for a SOC 1 report instead, our SOC 1 vs SOC 2 guide explains the difference. Defense contractors handling CUI need CMMC 2.0, which a SOC 2 report doesn’t replace.

SOC 2 compliance checklist: 9 steps from scoping to report
1. Confirm why you need SOC 2 compliance and which report
Identify the trigger. It’s usually a customer security questionnaire, a procurement requirement or a contract clause. Ask the customer which report they’ll accept, which categories they expect and when they need it. Their answer sets both your deadline and your scope.
2. Define the system in scope
Define the boundary of the system the report will cover: the service you sell, plus the infrastructure, software, people, data and procedures that support it. Leave out internal tools that never touch customer data unless a customer asks about them.
List the vendors that operate part of that system, like your cloud host, identity provider and payment processor. For each, plan how you’ll show their controls are in place. A vendor’s own SOC 2 report is the standard evidence.
3. Choose your Trust Services Categories
Security is required for SOC 2 compliance. For every optional category, write one sentence explaining why it’s included or excluded. That sentence saves time when the auditor and your customers inevitably ask the same thing.
4. Run a gap assessment against the criteria
Go through all 33 common criteria and mark each as met, partly met or missing. Record the control, owner and evidence for every one. The table in the next section offers a starting map.
5. Write the policies the controls depend on
Policies come first on most SOC 2 checklists. Auditors check whether they exist, were approved and were communicated to staff. A typical first batch covers:
- Information security policy and acceptable use
- Access control, covering onboarding, role changes and offboarding
- Change management and secure development
- Incident response and breach notification
- Business continuity and disaster recovery
- Vendor management
- Data classification, retention and disposal
- Risk assessment methodology
Keep them short and accurate. A 40-page policy your team ignores is worse than a 4-page one it follows, because the auditor tests against what you wrote down.
6. Implement and assign the controls
Your SOC 2 checklist should assign every control one owner and a frequency, whether daily, monthly, quarterly or annually. A control with no owner is the top reason evidence goes missing during a Type 2 period.
7. Set up evidence collection
For each item on your SOC 2 checklist, decide what proves the control actually ran: a ticket, a log export, a signed review or a dated screenshot. Set up a recurring calendar for anything periodic, like quarterly access reviews. Compliance automation tools can collect much of this evidence for you, but they don’t take the place of control owners.
8. Pick an independent CPA firm and consider a readiness review
Only a CPA firm can issue a SOC 2 report. Ask prospective firms about their experience with companies like yours in size and stack, how they test cloud environments and what they’ll need from you before fieldwork begins. A readiness review ahead of the formal audit surfaces gaps while there’s still time to close them.
9. Complete the audit and keep it running
For a Type 1, the auditor tests design as of a single date. For a Type 2, your controls have to operate throughout the audit period, and the auditor samples evidence from across it. Once the report is out, the cycle begins again. Many customers want a fresh report every year, so plan around an annual cycle.
SOC 2 checklist of controls: the common criteria, CC1 to CC9
This is the heart of the SOC 2 compliance checklist. The criteria column summarizes the AICPA text, and the controls column shows common ways teams satisfy each series; the criteria don’t require any particular tool.
| Series | What the criteria cover | Controls teams commonly use | Evidence the auditor may ask for |
|---|---|---|---|
| CC1 Control environment (5 criteria) | Integrity, board or management oversight, structure, competence, accountability | Code of conduct, org chart, background checks, job descriptions, annual performance reviews | Signed code of conduct acknowledgments, background check records |
| CC2 Communication and information (3) | Quality information, internal and external communication | Security policies published to staff, customer-facing security commitments, a way to report concerns | Policy acknowledgment logs, system description, published terms |
| CC3 Risk assessment (4) | Objectives, risk identification, fraud risk, change in risk | Annual risk assessment with a risk register | Dated risk register and approval |
| CC4 Monitoring activities (2) | Ongoing evaluations, communicating deficiencies | Internal control reviews, tracking of findings to closure | Review notes, remediation tickets |
| CC5 Control activities (3) | Selecting and deploying controls, technology controls, policies | Control matrix tied to risks, documented procedures | Control matrix, approved policies |
| CC6 Logical and physical access (8) | Access security, provisioning and removal, least privilege, physical access, disposal, external threats, data in transit, malware | SSO with MFA, quarterly access reviews, prompt offboarding, encryption, firewalls, endpoint protection | Access review sign-offs, offboarding tickets, MFA settings, encryption configs |
| CC7 System operations (5) | Vulnerability detection, monitoring anomalies, evaluating events, incident response, recovery | Vulnerability scanning, centralized logging and alerts, incident response plan and tabletop tests | Scan reports, alert samples, incident tickets, test records |
| CC8 Change management (1) | Changes are authorized, tested, approved and deployed in a controlled way | Pull requests with peer review, separate environments, change tickets | Sample of changes showing approval before deployment |
| CC9 Risk mitigation (2) | Business disruption risk, vendor and business partner risk | Business continuity plan, backups, vendor reviews | Backup restore tests, vendor SOC reports and review notes |
Several rows deserve a closer look:
- CC6 is the biggest series, with eight criteria. Access reviews and offboarding are where many teams hit their first exceptions.
- CC8 has only one criterion but plenty of samples. Every production change during the period can be tested, so the process has to hold up for urgent fixes as well.
- CC9.2 covers vendors. If you want a starting point for reviewing your own suppliers, our AI vendor questionnaire shows how to structure the questions, AI tools included.

Optional categories: what they add to the SOC 2 checklist
Every optional category adds its own criteria on top of the 33 common criteria:
- Availability (A1.1 to A1.3) addresses capacity planning, environmental protections, backups and recovery testing. Add it when you commit to uptime.
- Processing integrity (PI1 series) addresses whether processing is complete and accurate. It fits payroll, billing and data processing services where the output is the product.
- Confidentiality (C1 series) addresses identifying and protecting confidential information and disposing of it correctly. It’s common for companies holding customer contracts, financials or intellectual property.
- Privacy (P1 to P8) addresses notice, choice and consent, collection, use and retention, access, disclosure, quality and monitoring of personal information. It’s the largest category and takes the most effort.
Evidence checklist: what first-time teams forget
Most first audits stumble on evidence rather than missing controls. Add these items to your SOC 2 compliance checklist and make sure you can produce them on demand before the period begins:
- A current system description plus a network or data-flow diagram.
- An employee list showing hire dates, termination dates and roles.
- Proof of background checks and security awareness training for anyone hired during the period.
- Quarterly user access reviews for production systems, signed and dated.
- Offboarding records showing access was removed promptly after each departure.
- A sample of code changes, each approved before deployment.
- Vulnerability scan results and the tickets that resolved the findings.
- An incident log, even one showing no significant incidents, along with records of an incident response test.
- Backup configuration and at least one documented restore test.
- A vendor list with each critical vendor’s SOC report or review notes.
- Board or management minutes showing oversight of security.
What’s changing: the proposed 2027 Trust Services Criteria
Things are changing, and most checklists haven’t kept up. In October 2026, the AICPA’s SOC 2 Working Group published an exposure draft of revised Trust Services Criteria, according to the Journal of Accountancy. The main points:
- Comment deadline: January 15, 2027.
- Proposed effective date: engagements starting on or after December 31, 2027, with early adoption allowed.
- Structure: a targeted overhaul that merges duplicate concepts, drops some criteria and adds others where clarity is needed, according to CPA Practice Advisor.
- AI: new points of focus covering AI governance, model monitoring, prompt manipulation, data poisoning, transparency of AI-generated outputs, training data and automated decision-making.
Audit firms’ early readings of the draft suggest a much shorter common criteria list. Schellman’s analysis counts the common criteria dropping from 33 to 21, with control activities (CC5) eliminated as a separate series and change management absorbed into renumbered criteria. Other analyses count 20. The five categories don’t change.
What this means for your SOC 2 compliance checklist right now: nothing changes for audits beginning before the effective date. If your next audit period begins in 2028, plan to map your controls to the new structure during 2027. If your product uses AI, start documenting model monitoring and training data handling today, because customers are already asking about it.

Common SOC 2 compliance mistakes
- Scoping too broadly. Pulling every internal system into scope multiplies the evidence without helping customers.
- Using vendor policy templates without editing them. The auditor tests what the policy says, including promises you can’t keep.
- Starting a Type 2 period before controls settle. Exceptions from month one stay in the report.
- Mistaking automation for the control. A tool that flags a missed access review doesn’t perform the review; a person still has to do it.
- Overlooking people controls. Background checks, training and offboarding generate as many exceptions as technical controls do.
Our Take / Expert Perspective
Our take: the real question isn’t “how do we achieve SOC 2 compliance?” It’s “can we show our controls work every month without scrambling?” A first SOC 2 report mostly tests operational habits. Companies that pass cleanly usually have dull, owned routines: access reviews on the calendar, change approvals built into the pull request flow and an offboarding checklist that runs the same day someone leaves.
The proposed 2027 criteria will reinforce that. Fewer, clearer criteria leave less room to debate mapping, and the new AI points of focus mean customers will expect specific answers about model monitoring and training data. Forecast, not fact: within a year of the new criteria taking effect, AI controls will appear in most enterprise security questionnaires whether or not a company’s SOC 2 scope covers them.
Our recommendation: organize your SOC 2 compliance checklist around owners and frequencies rather than tools, and keep the criteria mapping in its own column. When the criteria change, you’ll remap one column instead of rebuilding the program.
Frequently Asked Questions
Is SOC 2 compliance required by law?
No. No federal or state law requires SOC 2 compliance. It’s a market requirement: customers, particularly larger companies, ask for a SOC 2 report in contracts and security reviews before sharing data with a vendor.
What are the SOC 2 compliance requirements?
The requirements are the AICPA’s Trust Services Criteria. Every report includes security, which means 33 common criteria across nine series. Availability, processing integrity, confidentiality or privacy criteria are added only if you pick those categories.
Do SOC 2 compliance requirements include specific controls like MFA or penetration testing?
The criteria don’t specify tools or tests. They set objectives, and you pick controls that meet them. In practice, MFA, encryption and vulnerability scanning are common ways to satisfy the access and system operations criteria.
Who can perform a SOC 2 audit?
Only an independent CPA firm can perform the examination and issue a SOC 2 report under AICPA standards. Compliance software vendors and consultants can help you get ready, but they can’t issue the report.
How is a SOC 2 checklist different for Type 1 and Type 2?
The SOC 2 checklist is mostly the same for both. A Type 1 checks that controls are designed properly as of a single date, so evidence is a point-in-time snapshot. A Type 2 also tests that they operated throughout a period, so you need recurring evidence for every month in the window.
Will the 2027 Trust Services Criteria change my current audit?
Not if your engagement starts before the effective date. The exposure draft proposes applying the revised criteria to engagements beginning on or after December 31, 2027, pending final approval, with early adoption allowed.
This article is for general information only and is not legal advice. Laws differ by state, province and country; consult a qualified attorney for your situation.
Sources
- AICPA & CIMA: 2017 Trust Services Criteria (with revised points of focus, 2022), checked November 7, 2026
- AICPA & CIMA: SOC services overview, checked November 7, 2026
- Journal of Accountancy: AICPA proposes improvements to SOC 2 trust services criteria, checked November 7, 2026
- CPA Practice Advisor: AICPA proposes update of SOC 2 Trust Services Criteria, checked November 7, 2026
- Schellman: SOC 2 is getting an update, checked November 7, 2026
- Bright Defense: AICPA’s SOC 2 proposal cuts criteria and expands AI coverage, checked November 7, 2026
- aiandblog: SOC 2 Type 1 vs Type 2 and AI vendor questionnaire
- aiandblog: more Security Compliance articles and our Editorial Policy
Photos: Taylor Vick, Kevin Ache and Christina @ wocintechchat.com on Unsplash.










Leave a Reply