Radius360 by BlueRadius
Radius360by BlueRadius

SOC 2 checklist

SOC 2 checklist: what to have in place before the auditor arrives

Scope the report, cover the common criteria, collect the evidence and pick the right report type. This is the order most teams follow.

Step 1: Scope it

  • Decide which systems, services and data are in scope.
  • Choose the Trust Services Criteria: Security is required; add Availability, Processing Integrity, Confidentiality or Privacy only if customers need them.
  • Choose Type I or Type II, and for Type II agree the observation period with your auditor.
  • Pick a licensed CPA firm early so you know what evidence it expects.

Step 2: Cover the common criteria

  • CC1 Control environment: Board or management oversight, ethics, org structure, hiring and accountability.
  • CC2 Communication and information: Internal and external communication of security responsibilities and commitments.
  • CC3 Risk assessment: A documented risk assessment, including fraud risk and changes that affect controls.
  • CC4 Monitoring activities: Ongoing and separate evaluations, and fixing what they find.
  • CC5 Control activities: Controls and policies that address the risks, and the technology controls behind them.
  • CC6 Logical and physical access: Access provisioning and reviews, authentication, encryption, physical access and device protection.
  • CC7 System operations: Vulnerability management, monitoring, incident detection, response and recovery.
  • CC8 Change management: Authorized, tested and approved changes to systems and infrastructure.
  • CC9 Risk mitigation: Business disruption planning and vendor and business partner risk management.

Step 3: Write the policies

Auditors expect written, approved policies for information security, acceptable use, access control, change management, incident response, business continuity, vendor management, data classification and risk management, with evidence that staff have acknowledged them. Start from our free security policy templates.

Step 4: Collect the evidence

  • A current risk assessment and risk register (free template)
  • Quarterly user access reviews, with decisions recorded
  • Onboarding and offboarding records, background checks and training completion
  • Vulnerability scans and remediation records
  • Change tickets showing approval and testing
  • Incident response plan and test results
  • Vendor reviews for key suppliers
  • Backup and restore test results

Step 5: Readiness check, then the audit

Run a readiness assessment against the criteria, fix the gaps, then let the auditor test. For a Type II report, the evidence has to show the controls working across the whole observation period, so start collecting early. If you are also weighing ISO 27001, see the ISO 27001 checklist; many controls overlap.

Frequently asked

What is the difference between SOC 2 Type I and Type II?+

A Type I report says your controls are suitably designed at a point in time. A Type II report says they operated effectively over a period, so the auditor tests samples across that window. Most enterprise customers ask for Type II.

Which Trust Services Criteria do we need?+

Security, also called the common criteria, is required in every SOC 2 report. Availability, Processing Integrity, Confidentiality and Privacy are optional; include them when your customers or contracts call for them.

Who can issue a SOC 2 report?+

Only a licensed CPA firm. Software and consultants can get you ready, but the report itself comes from the auditor.

Is SOC 2 a certification?+

Not technically. SOC 2 is an attestation report, not a certificate. You do not pass or fail; the auditor gives an opinion and lists any exceptions found.

Run SOC 2 readiness without the spreadsheet

Radius360 maps your controls to the Trust Services Criteria, collects evidence from connected tools and shows what is still missing.

Start free trial