Skip to main content
SOC 2 Framework

SOC 2 Compliance

The security audit standard for SaaS and cloud service providers. AICPA's Trust Services Criteria framework — available on the Ultimate plan.

The security audit standard
enterprise customers require

SOC 2 (System and Organization Controls 2) is an auditing framework developed by the AICPA (American Institute of Certified Public Accountants). It verifies that a service organization has appropriate controls in place to protect customer data across five Trust Services Criteria: Security, Availability, Processing Integrity, Confidentiality, and Privacy.

Most enterprise customers in the US require a SOC 2 Type II report from their SaaS vendors before signing contracts. For B2B SaaS companies, SOC 2 certification is increasingly the difference between winning and losing enterprise deals.

Unlike ISO 27001, SOC 2 has no prescriptive control list — the auditor evaluates whether your controls *effectively* meet the Trust Services Criteria. This makes preparation more nuanced, and evidence collection more critical.

SOC 2 Type I vs Type II

Type I assesses whether controls are *designed* appropriately at a point in time — faster but less credible. Type II assesses whether controls *operated effectively* over a 6–12 month period — the gold standard for enterprise customers.

Who needs SOC 2?

SaaS companies, cloud service providers, data centers, managed security providers, and any B2B software company whose customers store sensitive data on their platform. If your enterprise customers are asking for it, you need it.

How long does SOC 2 take?

Type I: 2–5 months from starting readiness work. Type II: 8–14 months total (3 months prep + 6–12 month observation period + 1–2 month audit). Starting with automated evidence collection significantly reduces prep time.

The five SOC 2 Trust Services Criteria

All SOC 2 reports must include Common Criteria (Security). Additional criteria are selected based on your service's commitments to customers.

CC
Required

Common Criteria (CC)

33 criteria

Required for all SOC 2 reports. Covers security across organization, communication, risk management, monitoring, logical access, system operations, and change management.

A

Availability (A)

3 criteria

The system is available for operation and use as committed or agreed. Covers uptime, performance monitoring, incident response, and disaster recovery.

PI

Processing Integrity (PI)

5 criteria

System processing is complete, valid, accurate, timely, and authorized. Relevant for financial processing, payroll, and transaction-intensive systems.

C

Confidentiality (C)

2 criteria

Information designated as confidential is protected as committed or agreed. Critical for B2B platforms handling customer intellectual property or trade secrets.

P

Privacy (P)

9 criteria

Personal information is collected, used, retained, disclosed, and disposed of in conformity with the entity's privacy commitments and criteria.

SOC 2 compliance checklist
for startups and SaaS companies

This checklist covers the most common SOC 2 Common Criteria requirements. Use it to assess your current readiness before starting a formal SOC 2 audit process.

Organization & Governance

4 items
CC1.1

Board of directors or equivalent oversees information security

Low effort
CC1.2

Management establishes a structure with assigned security responsibilities

Low effort
CC1.3

Background checks conducted for employees in security-sensitive roles

Medium effort
CC1.4

Security policies reviewed and approved annually

Low effort

Communication & Information

3 items
CC2.1

Information security policy communicated to all employees

Low effort
CC2.2

Security training completed by all staff annually

Medium effort
CC2.3

Security incidents reported to appropriate personnel

Medium effort

Risk Assessment

4 items
CC3.1

Risk assessment process defined and documented

Medium effort
CC3.2

Risk assessment conducted at least annually

Medium effort
CC3.3

Significant changes trigger a new risk assessment

Medium effort
CC3.4

Fraud risk considered in the risk assessment

Low effort

Monitoring Activities

2 items
CC4.1

Security controls monitored on an ongoing basis

High effort
CC4.2

Internal audit or independent review conducted

High effort

Logical & Physical Access

6 items
CC6.1

Unique IDs assigned to all users — no shared accounts

Low effort
CC6.2

MFA enforced for all remote access and privileged accounts

Medium effort
CC6.3

Access provisioning follows a formal approval process

Medium effort
CC6.6

Encryption used for all data transmitted over public networks

Low effort
CC6.7

Data classified and handled according to classification policy

Medium effort
CC6.8

Malicious software controls implemented (AV, EDR)

Medium effort

System Operations

4 items
CC7.1

Vulnerability scanning conducted regularly

Medium effort
CC7.2

Security incidents identified and responded to within defined SLAs

High effort
CC7.3

Incident response plan documented and tested

High effort
CC7.5

Identified security deficiencies communicated to management

Low effort

Change Management

2 items
CC8.1

Change management process documented and followed

Medium effort
CC8.2

Security testing conducted before production deployment

High effort

Track this checklist automatically in Unicis

Every item in this checklist is a trackable control in Unicis. Automatically link evidence, track completion status, and generate audit-ready reports. Ultimate plan includes all SOC 2 Trust Services Criteria.

What a SOC 2 Type II journey
looks like in practice

01

Readiness

1–3 months

GAP analysis, policy development, control implementation, evidence collection setup.

02

Type I audit

1–2 months

Auditor reviews design effectiveness of controls at a point in time. Good for first-time SOC 2.

03

Observation period

6–12 months

Evidence collected continuously over the observation window for Type II.

04

Type II audit

1–2 months

Auditor reviews operating effectiveness of controls over the observation period.

Who needs SOC 2?

SOC 2 is widely adopted by technology companies, cloud service providers, SaaS platforms, financial institutions, healthcare organizations, and any entity responsible for managing customer data or IT services — particularly those selling to US enterprise customers.

B2B SaaSCloud ProvidersFintechHealthtechHR PlatformsData AnalyticsManaged ServicesPayment Processors

Multi-Framework Support

11 Compliance Frameworks Supported

From the minimum viable security baseline to enterprise-grade standards — coverage for every compliance requirement.

Community (Free) Premium Ultimate

Start your SOC 2 preparation with Unicis

Unicis automates evidence collection, GAP analysis, and audit reporting for SOC 2. Ultimate plan includes all Trust Services Criteria. Start with the free Community plan to build your foundation.