PlatformPlatform overviewAudit readinessEvidence roomPolicy managementRisk registerVendor riskSecurity questionnairesPeople & trainingIncidents & continuityReports & exportsSolutionsClear security reviewsPass your first auditManage third-party riskStay continuously readyFrameworksSOC 2HIPAAISO 27001NIST CSFPCI DSSResourcesAll resourcesBlogSOC 2 guideHIPAA Security Rule guideISO 27001 guideSecurity questionnaires guideSOC 2 readiness checklistFAQCompanyPricingAbout usServicesSecurityTrust CenterPartnersCareersNewsroomContactSign inRequest a demo

Home / Resources / SOC 2 guide

Guide

SOC 2, explained for teams doing it for the first time.

What the report is, what auditors look at, and how to get from no controls to a clean report.

Guide · Updated November 9, 2026 · General information, not legal or audit advice

What SOC 2 is

SOC 2 is an attestation report on a service organisation’s controls, defined by the American Institute of Certified Public Accountants (AICPA). An independent CPA firm examines your controls and writes an opinion on them. Customers ask for it because it lets them rely on an independent check instead of auditing you themselves.

There is no pass or fail certificate. You receive a report, and the auditor’s opinion in it says whether your controls are suitably designed (and, for Type II, whether they operated effectively).

The Trust Services Criteria

The report is built on the Trust Services Criteria. Security is always in scope; the other four are optional and chosen by what you promise customers.

CriteriaCoversInclude it when
Security (Common Criteria)Protection against unauthorised accessAlways
AvailabilityUptime and recoveryYou commit to uptime or recovery times
ConfidentialityData marked confidentialYou hold customers’ confidential information
Processing integrityComplete, accurate, timely processingYour service processes transactions or calculations
PrivacyPersonal information over its life cycleYou collect personal data directly from individuals

Type I versus Type II

Type IType II
Question it answersAre the controls designed properly on one date?Did the controls work over a period of time?
PeriodA single point in timeAn observation window, commonly 3 to 12 months
Typical useA first report to unblock deals quicklyWhat most enterprise customers ultimately ask for

Many companies start with Type I and move to Type II, or go straight to a Type II with a shorter first window.

How to get there

  1. Scope. Decide which systems, people and criteria are in scope.
  2. Gap assessment. Compare what you do today with the criteria.
  3. Remediate. Write policies, put controls in place, assign owners.
  4. Collect evidence. Screenshots, exports, tickets and sign-offs that prove each control.
  5. Pick an auditor. A licensed CPA firm; ask about their experience with companies your size.
  6. Audit. Type I on a date, or Type II across the observation window.
  7. Stay ready. Controls must keep operating; the next report covers the next period.

Where teams get stuck

  • Evidence collected once and then left to go stale.
  • Access reviews that happen but are never recorded.
  • Vendors with no assessment or agreement on file.
  • Policies that exist but were never acknowledged by staff.
  • Change management with no recorded approval.

How Doniastack helps

Doniastack tracks each control against the criteria, keeps evidence with its collection date and owner, and gives your auditor a workspace. Our specialists run the gap assessment and work through remediation with you. Start with the SOC 2 readiness checklist.

Get started

See where you stand in 30 minutes

Tell us which review or audit is in front of you. We'll walk you through the platform and map what readiness takes, with no obligation.