SOC 2 Readiness Assessment, Gap Assessment and Remediation Services

Find out what your service auditor will find, before the auditor finds it. Delivered by a peer-reviewed CPA firm with offices in Wilmington, Delaware and Bengaluru, India.

Book a scoping call See how the services differ
Peer-reviewed CPA firm We can sign the report, not just prepare you for it
120+ SOC engagements SOC 1 and SOC 2 work across the engagement team
Delaware and Bengaluru US licence and India delivery under one firm
HITRUST assessor Authorized External Assessor for healthcare clients

A SOC 2 readiness assessment tells you what your service auditor will find before the auditor finds it. EntPerMaSys Consulting runs that assessment as a peer-reviewed CPA firm, so the gaps we raise are the gaps that get tested in a real examination, scored against the Trust Services Criteria your customers asked you to report on. You work with a named SOC 2 readiness consultant from the scoping call through to the readout.

Most first SOC 2 projects slip on timing, not on security. A company closes an enterprise deal in March, books an examination for June, and finds in May that access reviews were never written down, that leavers kept live credentials for three weeks, and that the logs an auditor wants to sample were rotated out after 30 days. A SOC 2 gap assessment run early turns that into a dated work plan instead of a delayed deal.

Definition

What a SOC 2 readiness assessment is

A SOC 2 readiness assessment is a structured review of your controls, policies and evidence against the AICPA Trust Services Criteria you intend to report on, completed before the formal examination starts. The output is a written gap register: each finding, the criterion it sits under, the control that has to exist, and the evidence the auditor will ask for.

Four things it is not, because this is where buyers lose money:

It is not a certification

SOC 2 produces an attestation report signed by a licensed CPA firm. There is no SOC 2 certificate and no certifying body.

It is not an examination

A readiness assessment contains no auditor opinion, so it cannot be sent to a customer as proof of anything.

It is not a fixed checklist

The Trust Services Criteria are applied to your system. Two companies of the same size reporting on the same criteria can need different controls.

It is not remediation

Finding a gap and closing it are separate pieces of work, and in some cases they have to be done by separate firms. That rule is explained further down this page.

Comparison

SOC 2 readiness assessment, SOC 2 gap assessment and the examination compared

The terms get used loosely across the market. Here is how the four pieces of work actually differ, and how EntPerMaSys Consulting uses them.

  SOC 2 readiness assessment SOC 2 gap assessment Type 1 report Type 2 report
Question it answers Can we pass, and when Which specific controls are missing or undocumented Were the controls designed correctly on one date Did the controls operate correctly across a period
Scope of work Scoping, control mapping, walkthroughs, evidence sampling, remediation plan Control mapping and gap identification against the chosen criteria Independent testing of control design Independent testing of design and operating effectiveness
What you receive Gap register, risk-ranked remediation plan, dated path to an examination Gap register mapped to criteria Signed report with an auditor opinion Signed report with an auditor opinion and test results
Who performs it A CPA firm or a qualified advisory firm A CPA firm or a qualified advisory firm A licensed CPA firm only A licensed CPA firm only
Typical duration 3 to 5 weeks 2 to 3 weeks 3 to 6 weeks of fieldwork 3 to 12 month observation window, then fieldwork
Shareable with customers No No Yes, under NDA Yes, under NDA
Contains an opinion No No Yes Yes

Swipe the table sideways to see every column.

In plain terms: the SOC 2 gap assessment is the diagnostic step, and the SOC 2 readiness assessment is the full engagement that contains it plus scoping, evidence testing and a plan with dates and owners. If you only need to know where you stand, the gap assessment is enough. If you have a customer deadline to hit, the readiness assessment is the piece that gets you there, because the plan is the part that moves the date.

Deliverables

What a SOC 2 gap assessment delivers

Every SOC 2 gap assessment we run ends with the same six documents, so your engineering lead, your security owner and your buyer all work from one version of the facts.

1

Scope statement

The system boundary in writing: products, environments, cloud accounts, repositories, identity provider, data stores and the third parties inside the boundary. This is the document that keeps the examination from growing after the fee is agreed.

2

Criteria selection memo

Which Trust Services Criteria you are reporting on and why. Security is required. Availability, Processing Integrity, Confidentiality and Privacy are added only where a customer contract or a regulator asks for them, because each one you add raises both the remediation work and the examination fee.

3

Control mapping matrix

Every control you already run, mapped to the criterion it satisfies, with the owner named.

4

Gap register

Each gap, the criterion it breaches, whether it is a design gap or an evidence gap, and the risk rating. Design and evidence gaps are separated because they are fixed in different ways and on different timelines.

5

Evidence inventory

For each control, the artefact an auditor will sample, where it lives, who produces it, and the retention period it needs. Short log retention is the single most common reason a Type 2 window has to be restarted.

6

Remediation plan

The gaps in fix order, each with a named owner, a date and a completion test, plus the earliest honest date you can open an observation window.

Findings

The six control areas where first-time gaps concentrate

Across SOC 1 and SOC 2 engagements, our findings cluster in the same places. The right-hand column is what we actually write up, not a generic category.

Control area What the auditor tests The gap we find most often
Logical access Provisioning approvals, access reviews, privileged accounts, MFA coverage Access reviews happen in conversation but produce no dated artefact with a reviewer name on it
Offboarding Access removed across every system on the leaver date HR records a leaving date, but contractor accounts and shared tool logins stay active for weeks
Change management Approval, testing and separation of duties on production changes Pull requests are approved by the author on urgent fixes, and nothing records the exception
Logging and incident response Log retention, alert triage, documented incidents, a tested response plan Logs retained for 30 days against a 12 month window, and an incident response plan nobody has rehearsed
Vendor management Risk rating of subservice organisations, review of their SOC reports A vendor register exists but no one has read the subservice organisations' own reports or tracked the complementary controls those reports assign to you
Backup and recovery Restore testing against stated recovery objectives Backups run and are monitored, but no timed restore test has ever been completed and signed off

Swipe the table sideways to see every column.

Process

How the engagement runs

Five phases. A single-criterion scope on one product runs 3 to 5 weeks end to end. More criteria, more environments or a multi-entity group takes longer, and we give you the number in the proposal rather than after kickoff.

1

Scoping and criteria selection

3 to 5 business days

We read the customer contracts and security questionnaires that triggered the project, then set the system boundary and the criteria. Most companies arrive wanting all five criteria and leave with two, which removes work rather than adding it.

2

Control mapping

3 to 5 business days

Your existing policies, tickets and configurations are mapped to the criteria. Companies holding ISO 27001 usually find a large share of the Security criteria already covered.

3

Walkthroughs and evidence sampling

5 to 10 business days

We sit with each control owner, watch the control run, and pull the same samples an auditor would pull. This phase is what separates a SOC 2 readiness assessment from a questionnaire, and it is where the findings that matter come from.

4

Gap register

3 to 5 business days

Findings written up, rated and split into design gaps and evidence gaps.

5

Remediation plan and readout

2 to 3 business days

A working session with your leadership on fix order, owners, dates and the observation window. You leave with a plan your engineers can execute, not a list of criteria.

You keep working with the same people throughout. A SOC 2 readiness consultant who ran your walkthroughs writes your gap register and sits in your readout, because the person who watched the control run is the person who knows whether it will survive testing.

Remediation

SOC 2 remediation services

A gap register is not a plan. Our SOC 2 remediation services take the register and sequence it, because fix order decides your report date more than the number of gaps does.

Most prioritisation advice ranks gaps by audit risk against engineering effort. That misses the dimension that actually controls the calendar: some gaps cannot be fixed after the fact. A log retention setting raised in month four does not produce the eleven months of logs an auditor wants to sample. An access review designed in month five leaves the earlier quarters with no artefact. Those gaps go first whatever they cost, and everything else sequences behind them.

The order we fix in

Order Gap Why it sits here Typical effort
1 MFA and single sign-on across production systems Tested in every examination, and auditors accept no compensating control for it Days
2 Offboarding and access removal Auditors sample leavers by name and date, and one live account becomes a reported exception Days to 2 weeks
3 Log and audit trail retention Has to exceed the observation window before the window opens, and no later fix recovers the missing months Hours to configure, then it has to run
4 Access review cadence An artefact must exist for every period sampled, so the first review has to land before the window starts 1 to 2 weeks to design, quarterly after
5 Change management in the deployment pipeline Needs a process change that engineering has to agree to, so it sets the overall timeline 3 to 6 weeks
6 Incident response plan and tabletop exercise The plan is quick, the rehearsal record takes calendar time to schedule 2 to 4 weeks
7 Timed restore testing Needs a scheduled test with a recorded result against a stated recovery objective 2 to 4 weeks
8 Vendor register and subservice organisation review Lower audit risk, but it waits on third parties replying, so it starts early and runs alongside everything else 4 to 8 weeks

Swipe the table sideways to see every column.

Items 1 to 4 close before the observation window opens. Items 5 to 8 run in parallel and are tested again before fieldwork. Re-testing is part of our SOC 2 remediation services, because a control that was fixed but never re-tested is still an exception waiting to be written up.

Advisory remediation and hands-on remediation

SOC 2 remediation services come in two shapes, and the difference matters more than most buyers realise:

Advisory remediation

We specify what each control has to do, review what your team builds, re-test it against the criteria and confirm the evidence will hold. Your team does the building.

Hands-on remediation

We write the policies, configure the controls and build the evidence pipeline ourselves.

Both are legitimate. They lead to different answers on who signs your report, which is the next section.

Read this before you sign anything

The independence rule most buyers find out too late

A SOC 2 report is an attestation that only a licensed CPA firm can issue. The AICPA Code of Professional Conduct also governs the other work that firm does for the same client. In short: a CPA firm may perform a SOC 2 readiness assessment or a SOC 2 gap assessment for a company it will later examine, as long as your management makes the decisions, accepts responsibility for the results and oversees the work. Once that firm starts designing, writing and operating the controls itself, it has taken on a management function, and its independence for your attestation is impaired.

This is why competitor pages carry statements that look odd until you know the rule. One large advisory firm states it does not issue reports at all. One large CPA firm states it provides no remediation or implementation services of any kind. Both are managing the same boundary from opposite sides.

EntPerMaSys Consulting tells you which side you are on in the engagement letter, before any work starts. There are two clean routes:

  Route A Route B
SOC 2 readiness assessment and gap assessment EntPerMaSys Consulting EntPerMaSys Consulting
SOC 2 remediation services Advisory only, your team builds Hands-on, we build
Who issues the report EntPerMaSys Consulting An independent CPA firm we introduce you to
Best when You have an engineering team that can execute and you want one firm from start to signed report You have no internal security owner and need the work done, not specified

Swipe the table sideways to see every column.

What we will not do is run hands-on remediation, stay silent about it and then issue your opinion. If a buyer, an investor or your customer's security team later asks who built the controls and who tested them, you need the answer to hold up.

Timeline

Timeline to a report a customer will accept

The honest answer to "how fast can we get SOC 2" depends on which report your customer will accept. Here are both paths from kickoff, assuming a single product and the Security criteria.

Stage Type 1 path Type 2 path
SOC 2 readiness assessmentWeeks 1 to 5Weeks 1 to 5
Remediation of blocking gapsWeeks 5 to 14Weeks 5 to 14
Re-test and evidence confirmationWeeks 14 to 16Weeks 14 to 16
Observation windowNot applicable3 to 12 months, commonly 3 for a first report
Examination fieldwork3 to 6 weeks3 to 6 weeks
Signed report in handMonth 4 to 6Month 8 to 11

Swipe the table sideways to see every column.

Three things that follow from that table:

  • A Type 1 report buys time, it does not replace a Type 2. Enterprise buyers increasingly accept a Type 1 with a committed Type 2 date. They rarely accept a Type 1 indefinitely.
  • Going straight to Type 2 is often the cheaper route if your customer will wait, because you pay for one examination instead of two.
  • Remediation length is the only variable that really moves. The readiness assessment and the fieldwork are fairly fixed. A company arriving with cloud infrastructure, SSO and a ticketing system already in place can be through remediation in six weeks. A company with shared admin logins and no change process takes four months, and no platform or consultant compresses that honestly.

One scheduling point competitors skip: a report is treated by most customers as current for roughly twelve months after the period it covers. If your customers are already asking, plan the second examination before the first report ages out, and use a bridge letter to cover the interval rather than letting a gap appear.

Pricing

What a SOC 2 readiness assessment costs

EntPerMaSys Consulting scopes a fixed fee after a short scoping call, so the number you receive is the number you pay. For context on the market: published ranges from US compliance platforms put a professional SOC 2 readiness assessment between $10,000 and $17,000, and Indian consultancies commonly quote readiness consulting separately from the CPA examination fee.

Eight things move the number, in rough order of weight:

  • How many Trust Services Criteria you report on. This is the largest single driver. Adding Privacy or Processing Integrity to a Security scope can change both the readiness fee and the examination fee materially.
  • How many products, environments and cloud accounts sit inside the boundary. A multi-product group costs more than one product on one account.
  • Headcount, because it sets sample sizes for access, onboarding and training controls.
  • Whether you already hold ISO 27001 or ISO 27701. Existing certification removes a large share of the Security work, and we map rather than rebuild.
  • Whether evidence is produced automatically or assembled by hand. Manual evidence collection is the main driver of effort in walkthroughs.
  • How many subservice organisations are inside the boundary, since each one needs its report reviewed and its complementary controls tracked.
  • Type 1 or Type 2.
  • Whether a prior report carried exceptions, which requires those specific controls to be re-tested more deeply.

When you compare quotes, ask every firm for two numbers in writing: the readiness and remediation fee, and the examination fee. A firm that cannot give you the second number is not the firm issuing your report, and that cost will arrive later.

About the firm

Why companies pick EntPerMaSys Consulting as their SOC 2 readiness consultant

Most firms selling SOC 2 readiness in this market are advisory practices or software vendors. Neither can sign your report. EntPerMaSys Consulting is a peer-reviewed CPA firm with offices in Wilmington, Delaware and Bengaluru, India, and it performs SOC 1, SOC 2, SOC 3 and SOC 2 Plus attestations as its core practice.

That matters in a specific way. A SOC 2 readiness consultant who has never signed an opinion is guessing at what an auditor will accept as evidence. Our engagement teams have worked on more than 120 SOC 1 and SOC 2 engagements between them, and the standard we apply in a SOC 2 gap assessment is the standard we apply when our own name is on the report.

Credentials held across the engagement team

  • CPA (USA)
  • CISA
  • CITP
  • CIPP (US)
  • CCSK
  • Chartered Accountant
  • FCMA
  • AICWA
  • DISSA
  • HITRUST CCSFP
  • CHQP
  • ISO 27001 Lead Auditor
  • ISO 27701 Lead Auditor
  • C.DPO.DA
  • HITRUST Authorized External Assessor

One firm for overlapping frameworks

If a customer wants SOC 2 and a regulator wants privacy compliance, we handle both. See our ISO 27001 and ISO 27701 consulting and privacy gap assessment and remediation work. Healthcare clients can run HITRUST readiness and validated assessments alongside SOC 2.

US and India in one engagement

Indian technology exporters need a US-licensed CPA firm for the report. Most India-based SOC 2 consultancies have to hand that work to a third party, which splits accountability and adds a vendor to your timeline. We hold both offices.

Built for startups and mid-sized companies

Our practice is aimed at companies without a full internal GRC function, where the security owner is also the CTO.

Fit

Who this page is for

We run SOC 2 readiness assessment and SOC 2 remediation services most often for:

  • A SaaS company with an enterprise contract held up pending a SOC 2 report
  • A company holding ISO 27001 that a North American buyer has now asked for SOC 2, where most of the work is mapping rather than building
  • A company whose previous report carried exceptions and needs those specific controls rebuilt before the next period
  • An Indian IT, ITES, BPO or global capability centre provider serving US and European clients
  • A health technology company where HIPAA or HITRUST requirements sit alongside SOC 2
  • A company that bought a compliance automation platform and now has a dashboard full of failing controls and nobody to close them, which is a remediation problem, not a tooling problem

Start with a scoping call

A 30 minute call with a SOC 2 readiness consultant is enough to tell you which Trust Services Criteria you actually need, which report your customer will accept, and the earliest honest date you can hold a signed report. You will get a fixed fee for the SOC 2 readiness assessment and a separate figure for the examination, both in writing. Prefer email? Write to services@entpermasys.com.

FAQ

Frequently asked questions

A SOC 2 readiness assessment is a review of your controls, policies and evidence against the AICPA Trust Services Criteria, completed before the formal examination. It produces a gap register and a remediation plan with owners and dates. It contains no auditor opinion, so it is an internal planning document rather than something you can give a customer.

A SOC 2 gap assessment identifies which controls are missing or undocumented. A SOC 2 readiness assessment contains that gap work plus scoping, walkthroughs with each control owner, evidence sampling and a dated remediation plan. The gap assessment tells you where you stand. The readiness assessment tells you how to get from there to a signed report, and by when.

No. Nothing in the AICPA standards requires one. In practice, companies that skip it for a first report usually find gaps during fieldwork, which either produces exceptions in the report or forces the examination to be rescheduled. The assessment is optional. The consequences of a failed first examination are not.

For one product reporting on the Security criteria, 3 to 5 weeks from kickoff to the remediation readout. Multiple criteria, multiple environments or a group structure takes longer. Remediation afterwards is the variable part, running from 6 weeks for a company with cloud infrastructure and single sign-on already in place to 4 months for one with shared administrator accounts and no change process.

Published ranges from US compliance platforms put a professional SOC 2 readiness assessment between $10,000 and $17,000. The number is driven mainly by how many Trust Services Criteria you report on, how many environments sit inside your boundary, your headcount and whether your evidence is produced automatically or by hand. EntPerMaSys Consulting quotes a fixed fee after a scoping call, with the examination fee stated separately.

Yes, within limits set by the AICPA Code of Professional Conduct. A CPA firm can perform a readiness or gap assessment for a company it later examines, provided your management makes the decisions, accepts responsibility for the results and oversees the work. If that firm instead writes your policies and configures your controls itself, it has taken on a management function and its independence for the attestation is impaired. Agree which arrangement applies in the engagement letter before work begins, not afterwards.

No. A readiness assessment carries no auditor opinion and is not an attestation. Only a SOC 2 Type 1 or Type 2 report, signed by a licensed CPA firm, can be given to customers, and normally under a non-disclosure agreement. If a deal needs something immediately, a Type 1 report with a committed Type 2 date is the usual answer.

Start with Type 1 if a specific deal is blocked now and your customer will accept it. Go straight to Type 2 if the customer will wait, because one examination costs less than two. A Type 1 covers control design on a single date. A Type 2 covers design and operating effectiveness across an observation window of 3 to 12 months, and most enterprise buyers eventually require it.

A useful amount, though not all of it. An ISO 27001 information security management system typically covers a large share of the Security criteria, so the work becomes mapping existing controls rather than building new ones. The gaps that remain are usually in evidence retention, the specific form of access reviews auditors sample, and the complementary controls your subservice organisations assign to you. We run this as a mapping exercise and tell you at the end of the SOC 2 gap assessment exactly which items ISO 27001 did not cover.

An exception is not a failed audit. The auditor describes it in the report along with management's response, and customers routinely accept reports containing a small number of explained exceptions. A qualified or adverse opinion is a different and much more serious outcome. The way to avoid both is to re-test every remediated control against the criteria before fieldwork opens, which is part of our SOC 2 remediation services rather than an add-on.

Yes. There is no residency requirement on the service organisation. What matters is that the report is issued by a CPA firm licensed to perform attestation engagements under AICPA standards. This is why Indian technology exporters working with a local consultancy still need a US CPA firm at the end of the process. EntPerMaSys Consulting holds offices in Wilmington, Delaware and Bengaluru, so the readiness work and the examination stay with one firm.

No, though one helps with evidence collection and continuous monitoring once your controls work. A platform shows you which controls are failing. It does not configure your identity provider, change your deployment process or rehearse your incident response plan. Companies that buy a platform first often arrive at a readiness assessment with a dashboard of red items and no plan, which is the problem SOC 2 remediation services are there to solve.

Get In Touch

No 6, Ward No 65,
Vinir Towers, BDA 1st Stage,
BTM Layout, Bengaluru,
Karnataka 560068.

500 DELAWARE AVE,
STE 1 1960, WILMINGTON,
DE 19899, USA.

© 2026 EntperMasys. Distributed By: Soumiz