← Back to SOC 1

SOC 1 Requirements

Everything you need to produce a clean SOC 1 (SSAE 18) opinion — control objectives, ITGC domains, CUECs, carve-outs, and the Section 3 description.

Type 1 vs Type 2

Both are SOC 1 reports under SSAE 18. The difference is what the auditor opines on.

1

Type 1

Opinion on the design of controls at a specific point in time.

  • Shorter engagement (typically 4-8 weeks)
  • No evidence of operating effectiveness required
  • Useful as a first-year stepping stone before Type 2
  • Often not sufficient for user-entity financial auditors
2

Type 2

Opinion on design and operating effectiveness across a reporting period (typically 6-12 months).

  • Requires evidence of each control running throughout the window
  • The report user-entity auditors actually ask for
  • Automated evidence collection is critical
  • Repeats annually with a rolling reporting period

ITGC Domains

SOC 1 doesn't prescribe a universal control list. Instead, you define control objectives tied to the financial statement assertions you affect. These five IT general control domains almost always appear.

Control Environment

5 controls

Entity-level governance, policies, and oversight of subservice organizations

  • Information security policy approved by management
  • Entity-level risk assessment covering ICFR-relevant services
  • Code of conduct and ethics training
  • Documented organizational structure and reporting lines
  • Oversight of vendors and subservice organizations

Access to Programs and Data

10 controls

Provisioning, authentication, privileged access, and segregation of duties

  • Documented access request, approval, and provisioning
  • Password standards and multi-factor authentication
  • Privileged access management with enhanced monitoring
  • Periodic user access reviews with remediation tracking
  • Timely revocation on termination or role change
  • Segregation of duties or compensating detective controls
  • Restricted direct database access with change logging
  • Network segmentation and perimeter protection

Program Development

4 controls

SDLC, testing, and data migration for new systems and significant enhancements

  • Documented SDLC methodology
  • Testing and user acceptance in a non-production environment
  • Data migration validated for completeness and accuracy
  • Peer code review covering security-relevant changes

Program Changes

6 controls

Authorization, testing, environment separation, and promotion of ongoing changes

  • Formal change request and authorization
  • Changes tested in non-production prior to deployment
  • Separation of development, test, and production environments
  • Emergency change procedure with after-the-fact review
  • Only authorized personnel migrate changes to production
  • End-to-end audit trail on each change ticket

Computer Operations

9 controls

Processing, backup, disaster recovery, monitoring, incidents, and physical security

  • Batch job scheduling, execution, and failure resolution
  • Scheduled backups with monitoring
  • Periodic backup restoration testing
  • Documented and tested disaster recovery plan
  • Incident response with user-entity communication
  • Capacity and performance monitoring against commitments
  • Security event logging, retention, and review
  • Physical and environmental security of data centers

Structure of a SOC 1 Report

Beyond control testing, a SOC 1 report has four defined sections. Section 3 (the system description) is where first-time filers usually spend the most time.

Section 1: Service Auditor's Report

The CPA firm's opinion on management's description and (for Type 2) the operating effectiveness of controls over the reporting period.

Section 2: Management's Assertion

Service organization management's written assertion that the Section 3 description is fairly presented and controls are suitably designed (and, for Type 2, operating effectively).

Section 3: System Description

The narrative covering services, infrastructure, people, data, subservice organizations, CUECs, and material system changes during the period.

Section 4: Controls, Tests, and Results

Each control objective, the specific controls supporting it, the auditor's tests, and the results including any noted deviations.

CUECs and Subservice Organizations

Two concepts you'll see in every SOC 1 engagement. Both exist because your controls alone rarely cover the full ICFR picture.

Complementary User Entity Controls (CUECs)

Controls that your customers must operate for your controls to achieve their objectives. Documented in Section 3 so user-entity auditors can test them.

Example: "User entities are responsible for configuring their own user roles and performing periodic reviews of their users' access to the service."

Subservice Organizations

Third parties whose controls are relevant to your ICFR (cloud hosts, data centers, payment rails). You choose inclusive (they're tested with you) or carve-out (you rely on their own SOC 1/2 and disclose which controls you depend on).

Example: AWS carve-out — your report relies on AWS's SOC 1 for data center physical security and infrastructure availability.

Need help scoping yours?

Book a scoping call and we'll walk through control objectives, CUECs, and carve-outs for your specific services.