| TSC Category | Example Controls | Evidence |
|---|
| CC1 Control Environment | Code of Conduct, background checks, security awareness training | Training completion logs, signed policy acknowledgments |
| CC2 Communication | Security policies published to staff, customer commitments | Policy distribution records, customer-facing documentation |
| CC3 Risk Assessment | Annual risk assessment, vendor risk reviews | Risk register, vendor assessment records |
| CC4 Monitoring | Internal control evaluations, management review | Management review minutes, control test results |
| CC5 Control Activities | SOD, change management | Change tickets, approvals, segregation matrix |
| CC6 Logical Access | MFA, access reviews, provisioning/deprovisioning | Access review logs, MFA enforcement reports, joiner/mover/leaver tickets |
| CC7 System Operations | Vulnerability management, incident response, monitoring | Scan reports, IR logs, SOC reports |
| CC8 Change Management | Code review, deployment approvals, rollback procedures | Pull request reviews, deployment logs |
| CC9 Risk Mitigation | Vendor risk management, BCP/DR | Vendor assessments, DR test results |
Source: AICPA Trust Services Criteria, 2026.
Selecting the right auditor
Auditor independence rules require your readiness consultant and your auditor to be separate firms. Mid-tier CPA firms licensed in your state with a SOC 2 practice are the sweet spot for most non-public companies. Look for firms with industry experience and a published methodology. AICPA maintains a list of member firms; Schellman, A-LIGN, Coalfire ISO, Linford & Co, Sensiba, and KirkpatrickPrice are common choices.
How to reduce SOC 2 audit duration and cost
Three levers compress SOC 2 prep: automation, scoped TSCs, and pre-built policy templates. Automation platforms like Vanta, Drata, Secureframe, and Tugboat Logic integrate with AWS, Azure, GCP, GitHub, Okta, Entra ID, Slack, and Jira to automate 40 to 60 percent of evidence collection. Limit TSCs to Security plus whatever is contractually required. Adopt policy templates from your automation vendor or auditor and customize rather than authoring from scratch.
Internal links
See related compliance guides: SOC 2 compliance cost, ISO 27001 SoA template, and HIPAA risk assessment template.
FAQs
See FAQ section above for SOC 2 audit prep timeline, Type I vs Type II, TSC scoping, auditor selection, and common failure points.
SOC 2 readiness assessment methodology
The readiness assessment is the foundation of a successful SOC 2 audit. A proper readiness assessment compares current state to AICPA Trust Services Criteria requirements and identifies remediation scope before the formal audit begins.
| Readiness Phase | Activities | Deliverables |
|---|
| Scope definition | System boundaries, services, TSC selection | Scope statement document |
| Current state assessment | Gap analysis vs TSC requirements | Gap analysis report |
| Remediation planning | Prioritize gaps, assign owners, set timelines | Remediation roadmap |
| Evidence collection | Baseline policies, procedures, screenshots | Evidence repository |
| Pre-audit testing | Internal control testing | Pre-audit report |
Source: Schellman SOC 2 readiness methodology and AICPA guidance, 2026.
FAQ expansion
Q: Should I hire a separate readiness consultant from my auditor? Yes. AICPA independence rules require that the firm conducting your SOC 2 audit cannot also provide certain non-audit services. Most auditors cannot also do readiness assessments for the same engagement. Use separate firms for readiness and audit to maintain independence.
Q: What is the difference between Type I and Type II observation windows? Type I observation is at a point in time. Type II observation is over a period, typically 3 to 12 months. The longer the observation window, the more rigorous the audit and the more confidence customers have in the report. Most enterprises target a 12-month observation window for Type II.
Q: How long are SOC 2 reports valid? SOC 2 Type II reports cover a specific period (typically 6 or 12 months). Reports are commonly accepted by customers for 12 months from issuance, after which a new report is needed. Type I reports are point-in-time and valid until the controls change materially.