Attestation

SOC 2

Type I and Type II reports over the Trust Services Criteria: security, availability, processing integrity, confidentiality, and privacy.

Ready Applies in: North America, Europe, Asia Pacific, South America

Controls passing
3 of 5
Needs action
2
Readiness
60%

Sample data The framework defines 64 controls in total. The figures above and the checklist below track a sample of 5 of them, with owners and due dates.

What SOC 2 requires

SOC 2 is an attestation framework published by the AICPA. An organisation defines its own controls against the Trust Services Criteria — security, availability, processing integrity, confidentiality, and privacy — and an independent CPA firm examines those controls. A Type I report covers the design of the controls at a single date; a Type II report covers how they operated across a period, usually three to twelve months.

The security category, often called the Common Criteria, is the part every SOC 2 report includes. It asks for documented control over who can reach systems and data, how changes are approved before deployment, how incidents are detected and handled, and how risks are assessed. None of this is checked once: the observation period runs for months, so the evidence has to exist for the whole period.

That timing shapes the work. Access reviews, change tickets, monitoring alerts, and vendor assessments are gathered as the work happens, because an auditor samples from the full period and a gap in the record reads as a gap in the control. Reports are shared under NDA, and readers weigh the listed exceptions as carefully as the passes.

Evidence checklist

The sample controls tracked for this guide, in due-date order. A control marked as passing has current evidence on file; one marked as needing action has an owner and a deadline.

  • CC6.1 — Logical access restricted to authorised users

    Owner: IT operations lead · Due

    Passing
  • CC6.6 — Encryption for data in transit and at rest

    Owner: Platform engineer · Due

    Passing
  • CC7.2 — Change tickets approved before deployment

    Owner: Engineering manager · Due

    Needs action
  • CC7.4 — Incident response plan tested in the period

    Owner: Security lead · Due

    Needs action
  • CC8.1 — Vendor reviews completed for critical suppliers

    Owner: Compliance manager · Due

    Passing
SOC 2 sample controls by status (controls)
0 1 2 3 SOC 2 Passing Needs action

Related guides

Guides in the same family are listed first.