A SOC 2 audit is an independent examination of the controls a service organization uses to protect customer data, measured against the American Institute of Certified Public Accountants (AICPA) Trust Services Criteria. A readiness assessment is the structured work you do before that examination begins: you map your controls to the criteria, find the gaps, and fix them while there is still time. This article walks through the five Trust Services Criteria, explains how a Type I report differs from a Type II report, and gives you a practical checklist to work through before your first SOC 2 Type II examination.
Most first-time failures are not caused by weak technology. They are caused by controls that exist in practice but were never documented, never assigned an owner, or never produced evidence an auditor can test. A readiness assessment surfaces those issues early, which is exactly why buyers increasingly ask for a clean SOC 2 report before they sign.
What the Five Trust Services Criteria Actually Cover
SOC 2 is built on the AICPA 2017 Trust Services Criteria (with revised points of focus, 2022), established by the AICPA Assurance Services Executive Committee. There are five criteria categories, and a common mistake is assuming all five apply to every engagement. Only one is mandatory, and the other four are included based on the commitments you make to customers.
Security is the only required category and is often called the common criteria. It covers protection of information and systems against unauthorized access, unauthorized disclosure, and damage that could compromise availability, integrity, confidentiality, or privacy. Security maps closely to the COSO internal control framework and includes logical and physical access controls, change management, risk assessment, and incident response.
Availability addresses whether systems are available for operation and use as committed or agreed. This is where capacity planning, performance monitoring, backup, and disaster recovery live. It does not set a minimum uptime; it tests whether you meet the commitments you actually made.
Processing integrity addresses whether system processing is complete, valid, accurate, timely, and authorized. It is most relevant to organizations that process transactions on behalf of customers, such as payment or payroll platforms, where a wrong output has direct financial consequences.
Confidentiality addresses information designated as confidential, covering how it is collected, used, retained, and disposed of. Think contractual nondisclosure obligations, encryption of sensitive business data, and defined retention and destruction schedules.
Privacy addresses personal information specifically, aligned to the organization’s privacy notice and criteria consistent with generally accepted privacy principles. It is the most involved category to add because it reaches into consent, data subject rights, and third-party disclosure practices. Scope each category deliberately: adding privacy or processing integrity when you have no real obligation only enlarges the audit without adding value for customers.
Type I Versus Type II: The Difference That Changes Your Timeline
Both report types evaluate the same controls against the same Trust Services Criteria, but they answer different questions, and the difference drives your entire planning calendar.
A Type I report evaluates whether your controls are suitably designed and in place at a single point in time. The auditor looks at your control environment on a specified date and opines on design. It is faster to obtain and useful as a first milestone, but it says nothing about whether the controls actually worked day after day.
A Type II report evaluates both the design and the operating effectiveness of controls over a defined review period, commonly three to twelve months. The auditor collects evidence showing the controls ran consistently throughout that window, not just on one day. Because buyers want assurance that your controls hold up over time, the Type II report is what most enterprise customers and procurement teams require. You can read the AICPA’s full explanation of the SOC suite of services and SOC 2 reporting for the authoritative framing.
The practical consequence is simple. A Type II examination tests evidence across an observation period, so if a control was not operating during the first two months of that period, no amount of late effort will produce the missing evidence. This is the single strongest argument for a readiness assessment: it forces you to turn controls on and start generating evidence before the clock starts.
The SOC 2 Type II Readiness Assessment Checklist
Work through the checklist below before you commit to a Type II observation window. Each item is something an examiner will expect to see, and each is something a readiness assessment is designed to catch while it is still cheap to fix.
1. Define scope and select criteria
- Confirm which systems, products, and data flows are in scope, and document the boundary clearly.
- Select which Trust Services Criteria categories apply beyond the required Security category, based on your customer commitments and contractual obligations.
- Write a system description that accurately explains your services, infrastructure, software, people, procedures, and data. The description is part of the report, and inaccuracies here undermine the entire engagement.
2. Establish governance and risk assessment
- Document a formal risk assessment process that identifies threats, rates likelihood and impact, and ties each risk to a mitigating control.
- Define roles and responsibilities, including who owns each control and who reviews it.
- Confirm board or leadership oversight of the security program is evidenced in meeting records or policy approvals.
3. Formalize policies and procedures
- Maintain written policies for information security, acceptable use, access control, change management, incident response, business continuity, and vendor management.
- Ensure policies are version controlled, approved by management, and reviewed at least annually.
- Confirm employees acknowledge policies at hire and on a recurring schedule, with records retained.
4. Harden access controls
- Enforce unique user accounts, role-based access, and least privilege across production systems.
- Require multi-factor authentication for administrative and remote access.
- Run periodic user access reviews and document that terminated users were deprovisioned promptly.
5. Control change management
- Require changes to code and infrastructure to be reviewed, tested, and approved before deployment.
- Separate development, testing, and production environments.
- Keep a change log that an auditor can sample across the review period.
6. Monitor, log, and respond
- Centralize logging and enable alerting for security-relevant events.
- Maintain an incident response plan with defined severity levels, and test it at least once before the observation period.
- Retain evidence of incidents, how they were handled, and what remediation followed.
7. Manage vendors and subservice organizations
- Inventory third parties that touch in-scope data and classify them by risk.
- Collect and review their SOC reports or equivalent assurance, and document the review.
- Decide whether to use the inclusive or carve-out method for subservice organizations, and reflect that choice in your system description.
8. Prove the evidence engine runs
- Confirm each control produces a repeatable, time-stamped artifact: tickets, logs, approvals, review sign-offs, or screenshots.
- Assign an owner and a cadence to every piece of evidence so it accumulates automatically during the observation period.
- Run a dry sample. If you cannot pull three months of evidence for a control today, that control is not ready for a Type II window.
Treat the readiness assessment as a rehearsal of the real examination. If you can satisfy each item above with documentation an independent party could test, you are prepared to start the observation period with confidence.
Common Readiness Gaps That Delay a Report
A few failure patterns recur across first-time examinations. Controls operate informally but are never written down, so there is nothing for the auditor to reference. Access reviews happen in someone’s head rather than in a documented, dated sign-off. Change management is disciplined for code but ignored for infrastructure. Vendor risk is assumed rather than reviewed. Each of these is invisible until an examiner asks for evidence, and each is straightforward to fix months ahead of time but nearly impossible to fix retroactively once the window has started.
The other recurring gap is ownership. A control without a named owner tends to drift, and drift during a Type II observation period shows up as an exception in the final report. Assigning owners and review cadences during readiness is the cheapest insurance you can buy against exceptions.
Turning a Readiness Assessment Into a Clean Report
A SOC 2 engagement is most efficient when readiness and examination are planned together rather than treated as separate events. The readiness assessment identifies and closes gaps, management remediates, and only then does the formal observation period begin. Rushing into a Type II window without this step is the most common reason reports come back with exceptions or slip their deadline.
Pease Bell’s risk advisory services help organizations run the readiness assessment, scope the right Trust Services Criteria, and build the control and evidence structure that a Type II examination depends on. When you are ready for the examination itself, our audit and assurance services deliver the independent SOC 2 report that your customers and prospects are asking for. Approaching readiness and examination as one continuous process is the surest way to move from first attempt to a clean opinion without wasted cycles.
A SOC 2 audit rewards preparation. Define your scope, map your controls to the five Trust Services Criteria, prove your evidence engine runs, and you will enter your Type II observation period ready to pass rather than hoping to.
Frequently Asked Questions
How long is a SOC 2 Type II observation period?
A SOC 2 Type II report evaluates the design and operating effectiveness of controls over a defined review period, commonly three to twelve months. The auditor collects evidence that controls ran consistently throughout that window, not just on one day. Because evidence is tested across the full period, controls need to be operating and producing evidence before the period starts.
Which Trust Services Criteria are required in a SOC 2 audit?
Only the Security category is required in every SOC 2 engagement. It is often called the common criteria. The other four categories, availability, processing integrity, confidentiality, and privacy, are included based on the commitments you make to customers. Adding a category you have no real obligation for only enlarges the audit without adding value for customers.
Does the SOC 2 availability criterion require a minimum uptime?
No. The availability category does not set a minimum uptime. It tests whether systems are available for operation and use as committed or agreed, meaning whether you meet the commitments you actually made to customers. Capacity planning, performance monitoring, backup, and disaster recovery controls fall under this category.
Can I fix a control gap after the SOC 2 Type II period has started?
Not retroactively. A Type II examination tests evidence across the observation period, so if a control was not operating during the first two months of that period, no amount of late effort will produce the missing evidence. That is the strongest argument for a readiness assessment, which turns controls on and starts generating evidence before the clock starts.
Should a company get a SOC 2 Type I report before a Type II?
A Type I report can be a useful first milestone because it is faster to obtain and evaluates whether controls are suitably designed and in place at a single point in time. It says nothing about whether controls worked over time, however, and most enterprise customers and procurement teams require the Type II report for that reason.




