
A SOC 2 compliance checklist starts with the security criteria every report covers, the common criteria CC1 to CC9, then adds availability, confidentiality, processing integrity or privacy only if customers need them. For a small company the core is MFA, endpoint protection, logging, access reviews, change control, vendor reviews, incident response, tested backups and proof of each.
This is the checklist we work from in our SOC 2 readiness services, organized the way the AICPA organizes the criteria. If you have not chosen a report yet, read SOC 2 Type 1 vs Type 2 first, and for budgeting, see our SOC 2 audit cost guide.
What are the SOC 2 requirements?
SOC 2 has no fixed control list. Its requirements are the AICPA's 2017 Trust Services Criteria, with points of focus revised in 2022, and the AICPA calls them outcome-based: they describe what your controls must achieve, not which tools to buy. The criteria fall into two groups:
- Common criteria, CC1 to CC9. CC1 to CC5 carry the 17 principles of the COSO internal control framework, grouped as control environment, communication and information, risk assessment, monitoring activities and control activities. CC6 to CC9 add logical and physical access, system operations, change management and risk mitigation. On their own, the common criteria are the complete set for security.
- Additional criteria. Availability (A1), confidentiality (C1), processing integrity (PI1) and privacy (P1 to P8) each add criteria on top of the common criteria.
Each criterion comes with points of focus, but the AICPA says using the criteria does not require an assessment of whether each point of focus is addressed, and some may not suit your company at all. Treat them as prompts, not as the checklist.
Which Trust Services Criteria apply to your company?
| Category | Criteria | Include it when |
|---|---|---|
| Security | CC1 to CC9 | Always: every SOC 2 report covers the common criteria |
| Availability | A1.1 to A1.3 | Customers depend on your uptime, or you commit to service levels |
| Confidentiality | C1.1 and C1.2 | You hold customer information that contracts say to protect and later delete |
| Processing integrity | PI1.1 to PI1.5 | Customers rely on your processing being complete, accurate and timely, as with billing or payments |
| Privacy | P1 to P8 | You collect personal information from individuals and make commitments about how you handle it |
A smaller scope is cheaper and still credible. Add a category because a customer asked for it, not because it looks thorough.
What does the SOC 2 checklist include for the security criteria?
These are the controls we expect a small company to run for each part of the common criteria, and the evidence auditors commonly request. The criterion numbers are the AICPA's.
| Criteria | Control for a small company | Evidence to keep |
|---|---|---|
| CC1: control environment | A code of conduct, a named security owner, background checks at hire, and security training at onboarding and every year | Signed acknowledgments, org chart, role descriptions, training completion records |
| CC2: communication and information | Approved security policies, a written system description, and a way for staff and customers to report security problems | Policies with approval dates, staff acknowledgments, the system description |
| CC3: risk assessment | A yearly risk assessment that considers fraud and major changes to the business | A dated risk register with owners and decisions |
| CC4: monitoring activities | Periodic control reviews, vulnerability scans and a penetration test, with findings tracked to closure | Review notes, scan and test reports, remediation tickets |
| CC5: control activities | A written procedure and a named owner for every control | A control matrix mapping each control to its criteria and owner |
| CC6.1: logical access | Multi-factor authentication on every account, single sign-on and Conditional Access | MFA enforcement report, sign-in policy export |
| CC6.2 and CC6.3: user access | Joiner, mover and leaver steps tied to HR, least privilege, and quarterly access reviews | Onboarding and offboarding tickets matched to HR dates, signed access reviews |
| CC6.4 and CC6.5: physical access and disposal | Restricted access to the office and equipment, and devices wiped before reuse or disposal | Access lists, disposal certificates |
| CC6.6 to CC6.8: network, data in transit and malware | A firewall, email filtering, encryption in transit and at rest, and endpoint detection and response on every device | Firewall rule review, disk encryption report, EDR coverage report |
| CC7.1: vulnerabilities and configuration | Patching on a schedule and baseline configurations for devices and servers | Patch compliance reports, scan results with fix dates |
| CC7.2 and CC7.3: monitoring | Central logs, alerts that someone reviews, and suspicious events triaged | Alert tickets, log retention settings, monitoring reports |
| CC7.4 and CC7.5: incident response and recovery | A written incident response plan, tested with a tabletop exercise, and a recovery procedure | The plan, the tabletop record, the incident log and post-incident reviews |
| CC8.1: change management | Changes requested, tested and approved before release | Sample change tickets with approvals and test notes |
| CC9.1 and CC9.2: risk mitigation and vendors | Business continuity planning, insurance considered for financial loss, and a vendor inventory reviewed every year | The continuity plan, a vendor list with risk ratings, vendor reports reviewed |
Some controls serve several criteria. Security awareness training supports CC1.4, which covers developing competent people, and CC2.2, which covers communicating security information internally. Tested backups support recovery under CC7.5 and the availability criteria below. Our vendor risk management guide goes deeper on CC9.2, and our incident response plan steps cover CC7.4.
What do the other Trust Services Criteria add?
| Category | What it adds | Evidence to keep |
|---|---|---|
| Availability (A1.1 to A1.3) | Capacity monitoring, backups and recovery infrastructure, and testing of recovery plan procedures | Capacity reports, backup job logs, restore test results with dates and measured times |
| Confidentiality (C1.1 and C1.2) | Identifying confidential information and disposing of it when it is no longer needed | A data inventory, a retention schedule, deletion records |
| Processing integrity (PI1.1 to PI1.5) | Defined processing specifications, plus controls over inputs, processing, outputs and stored data so results are complete, accurate and timely | Specifications, validation checks, reconciliations, error logs |
| Privacy (P1 to P8) | Notice, choice and consent, collection, use, retention and disposal, access, disclosure and notification, quality, and monitoring and enforcement | The privacy notice, consent records, a log of individuals' requests |
Which SOC 2 policies do you need?
The criteria call for written policies in several places but name no list. This is the set we usually write for a small company, each tied to the criteria it supports:
| Policy | What it covers | Criteria it supports |
|---|---|---|
| Information security policy | The security owner, acceptable use, data classification and how staff report problems | CC1, CC2 and CC5 |
| Risk assessment policy | The yearly risk assessment, including fraud and major business changes, and who signs off on decisions | CC3 |
| Access control policy | Joiners, movers and leavers, MFA, least privilege and quarterly access reviews | CC6 |
| Change management policy | How changes are requested, tested, approved and released | CC8 |
| Incident response plan | Detection, triage, communication, recovery and the review after each incident | CC7.3 to CC7.5 |
| Vendor management policy | The vendor inventory, risk ratings and yearly reviews | CC9.2 |
| Business continuity and disaster recovery plan | Backups, recovery order, restore tests and who decides during an outage | CC7.5, CC9.1 and, if in scope, A1 |
| Data retention and disposal policy | How long each kind of data is kept and how it is deleted | C1, if confidentiality is in scope |
A policy template saves typing, not work. Rewrite each one to describe what your team actually does, have staff acknowledge it, and keep the approval date, because the auditor tests the policy against your records.
What evidence will the auditor ask for?
For a Type 1, the auditor looks at whether each control is suitably designed as of the report date, so policies, configurations and procedures carry most of the weight. For a Type 2, the auditor also tests whether controls operated across the period, so you need records from throughout it: access reviews from each quarter, change tickets from different months, restore tests on the dates your schedule promised. Three habits make that easy:
- Keep an evidence calendar that names who produces each record and when.
- Export reports straight from the systems that run the controls, with dates visible, instead of rebuilding them later.
- Store final versions only. A draft policy or an undated screenshot proves little.
Is there a SOC 2 compliance checklist in Excel?
Yes. Download the SOC 2 evidence-owner checklist (Excel, .xlsx). It has one row for every criterion in the 2017 Trust Services Criteria: the 33 common criteria, CC1 to CC9, marked in scope, plus the availability, confidentiality, processing integrity and privacy criteria for you to mark in or out. Each row has columns for applicability, control owner, evidence owner, your control in your own words, the evidence to collect and where it lives, frequency, due date, status and exceptions.
How to use this file. Set applicability first, because every added category adds controls and audit fees. Then name two people per row: the control owner who runs the activity and the evidence owner who can produce the record. Set a due date for the next piece of evidence and track status from the list. The Summary sheet counts rows by status, and that count measures your own readiness work: it is not an audit opinion, not a SOC 2 report and not a pass. Only an independent CPA firm's examination produces a SOC 2 report. The criterion summaries in the file are our short paraphrases; the AICPA's 2017 Trust Services Criteria with revised points of focus (2022) are the authority, checked on November 7, 2026.
How do you work through the SOC 2 checklist?
We run the work in nine steps:
- Scope the system. Choose the services, systems, people and vendors the report will cover, and the Trust Services Criteria your customers need beyond security.
- Run a gap assessment. Compare your current controls with each criterion in scope and turn every gap into a dated task with an owner.
- Write the policies. Write the security, access, change, incident, vendor and continuity policies your team will follow, and have staff acknowledge them.
- Implement the controls. Configure MFA, device management, endpoint protection, logging, backups and the other controls the gap list calls for.
- Collect evidence on a schedule. Keep an evidence calendar so access reviews, scans, restore tests and change records are produced and stored on time.
- Choose an independent CPA firm. Engage a licensed CPA firm that did not build your controls, and agree on the scope, criteria and timing.
- Get a Type 1 report if you need one soon. If a customer needs a report quickly, the CPA firm examines the design of your controls as of a date.
- Run the observation period. Operate every control through the agreed period and keep the records, because the auditor samples across it.
- Complete the Type 2 examination. The CPA firm tests the controls, you answer its requests from the evidence library, and the firm issues the report.
The AICPA notes that a CPA firm that designs or implements an attest client's systems can face threats to its independence, which is why step six names a firm that did not build your controls. We handle steps one to five and support the rest, starting with a free remote external penetration test within an agreed scope. For managed clients we already run many of the controls in Microsoft 365, Entra ID and Intune, so the evidence comes from systems we operate every day.
Give every readiness item an evidence owner
Use the checklist above to define the work, then assign who operates each control and who can provide evidence. Agree the system boundary and examination scope with the appropriate advisers and auditor. A readiness spreadsheet should support that process, not imply that checking every row produces a SOC 2 report.
| Readiness field | What to record |
|---|---|
| Control and scope | The actual process, systems and people covered |
| Operating owner | Who performs the activity and handles exceptions |
| Evidence source | The system or record that demonstrates performance |
| Period and reviewer | Which dates matter and who checks completeness |
| Gap and action | What is missing, who will fix it and how it will be validated |
For an illustrative access-review control, evidence might include the approved population, the owner's decisions and proof that removals were completed. A policy saying reviews occur does not, by itself, show that a particular review happened. Preserve the actual record and investigate gaps rather than constructing retrospective evidence that misrepresents events.
Keep evidence in an approved location with appropriate access. Ask the auditor what form and period are relevant to the engagement instead of exporting every available record. Track requests and unresolved items so the same issue is not answered differently by multiple teams.
AICPA's SOC resources describe the examination framework. NetSys's SOC 2 readiness service focuses on scope preparation, technical remediation and evidence organization; the independent CPA examination remains a separate role. The handoff should make that division explicit.
Frequently asked questions
Is there an official SOC 2 checklist?
No. The AICPA publishes the Trust Services Criteria, which are outcome-based, and leaves the controls to each company. Its points of focus describe characteristics of each criterion but are not required items. A checklist like the one above translates the criteria into controls and evidence for a typical small company; your scope may need more or less. The criteria themselves are a downloadable PDF on the AICPA's site, the tables on this page print cleanly as a working controls list, and the Excel evidence-owner checklist above is the editable version.
Are SOC 2 Type 2 requirements different from Type 1?
The criteria and the controls are the same. A Type 2 adds time: the auditor tests whether each control operated throughout the observation period, so you need records from across it, such as access reviews from every quarter and change tickets from different months. A control that existed on paper but skipped a quarter shows up as an exception in a Type 2.
Is there a SOC 2 certification?
Not in the formal sense. A SOC 2 is an attestation report from a licensed CPA firm, not a certificate, and it describes a date or a period rather than granting a status. People say certified loosely; our guide to SOC 2 compliance for small business covers what customers mean when they ask for it, and our SOC 1 vs SOC 2 guide covers which report to get. A customer that wants a certificate may be asking for ISO 27001, which our ISO 27001 vs SOC 2 comparison sets side by side.
What does a SOC 2 readiness assessment check?
It compares your current controls with each criterion in scope. It covers the scope and system description, the controls you run today, the evidence you can already produce, and it ends with a dated remediation list with a named owner for every gap. It prepares you for the audit; it is not the audit.
How does a SOC 2 project start with NetSys?
With our free remote external penetration test within an agreed scope, then a scoping session that settles which criteria and systems belong in the report, then the gap assessment. Remediation, the policy set and the evidence calendar follow. We deliver readiness remotely to companies anywhere in the U.S. and on site in our coverage areas, month to month.
What affects the cost of SOC 2 compliance?
Scope, more than anything: the criteria and systems in the report, how mature your controls already are, how much evidence exports automatically, and the length of the observation period. Readiness work, technical fixes, optional compliance software and the CPA firm's examination are four separate budget lines, and our SOC 2 audit cost guide breaks each one down.
Who answers the auditor's requests during the audit?
The control owners, with help. Each control has a named owner who answers for it, and we answer the auditor's request list from the evidence library, with our engineers on the calls. If the auditor finds an exception, it goes to that control's owner with a fix and a date, and the fix is tracked like any other remediation item.
Do we need every Trust Services Criteria category?
No. Every SOC 2 covers the common criteria, which are the security category. Availability, confidentiality, processing integrity and privacy are optional and should be added only when customers need them, because each adds controls, evidence and audit fees.
What tools does SOC 2 require?
None by name. The criteria describe what controls must achieve, such as restricting logical access or detecting malicious software, so you can meet them with the tools you already run. A typical small company uses its identity provider, device management, endpoint protection, a logging platform and a ticketing system, plus a compliance platform if they want help tracking evidence.
Can a small company with no IT staff get SOC 2 ready?
Yes, with an outside provider running the controls and a named owner inside the company for the decisions only the business can make, such as who gets access and which vendors are approved. The provider builds and operates the controls; an independent CPA firm audits them.
Sources and further reading
- AICPA: 2017 Trust Services Criteria, with revised points of focus (2022): the common and additional criteria, the role of points of focus and the independence note, checked on November 7, 2026.
- AICPA: Mappings relevant to the trust services criteria: the criteria described as outcome-based, checked October 2026.
- AICPA Guide: SOC 2 Reporting on an Examination of Controls at a Service Organization: what a SOC 2 examination covers, checked October 2026.
- AICPA & CIMA: SOC suite of services, checked October 2026.
Discuss soc 2 readiness services for your business.
Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.


