In this article:

SOC 2 Readiness Assessment: Scope, Cost, Timeline, and What You Get

Compliance
/
November 16, 2026
SOC 2 Readiness Assessment: Scope, Cost, Timeline, and What You Get

A SOC 2 readiness assessment is a gap analysis performed before the CPA firm starts its examination. The assessor defines the system in scope, maps your existing controls to the trust services criteria you plan to report on, tests whether each control is designed properly and leaves evidence, and gives you a prioritized list of what to fix. It typically takes two to six weeks and costs $5,000 to $40,000, depending on how much of the remediation you want the assessor to carry. The output is internal. It is not an audit, it produces no report you can hand to a customer, and it carries no opinion. Its value is that the auditor's first look at your controls is no longer the first time anyone has tested them.

What is a SOC 2 readiness assessment?

SOC 2 is an examination performed by a CPA firm under AICPA attestation standards. The AICPA describes the wider family as a suite of service offerings CPAs may provide, and a SOC 2 report covers controls at a service organization relevant to security, availability, processing integrity, confidentiality, or privacy. The examination has two inputs that you own: a written description of your system, and the controls you assert are in place. A readiness assessment checks both before the auditor does.

Three terms get used for the same idea. A gap assessment compares your controls to the criteria and lists what is missing. A self-assessment is the same comparison done by your own team, often inside a compliance automation platform. A readiness assessment usually means the fuller version: an outside party scopes the system, tests the controls the way an auditor would, and produces a remediation plan. The differences are in depth and independence, and the question each one answers is identical: if the examination started today, where would the exceptions be?

What does a readiness assessment cover?

The assessment follows the two documents the auditor will use. The first is the 2017 Trust Services Criteria (With Revised Points of Focus, 2022), which holds the control criteria. Security is the category every SOC 2 report includes, and its criteria are organized as nine common criteria series, CC1 through CC9. Availability, confidentiality, processing integrity, and privacy are added only when your commitments to customers call for them. The second document is the 2018 SOC 2 Description Criteria, the benchmarks for the system description that opens the report.

AreaWhat the assessor checksGap we find most often
System description and scopeServices, infrastructure, software, people, data, and the boundaries of the systemScope includes products or environments no customer asked about
CC1 and CC2, control environment and communicationBoard or management oversight, code of conduct, organizational chart, and how commitments reach staff and customersPolicies exist but nobody has acknowledged them
CC3 and CC4, risk assessment and monitoringA documented risk assessment, including fraud and change, and evidence that controls are reviewedRisk assessment performed once and never repeated
CC5 and CC6, control activities and accessProvisioning, removal, access reviews, multifactor authentication, encryption, and physical accessDeparted users still active, and no periodic access review
CC7, system operationsVulnerability management, logging, alerting, and incident responseAlerts exist with no record that anyone responded
CC8, change managementApproval, testing, and separation of duties for production changesChanges merged and deployed by the same person with no review
CC9, risk mitigationVendor management and business disruption planningNo security review for critical vendors

For each control, the assessor asks two questions. Is the control designed so that it would meet the criterion if it operated? And would it leave evidence that an auditor can sample? Many first-year exceptions come from the second question. A team that reviews access every quarter in a meeting, with no ticket or sign-off, has a control that operates and cannot be proven.

What do you receive at the end?

A useful readiness assessment ends with six things. The first is a scope statement: the system boundary, the trust services categories, and the subservice organizations, such as your cloud provider, that the report will carve out. The second is a control matrix that maps each of your controls to the criteria it satisfies. The third is a gap register, with every gap rated by how likely it is to become an exception in the report. The fourth is a remediation plan with an owner and a date for each gap. The fifth is an evidence list, so your team knows what the auditor will request and where each item lives. The sixth is a recommendation on report type and timing: whether to start with a Type 1, how long the Type 2 observation period should be, and when it can begin. Our comparison of SOC 2 Type 1 and Type 2 covers that last decision.

Ask to see a sample gap register before you hire an assessor. A register that says "improve access management" is not usable. One that says "14 of 60 terminated users retained active single sign-on accounts for more than five business days; deprovisioning is manual and has no ticket" tells an engineer what to build.

How long does it take and what does it cost?

BD Emerson's planning ranges, for a company of 20 to 300 people with one production environment, are below. Headcount, the number of environments, and the number of trust services categories move the numbers.

PhaseDurationCostWhat drives it
Readiness assessment only2 to 6 weeks$5,000 to $15,000Scope, number of categories, and how much documentation exists
Assessment plus remediation support2 to 4 months$15,000 to $40,000Policy writing, control build, platform configuration, and interview preparation
Type 2 observation period3 to 12 monthsInternal staff timePeriod length agreed with the auditor and required by customers

These figures sit beside the audit fee, the automation platform, and a penetration test. Our SOC 2 cost breakdown puts all of them in one first-year budget.

The readiness assessment pays for itself when it shortens the path to a clean report. An exception in a Type 2 report stays in that report for the whole period it covers, and the next clean report is up to 12 months away. A gap found in week two of a readiness assessment costs an engineering ticket.

When can you skip the readiness assessment?

You can skip it in three situations. The first is a second-year program with a clean prior report and no change in scope, where last year's audit is the readiness assessment. The second is a company that already holds ISO 27001 certification with a current internal audit, where most of the controls are tested and the work is a mapping exercise. The third is a company that chooses a Type 1 report as its first step, because a Type 1 tests design at a point in time and exposes most design gaps.

The third route has a cost. A Type 1 with exceptions is still a report customers will read, while a readiness assessment stays private. If the first report is going straight into an enterprise sales cycle, find the gaps privately first.

Who should perform it?

You have three options, and the differences come down to independence. A compliance automation platform will run automated tests against your cloud accounts and identity provider and show which checks fail. That covers the technical controls well and leaves out the ones that live in documents and meetings, such as risk assessment, vendor review, and board oversight. Your future audit firm can perform a readiness assessment, and many do. Independence rules limit how far the firm can go: it can tell you where the gaps are, but it cannot design or operate the controls it will later examine. A consulting firm can do both the assessment and the remediation, because it will not sign the report.

BD Emerson sits in the third group. We do not perform SOC 2 examinations. An independent CPA firm that you select examines the controls and issues the report, and we prepare you for it. That separation means the people who find your gaps are free to help close them.

What do the proposed 2027 criteria change for readiness?

On October 26, 2026, the AICPA posted exposure drafts of proposed 2027 SOC 2 Trust Services Criteria and Description Criteria. They are drafts open for comment. The 2017 criteria with the 2022 points of focus remain the criteria in use until the AICPA issues final versions with an effective date.

For a company starting readiness now, the practical step is a question for the audit firm: which version of the criteria will apply to your examination period? Build the control matrix so that each control maps to a criterion by reference. When the criteria change, you can remap the matrix without rebuilding the controls.

What if you need SOC 2 and HIPAA together?

A company that handles protected health information often asks for one examination that covers both. Auditors can address additional criteria in a SOC 2 examination, and a report that maps controls to the HIPAA Security Rule alongside the trust services criteria is commonly called SOC 2 plus HIPAA. The readiness assessment for that report widens in two places. The scope has to name every system that stores or transmits protected health information, and the control matrix needs a second mapping from each control to the Security Rule safeguards. A HIPAA risk analysis also has to exist before the examination, because the Security Rule requires one and the auditor will ask for it.

Most of the technical controls overlap, so the added effort is in documentation and in business associate agreements. Running the two as one readiness project costs less than running them in sequence, since the evidence is collected once.

Where BD Emerson fits

The readiness assessment covers the first two of the nine steps in our SOC 2 compliance checklist: scoping the trust services criteria and running the gap assessment. BD Emerson's SOC 2 consulting service covers the assessment, the remediation that follows, and preparation for auditor interviews, for first-year programs and for teams heading into a second-year Type 2 with a new auditor. We scope the system with you, test each control against the criteria, hand you a gap register your engineers can act on, and stay through remediation until the evidence is ready for the CPA firm you choose.

About the author

Leslie Sakal is a Managing Director at BD Emerson focused on cybersecurity, enterprise risk management, and regulatory compliance. She brings over a decade of experience advising organizations across technology, financial services, education, and other regulated industries on implementing organization-wide goals and programs that align with their broader business objectives.
Leslie Sakal
Leslie Sakal
Managing Director