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 differA 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.
On this page
- What a SOC 2 readiness assessment is
- Readiness, gap assessment and the examination compared
- What a SOC 2 gap assessment delivers
- Where first-time gaps concentrate
- How the engagement runs
- SOC 2 remediation services
- The independence rule
- Timeline to a signed report
- What it costs
- Why EntPerMaSys Consulting
- Who this page is for
- Frequently asked questions
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.
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.
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.
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.
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.
Control mapping matrix
Every control you already run, mapped to the criterion it satisfies, with the owner named.
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.
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.
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.
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.
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.
Scoping and criteria selection
3 to 5 business daysWe 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.
Control mapping
3 to 5 business daysYour 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.
Walkthroughs and evidence sampling
5 to 10 business daysWe 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.
Gap register
3 to 5 business daysFindings written up, rated and split into design gaps and evidence gaps.
Remediation plan and readout
2 to 3 business daysA 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.
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.
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 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 assessment | Weeks 1 to 5 | Weeks 1 to 5 |
| Remediation of blocking gaps | Weeks 5 to 14 | Weeks 5 to 14 |
| Re-test and evidence confirmation | Weeks 14 to 16 | Weeks 14 to 16 |
| Observation window | Not applicable | 3 to 12 months, commonly 3 for a first report |
| Examination fieldwork | 3 to 6 weeks | 3 to 6 weeks |
| Signed report in hand | Month 4 to 6 | Month 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.
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.
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.
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.