SOC 2 Readiness Assessment: Free Checklist Mapped to the Trust Services Criteria
Last updated: 2026-10-07
Choose your scope, then answer 32 plain-language checks. Each shows the criteria it usually supports and the evidence auditors commonly ask for. Only the categories you select are counted, and your answers stay in this browser.
1. Which Trust Services Criteria will be in scope?
Security is in every SOC 2. Add others only if your commitments to customers cover them — each adds criteria the auditor must test.
Security (Common Criteria) (CC1–CC9) 0/21
Someone (owner, board or exec) formally oversees security, and roles and reporting lines are documented.
CC1.1–CC1.3 · Evidence auditors usually ask for: Org chart, named security owner, management meeting notes covering security
New hires sign a code of conduct/acceptable use policy, and you screen people before giving them access to sensitive systems.
CC1.1, CC1.4 · Evidence auditors usually ask for: Signed acknowledgments, background-check records (where lawful)
Everyone completes security awareness training at hire and at least yearly.
CC1.4, CC2.2 · Evidence auditors usually ask for: Training completion records with dates
Written, approved information-security policies exist and staff can find them.
CC2.2, CC5.3 · Evidence auditors usually ask for: Policy set with approval dates and version history
You can describe your system: services in scope, infrastructure, software, people, data flows, and the vendors (subservice organizations) you rely on.
CC2.3 + description criteria · Evidence auditors usually ask for: Draft system description, architecture/data-flow diagram, vendor list
Your security commitments to customers (contract terms, SLAs, how to report issues) are written and communicated.
CC2.3 · Evidence auditors usually ask for: MSA/terms, SLA page, security contact or trust page
You perform and document a risk assessment at least yearly, including fraud risk and significant changes.
CC3.1–CC3.4 · Evidence auditors usually ask for: Risk register with likelihood/impact, owners and treatment decisions
You periodically check that controls actually work and track deficiencies to closure.
CC4.1–CC4.2 · Evidence auditors usually ask for: Internal control reviews, scan results, issue tracker with remediation
You keep an inventory of in-scope systems, endpoints and data stores.
CC6.1 · Evidence auditors usually ask for: Asset inventory (cloud accounts, servers, laptops, SaaS)
Unique accounts and MFA (ideally SSO) protect production, cloud consoles, code repositories and email.
CC6.1 · Evidence auditors usually ask for: IdP/MFA configuration screenshots, list of admin accounts
Access is approved before it's granted and removed promptly when people leave or change roles.
CC6.2–CC6.3 · Evidence auditors usually ask for: Access request tickets, offboarding checklists with dates
You review user access to critical systems on a schedule (e.g., quarterly) and fix what you find.
CC6.2–CC6.3 · Evidence auditors usually ask for: Signed-off access review exports
Customer data is encrypted in transit (TLS) and at rest.
CC6.1, CC6.7 · Evidence auditors usually ask for: TLS configuration, storage/database encryption settings, key management
Network boundaries are restricted (firewalls/security groups) and endpoints have anti-malware and disk encryption.
CC6.6, CC6.8 · Evidence auditors usually ask for: Security group rules, MDM/EDR reports
Physical access to offices/equipment is controlled, and you rely on your cloud provider's SOC report for data-center controls.
CC6.4–CC6.5 · Evidence auditors usually ask for: Badge/visitor process, cloud provider SOC 2 report on file
You scan for vulnerabilities and patch on a defined timeline.
CC7.1 · Evidence auditors usually ask for: Scanner reports, patch SLAs, remediation tickets
Security-relevant logs are collected and someone is alerted to suspicious activity.
CC7.2 · Evidence auditors usually ask for: Log retention settings, alert rules, on-call evidence
You have an incident response plan, have tested it (tabletop), and record incidents and lessons learned.
CC7.3–CC7.5 · Evidence auditors usually ask for: IR plan, tabletop notes, incident log
Changes to production are reviewed, tested and approved before release; developers can't push unreviewed code.
CC8.1 · Evidence auditors usually ask for: Branch protection, pull-request approvals, deployment logs
You keep a vendor list and assess critical vendors (e.g., review their SOC 2 reports) before and during the relationship.
CC9.2 · Evidence auditors usually ask for: Vendor inventory, risk ratings, reviewed vendor reports
You've planned how the business keeps running through disruptions (and considered cyber insurance).
CC9.1 · Evidence auditors usually ask for: Business continuity plan, insurance documentation
What each category covers
| Category | Criteria | Our checks | Covers |
|---|---|---|---|
| Security (Common Criteria) CC1–CC9 | 33 | 21 | Control environment, communication, risk assessment, monitoring, control activities, logical and physical access, system operations, change management, risk mitigation (incl. vendors). |
| Availability A1.1–A1.3 | 3 | 2 | Capacity planning, backups, environmental protections, recovery and recovery testing. |
| Confidentiality C1.1–C1.2 | 2 | 2 | Identifying, protecting, retaining and disposing of information designated confidential. |
| Processing Integrity PI1.1–PI1.5 | 5 | 2 | Complete, valid, accurate, timely and authorized processing — inputs, processing, outputs, stored data. |
| Privacy P1–P8 | 18 | 5 | Notice, choice and consent, collection, use/retention/disposal, access, disclosure and notification, quality, monitoring and enforcement. |
Our checks are a practical subset written in plain language, not the AICPA's text; download the criteria themselves from the AICPA. source
From checklist to report
- Export the gap register and give each gap an owner and date.
- Budget the work and the audit with the cost builder.
- Draft your system description (services, infrastructure, software, people, data, subservice organizations).
- Choose Type 1 or Type 2 and plan dates with the timeline planner.
- Engage a licensed CPA firm — see how to vet one.
Frequently Asked Questions
›What is a SOC 2 readiness assessment?
A review of your controls against the Trust Services Criteria before the real examination, to find gaps while there's still time to fix them. It can be done internally (like this checklist) or by a consultant. If your future auditor does a readiness review, AICPA independence rules limit them to identifying gaps — not designing or running your controls.
›Which Trust Services Criteria should I include?
Security is always included. Add Availability if you commit to uptime or recovery targets, Confidentiality if you promise to protect designated confidential information, Processing Integrity if customers rely on your processing being complete and accurate, and Privacy if you collect personal information under privacy commitments. Each category adds criteria the auditor must test.
›Does a high score mean I'll pass?
There's no pass/fail in SOC 2, and this checklist can't predict the CPA firm's opinion. It tells you which common controls and evidence are missing. The auditor tests the controls you describe, on your evidence.
›What are the most common gaps for small companies?
In our checklist the hardest items tend to be security monitoring and alerting, a documented risk assessment, regular access reviews, change-management evidence and vendor reviews — controls that need a repeatable process and records, not just a policy.
›What should I do after the checklist?
Assign owners and dates to each gap (the Excel export has columns for this), write your system description, and collect quotes from licensed CPA firms. For a Type 2, start the observation period only once controls are operating.
Related tools & guides
Official Sources
Figures checked against these sources on 2026-10-07- AICPA: 2017 Trust Services Criteria (revised points of focus, 2022)
- AICPA & CIMA: SOC 2 — SOC for Service Organizations
- Journal of Accountancy: Promises of 'fast and easy' threaten SOC credibility (Feb 2026) — AICPA SOC 2 Working Group's checklist for vetting a SOC 2 firm
Related Resources on This Site
Helpful guides
- CertificationMBE/WBE/MWBE certification guide
- Workers' Compworkers compensation insurance by state
- General Liabilitygeneral liability insurance
- Commercial Autocommercial auto insurance
A self-check, not an audit opinion. Only a licensed CPA firm can issue a SOC 2 report.