Blog News Contact Get a proposal

SOC 2 Readiness Assessment

Choose the Trust Services Criteria and the report type, then answer up to 40 questions. See your readiness by section, the top 5 gaps, what to close first and how long it will take to get the report, then get the full report as a PDF.

Runs in your browser, nothing is sent until you ask for the PDFFreeNo signup
Report type you are aiming for

For Type I, questions about evidence over time are set to N/A. You can change any answer.

Trust Services Criteria in scope

Security is always in scope. Add the other criteria your customers ask for: their questions appear below.

Security: governance, risk and policies

CC1–CC5

  1. Is a person named as owner of the security program, with management reviewing it at least once a year?

    CC1.2, CC1.3 · high impact
  2. Do you have written and approved security policies: information security, access, change, incident response, vendor management?

    CC5.3 · high impact
  3. Do employees and contractors accept the policies and a code of conduct when they join and every year?

    CC1.1, CC2.2 · medium impact
  4. Does everyone complete security awareness training on hire and yearly?

    CC1.4, CC2.2 · medium impact
  5. Are background checks done for new hires, where the law allows them?

    CC1.4 · medium impact
  6. Is there a documented risk assessment, with a risk register and owners, updated at least yearly?

    CC3.1–CC3.4 · high impact
  7. Do you have a current system description: architecture, data flows and the system boundary for the audit?

    CC2.1, CC2.3 · medium impact
Security: logical and physical access

CC6

  1. Is MFA enforced on the identity provider, cloud consoles, code repositories and admin panels?

    CC6.1 · high impact
  2. Is access granted by role on request with approval, and removed within one business day after someone leaves?

    CC6.2, CC6.3 · high impact
  3. Have quarterly user access reviews been done and documented for the last 3 months or longer?

    CC6.2, CC6.3 · high impact
  4. Is customer data encrypted at rest and in transit (TLS 1.2+), with keys managed in a KMS?

    CC6.1, CC6.7 · medium impact
  5. Is production protected by network rules: firewalls or security groups, no public databases, a bastion or VPN for admin access?

    CC6.6 · medium impact
  6. Are company laptops managed: disk encryption, screen lock, OS updates and endpoint protection?

    CC6.8 · medium impact
  7. Is physical access to offices and data centers controlled, or covered by your cloud provider's SOC 2 report?

    CC6.4 · lower impact
Security: monitoring and incident response

CC7

  1. Are logs from production, the cloud account and the identity provider centralized, kept for at least a year and covered by alerts?

    CC7.2 · high impact
  2. Do you scan for vulnerabilities and fix critical and high findings within defined deadlines?

    CC7.1 · high impact
  3. Has an independent penetration test been done in the last 12 months, with the findings fixed?

    CC4.1, CC7.1 · medium impact
  4. Do you have an incident response plan with roles, severity levels and customer notification steps?

    CC7.3–CC7.5 · high impact
  5. Was the incident response plan tested in a tabletop exercise, and are real incidents logged with a post-mortem?

    CC7.4 · medium impact
  6. Has every control produced evidence for at least 3 months: tickets, reviews, logs, screenshots?

    CC4.1, CC4.2 · medium impact
Security: change management and vendors

CC8–CC9

  1. Does every production change go through a pull request with peer review and passing tests before deployment?

    CC8.1 · high impact
  2. Are development, staging and production separated, with no production data in test environments?

    CC8.1 · medium impact
  3. Are infrastructure changes made through code (Terraform or similar) and reviewed like application code?

    CC8.1 · medium impact
  4. Is there a documented emergency change process with a review after the fact?

    CC8.1 · medium impact
  5. Do you keep a list of vendors with access to your data, and review their SOC 2 reports or security answers?

    CC9.2 · high impact
  6. Do you have business continuity and disaster recovery plans with defined RTO and RPO?

    CC9.1 · medium impact
Availability

A1

  1. Do you monitor uptime and capacity, with alerts and an on-call rotation?

    A1.1 · high impact
  2. Are backups automated, encrypted and stored in another region or account?

    A1.2 · high impact
  3. Was a backup restore or a disaster recovery failover tested in the last 12 months?

    A1.3 · high impact
  4. Do you publish uptime commitments (SLA) and a status page for customers?

    A1.1 · lower impact
Processing Integrity

PI1

  1. Are inputs validated and processing errors detected, logged and corrected?

    PI1.2, PI1.3 · high impact
  2. Do you reconcile outputs against inputs for critical processes like billing, payments or data exports?

    PI1.4 · medium impact
  3. Are processing specifications documented: what the system must do, with what accuracy and in what time?

    PI1.1 · medium impact
Confidentiality

C1

  1. Is confidential data classified and labeled, with handling rules per class?

    C1.1 · high impact
  2. Is confidential data deleted on schedule and at contract end, with proof of deletion?

    C1.2 · high impact
  3. Do employees and vendors with access to confidential data sign NDAs?

    C1.1 · medium impact
Privacy

P1–P8

  1. Is there a published privacy notice, and is consent collected where it is required?

    P1.1, P2.1 · high impact
  2. Do you collect and use only the personal information needed for the stated purposes?

    P3.1, P4.1 · high impact
  3. Can users access, correct and delete their personal information within set deadlines?

    P5.1, P5.2 · medium impact
  4. Are disclosures to third parties documented, and are privacy incidents reported to users and regulators?

    P6.1–P6.7 · medium impact

This assessment is not an audit and not legal advice. Only a licensed CPA firm can issue a SOC 2 report. Use the result to plan the work before you talk to an auditor. Your answers stay in your browser until you request the PDF.

Full gap report to your inbox

PDF with readiness by section, every gap with its SOC 2 criterion and a recommendation, a 3-step roadmap, the estimated time to the audit report and the next step. We send it once, no newsletter.

Need help getting SOC 2 ready?

We prepare SaaS products for SOC 2: policies and risk assessment, access control, logging and monitoring, secure SDLC, penetration tests and evidence collection. Send us your report or a short brief and we will reply within one business day.

TL;DR: SOC 2 readiness comes down to the Security criteria that every report includes, plus the optional Availability, Processing Integrity, Confidentiality and Privacy criteria your customers ask for. The assessment above checks up to 40 controls, scores your readiness by section, shows the five gaps to close first and estimates how long it will take to get a Type I or Type II report.

What does the example result look like?

Press “Load an example” above. It fills the answers of a typical B2B SaaS startup with Security and Availability in scope that aims for Type II: MFA, encryption and pull-request reviews are in place, but there is no risk assessment, no vendor review and no tested restore, and access reviews have not started. The readiness is about 60%, and the estimate to the Type II report is 6 to 12 months.

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

A Type I report says that your controls are designed properly and are in place on a specific date. A Type II report says that the controls worked over a period, usually 3 to 12 months, and the auditor tests samples from that period. Enterprise customers usually ask for Type II, but a Type I report is a common first step that unblocks deals sooner.

Which Trust Services Criteria should be in scope?

Security, also called the Common Criteria, is mandatory. Add Availability if customers depend on your uptime, Confidentiality if you store their confidential business data, Processing Integrity if you process transactions or calculations for them, and Privacy if you handle personal information of end users. Each extra criterion adds controls and audit cost, so choose what your customers really ask for.

How long does it take to get SOC 2 compliant?

For a startup with basic cloud hygiene, preparation takes 2 to 6 months. A Type I report can follow within 1 to 2 months. A Type II report needs an observation window of at least 3 months, usually 6, and then 4 to 8 weeks for fieldwork and the report. The estimate above uses the weight of your open gaps and the report type you chose.

How is the readiness score calculated?

Every control has a weight from 1 to 3 by its impact. “Yes” counts in full, “Partly” counts as half and “No” counts as zero. “N/A” and criteria outside your scope are excluded and do not lower the score. Gaps are sorted by weight, so high-impact items go to the first 30 days of the roadmap.

What should a startup do first to prepare for SOC 2?

Name an owner, write a short policy set, run a risk assessment and enforce MFA and access control on every system with customer data. Then set up centralized logging, vulnerability scanning and reviewed pull requests, list your vendors and start collecting evidence. A compliance automation platform and an early readiness review with the auditor save months.

FAQ

Is SOC 2 a certification?

No. SOC 2 is an attestation report issued by a licensed CPA firm under the AICPA standards. There is no official SOC 2 certificate: you get a report that you share with customers under NDA.

Is SOC 2 mandatory?

No law requires SOC 2. Customers ask for it, especially enterprise buyers in the US, as proof that you protect their data. Without a report, security reviews take longer and some deals stall.

Should we start with Type I or Type II?

If a deal needs a report soon, start with Type I and plan Type II right after it. If you have time, many companies go straight to Type II with a short first observation window of 3 months.

Which Trust Services Criteria do we need?

Security is always required. Most SaaS companies add Availability and Confidentiality. Processing Integrity and Privacy are chosen less often, when customers rely on your calculations or you handle a lot of personal data.

How much does a SOC 2 audit cost?

The audit fee depends on the firm, the scope and the report type. For a small SaaS company a Type I audit usually costs less than a Type II, and readiness work, tooling and a penetration test add to the budget. Ask two or three auditors for quotes on your scope.

What does “N/A” mean in the assessment?

Choose N/A when a control does not apply to you, for example office access when the team is fully remote. N/A answers and criteria outside your scope are excluded from the score.

Is this assessment a SOC 2 audit?

No. It is a self-assessment that helps you find gaps and plan the work. It is not an audit and not legal advice, and only a licensed CPA firm can issue a SOC 2 report.

Related tools