If you sell software or cloud services to businesses, sooner or later a prospect's security team will ask: "Do you have a SOC 2 report?" For many B2B companies, that question decides whether a deal moves forward or stalls in procurement for months.

SOC 2 can feel intimidating the first time. The terminology is unfamiliar, the framework is flexible rather than prescriptive, and there is no official checklist to tick. The good news is that the process is predictable once you understand its parts, and modern cloud tooling makes most of the evidence collection automatic.

2026 is also a turning point. In late October the AICPA published an exposure draft of revised SOC 2 Trust Services Criteria that restructures the criteria and adds new guidance for AI systems. Starting your SOC 2 journey now means building controls that will hold up under both today's criteria and tomorrow's.

This guide explains what SOC 2 is, what auditors look for, the step-by-step audit process, realistic timelines, the latest tools and trends, best practices and answers to the questions first-time teams ask most.

What is SOC 2?

SOC 2 (System and Organization Controls 2) is an attestation framework created by the American Institute of Certified Public Accountants as part of its SOC suite of services. An independent CPA firm examines how your organisation protects customer data and issues a report on whether your controls are suitably designed and, for Type II, operating effectively.

SOC 2 is not a certification you "pass" once. It is an opinion from an auditor, renewed every year, that customers and their auditors can rely on.

The five Trust Services Criteria

Every SOC 2 audit is scoped against the AICPA's Trust Services Criteria (TSC):

CriterionRequired?What it covers
SecurityAlwaysProtection against unauthorised access, also called the Common Criteria
AvailabilityOptionalUptime, capacity, backups and disaster recovery
Processing IntegrityOptionalComplete, accurate and timely data processing
ConfidentialityOptionalProtection of sensitive business information
PrivacyOptionalCollection, use and disposal of personal information

Most first-time SaaS audits cover Security, often with Availability and Confidentiality added because customers ask for them.

SOC 2 Type I vs Type II

 Type IType II
What it testsControl design at a single point in timeDesign and operating effectiveness over a period
Observation periodNoneUsually 3 to 12 months
Typical useA fast first report to unblock early dealsWhat most enterprise customers expect

Many startups get a Type I first, then move straight into a Type II observation window.

Who needs SOC 2?

SOC 2 matters most for SaaS providers, cloud and managed service providers, fintech, healthtech, data and AI platforms, and any vendor that stores or processes customer data. It is a market expectation rather than a law, especially for companies selling to US enterprises.

SOC 2 requirements and common controls

SOC 2 doesn't hand you a fixed control list. Instead, you design controls that meet each criterion, and the auditor tests them. In practice, most cloud-native companies implement a similar core set.

Control areaTypical controlsExample evidence
Governance and riskSecurity policies, annual risk assessment, vendor reviewsApproved policies, risk register
Access controlSSO, MFA, least privilege, quarterly access reviewsIdP configuration, review sign-offs
Change managementPull requests, peer review, CI/CD with approvalsMerge request history, pipeline logs
Infrastructure securityEncryption at rest and in transit, network segmentation, hardened imagesCloud configuration snapshots
Vulnerability managementScanning, patching SLAs, annual penetration testScan reports, pentest report
Monitoring and incident responseCentralised logging, alerting, incident runbooksAlert history, post-incident reviews
AvailabilityBackups, restore tests, disaster recovery planBackup logs, DR test results
PeopleBackground checks, security training, onboarding and offboardingTraining records, HR tickets

If your platform runs on AWS, Azure or Google Cloud, a large share of these controls live in your infrastructure. That is why a strong cloud security foundation and secure delivery pipelines make SOC 2 far easier. Our DevSecOps consulting team builds these controls directly into CI/CD, so evidence is produced on every change.

For penetration testing, which nearly every auditor expects, see our VAPT services. The CIS Benchmarks are also a practical baseline for hardening cloud accounts and servers.

The SOC 2 audit process, step by step

A first SOC 2 follows the same seven steps for almost every company.

SOC 2 Audit Process in 7 steps
  1. Define scope and objectives. Decide which products, systems, locations and teams are in scope, and which Trust Services Criteria to include. Keep the first scope tight: your production SaaS platform and the people who support it.
  2. Run a gap assessment. Compare current practices against the criteria and list missing or weak controls. Many teams use a compliance platform or an advisor for this step.
  3. Remediate gaps. Write policies, enable MFA and SSO everywhere, tighten IAM, turn on logging and encryption, formalise change management and set up vendor reviews.
  4. Choose an auditor. Only a licensed CPA firm can issue a SOC 2 report. Compare firms on SaaS experience, communication style and how well they work with your tooling.
  5. Optional readiness assessment. A pre-audit review by your auditor or advisor catches surprises before the clock starts.
  6. Run the audit. For Type I, the auditor tests control design at one date. For Type II, controls must operate throughout the observation window, after which the auditor samples evidence such as access reviews, change tickets and alerts.
  7. Receive the report and maintain. You'll get a report with the auditor's opinion, your system description and any exceptions. Then keep controls running for next year's audit.

Your system description matters

The report includes a narrative description of your system: services, infrastructure, software, people, data and processes. Write it early, keep it accurate and make sure your architecture diagrams match reality. Auditors test against what you describe.

How long a SOC 2 audit takes, and what drives cost

PhaseTypical duration
Gap assessment and remediation1 to 3 months
Type I audit2 to 6 weeks of fieldwork
Type II observation window3 to 12 months (3 to 6 is common for a first report)
Report issuance after fieldwork2 to 6 weeks

A realistic first Type II takes six to twelve months from kickoff to report. Cost depends less on company size than on these factors:

  • Scope: each extra criterion, product or region adds testing.
  • Maturity: teams with infrastructure as code, SSO and automated logging remediate faster.
  • Auditor choice: large firms charge more, and fees vary widely.
  • Tooling: compliance platforms, scanners and penetration tests add licence costs but save engineering time.
  • Internal effort: engineering, security and HR hours are often the biggest hidden cost.

Latest SOC 2 trends and tools in 2026

Proposed 2027 Trust Services Criteria

The AICPA's exposure draft, released in late October 2026, is the biggest change to SOC 2 in years. According to an analysis by Bright Defense, the total criteria would drop from 61 to 50, and the common criteria would be regrouped from CC1–CC9 into CC1–CC8. Public comments are due January 15, 2027, and if approved the new criteria would apply to engagements beginning on or after December 31, 2027, with early adoption allowed. Your current audit still uses the existing criteria, but designing controls with the new structure in mind avoids rework later.

AI governance enters SOC 2

The same proposal adds points of focus on AI governance, model monitoring, prompt manipulation, data poisoning, training data management and transparency of AI-generated output. If your product uses large language models or AI agents, expect auditors to ask how you test, monitor and control them. Many AI vendors now pair SOC 2 with ISO/IEC 42001, the AI management system standard.

Compliance automation and continuous monitoring

Platforms such as Vanta, Drata and Secureframe connect to your cloud, identity provider, code repositories and HR system to collect evidence continuously and flag drifting controls. Cloud-native tools such as AWS Security Hub and Audit Manager help too. SquareOps' own Verity platform runs continuous posture checks across cloud accounts and gathers the evidence auditors request.

Policy as code and public trust centers

Teams increasingly enforce controls as code, blocking non-compliant infrastructure before it is deployed; see our guide to policy as code with Open Policy Agent. On the sales side, public trust centers let prospects request your SOC 2 report under NDA without lengthy email threads.

SOC 2 best practices and common mistakes

Best practices

  • Start with security basics. SSO, MFA, least-privilege IAM, encryption and logging satisfy a large share of the criteria.
  • Automate evidence. Infrastructure as code, CI/CD approvals and centralised logs create audit trails without screenshots.
  • Assign owners. Every control needs a named person and a review cadence.
  • Write policies you actually follow. Auditors test reality against your documents; ambitious policies you ignore become exceptions.
  • Treat it as continuous. Run quarterly access reviews and annual risk assessments on schedule, not the week before fieldwork.
  • Mind your vendors. Collect SOC 2 reports from critical subprocessors and review their complementary user entity controls.

Common mistakes

  • Scoping too broadly for a first audit.
  • Leaving offboarding manual, so former employees keep access.
  • Starting a Type II window before controls are actually in place.
  • Treating SOC 2 as a one-off project, then scrambling a year later.

Conclusion

SOC 2 is far less mysterious than it first appears. Define a tight scope, close the gaps, pick a good auditor, and let automation produce evidence as a by-product of how you already build and run software. Done well, SOC 2 shortens sales cycles and leaves your platform genuinely more secure.

With the AICPA's proposed 2027 criteria adding AI governance and continuous monitoring becoming the norm, the best time to build durable controls is now. For a wider view of the tooling landscape, read our roundup of the top cloud security providers and solutions in 2026.

Preparing for your first SOC 2 audit? Talk to the SquareOps team about cloud security, compliance automation and audit-ready infrastructure from an ISO 27001-certified partner.