This guide is general information, not legal or audit advice. Confirm requirements with your auditor or counsel.
What a SOC 2 compliance checklist needs to cover
A SOC 2 compliance checklist is the list of controls, documents and recurring activities you need running so that a licensed CPA firm can test them against the AICPA Trust Services Criteria and issue a report. For most startups the report covers the Security category, which is made up of the common criteria CC1 to CC9, and sometimes Availability or Confidentiality.
Two things surprise first-time teams. First, SOC 2 is an attestation, not a certification. Nobody "passes" SOC 2: the auditor gives an opinion and lists any exceptions found while testing. Second, the work is mostly about dated proof. A well-written access control policy earns very little if you cannot show the quarterly access review that it promises, with names, dates and the accounts you removed.
- Type I tests whether your controls are suitably designed and in place on one date.
- Type II tests whether they operated effectively across a period, usually 3 to 12 months. The auditor samples evidence from across that window.
Step zero: decide what your SOC 2 report will cover
Scope decisions drive cost and effort more than anything else on this checklist. Settle them in writing before you write a single policy.
- Report type and date. Look at the deals that are asking. If a customer needs something this quarter, a Type I followed by a Type II is common. If you have time, go straight to a Type II with a three to six month first period.
- Trust Services Criteria. Security is always in. Add Availability if you sign uptime SLAs, and Confidentiality if customers send you data under NDA. Processing Integrity suits payment or data-processing products. Privacy is heavy, and B2B startups rarely choose it.
- System boundary. Name the product, the production cloud accounts, the code repositories, the identity provider and the teams that run them. Your marketing website and internal finance tools are usually out.
- Subservice organisations. AWS, Google Cloud or Azure run your data centres. They are normally "carved out", which means the auditor relies on their own SOC reports and you review those reports once a year.
Evidence to keep: a one-page scope note listing the above, approved by a founder or the CTO, plus a first draft of the system description. That draft becomes the section of the report that describes your services, infrastructure, software, people, data and procedures.
The SOC 2 compliance checklist, step by step
Work through these in order. Each item lists the evidence an auditor typically requests. For a Type II, assume they will pick samples from across the whole period, so the evidence has to exist every month, not only at the end.
Governance and risk (CC1 to CC3)
- Name an owner for the programme and for every control. Evidence: a control list with owners, and leadership meeting notes that approve the security programme.
- Publish an org chart and security responsibilities. Evidence: a dated org chart and job descriptions that mention security duties for engineering and operations roles.
- Run a risk assessment and keep a risk register. Rate likelihood and impact, decide a treatment, and include fraud risk, which the criteria call out separately. Evidence: the register with owners and dates, and a record that leadership reviewed it at least once a year.
Policies and people (CC1, CC2)
- Approve the core policy set. Information security, acceptable use, access control, change management, incident response, business continuity and disaster recovery, vendor management, data classification and retention, encryption, and secure development. Evidence: each policy with a version, approver and approval date that falls before the audit period starts.
- Collect acknowledgements. Every employee and contractor accepts the policies at joining and every year. Evidence: a per-person record with the date and the policy version accepted. A shared Slack message is not evidence.
- Complete background verification before access. Most Indian teams use a BGV vendor for employment, education and address checks. Evidence: completed reports for a sample of joiners in the period, including contractors.
- Run security awareness training. At onboarding and annually. Evidence: completion records by name and date.
- Formalise joining and leaving. Access is granted only on an approved request and removed within a set time of the last working day. Evidence: tickets for joiners and leavers. Auditors compare HR exit dates with the deactivation dates in Google Workspace or Microsoft Entra ID, AWS and GitHub.
Access control (CC6)
- Enforce SSO and MFA on every in-scope system. Evidence: identity provider settings showing MFA is enforced, and a user list with MFA status.
- Restrict production access. Use roles, keep admin rights to a few named people, and protect the cloud root account with MFA and no access keys. Evidence: IAM role and user exports, and approval tickets for privileged access.
- Review access every quarter. For each critical system, a reviewer confirms every account is still needed. Evidence: the review output with reviewer, date and decision per account, plus the closed tickets for every removal.
- Manage secrets properly. No credentials in code or shared spreadsheets. Evidence: secrets manager configuration and a secret-scanning setting on your repositories.
Keep this checklist running between audits
BeAuditReady turns each step into a control with an owner, evidence with an expiry date, and daily read-only checks on AWS, GitHub and Google Workspace. Expired evidence opens a task for its owner.
Infrastructure and code (CC6 to CC8)
- Encrypt data at rest and in transit. Evidence: configuration exports for databases, storage buckets, disks and load balancer TLS settings.
- Log and alert. Cloud audit logging on in all regions, logs retained for a defined period, and alerts for risky events such as root logins or security group changes. Evidence: logging configuration, alert rules, and a few alert tickets showing someone responded.
- Scan for vulnerabilities and test once a year. Evidence: dependency and infrastructure scan reports, an annual penetration test report, and remediation tickets closed within the timelines your policy sets for each severity.
- Control changes. Branch protection on the main branch, at least one reviewer who is not the author, automated tests in CI, and a written emergency change process. Evidence: branch protection settings and a sample of merged pull requests with approvals.
- Secure laptops. Disk encryption, screen lock, OS updates and antivirus or endpoint protection. Evidence: an MDM report or signed device attestations for each person.
- Back up and test a restore. Evidence: backup configuration and a dated restore test with the result. A backup nobody has ever restored is a common readiness gap.
Operations (CC7, CC9 and Availability)
- Prepare for incidents. An incident response plan, an on-call path, and one tabletop exercise a year. Evidence: the plan, tabletop notes with actions, and the incident log for the period.
- Manage vendors. A register of vendors that touch customer data, a risk tier for each, and an annual review of critical vendors, including their SOC reports. Evidence: the register and review notes.
- Test continuity. A business continuity and disaster recovery plan tested at least once a year. Evidence: the test report with recovery times achieved.
- Communicate commitments. Security and availability commitments in your customer contract, a status page or support channel, and a way for customers to report security issues. Evidence: the contract template and the published contact route.
The audit itself
- Run a readiness review. Walk every control against this list and fix the gaps before the period starts. Evidence: the gap list with owners and closure dates.
- Choose the auditor and fix the period. Get two or three quotes, agree the criteria, the system boundary and the start and end dates in the engagement letter.
- Answer the request list. The auditor sends a request list, often 100 to 200 items. Name an owner for each request and a due date.
- Review the draft report. Check the system description is accurate, respond to any exceptions with a management response, and sign the management assertion.
A SOC 2 checklist for startups with a small team
A SOC 2 checklist for startups is the same list with fewer people to share it. The criteria do not change with headcount, but the auditor expects controls sized to the company. Here is what that looks like in practice.
- Keep the policy set short. Ten clear policies of two to four pages each are easier to follow and defend than a 90-page manual copied from a template pack.
- Segregation of duties still matters. With four engineers, one person still cannot write, approve and deploy their own change. If a founder has to approve admin access they also hold, write down a compensating control, such as a monthly review of admin actions by a second person.
- Use what your cloud already gives you. Native audit logging, managed backups and built-in encryption usually cover several criteria without buying anything new.
- Do not skip the boring recurring work. Offboarding, access reviews and pull request approvals produce more exceptions than any technical control. Put them on a calendar with an owner.
- Count contractors. Freelance developers and agency staff with production access are in scope for background checks, acknowledgements, training and offboarding.
SOC 2 timeline and typical cost for a startup
These are typical ranges for an Indian SaaS company of 20 to 150 people on a single cloud. Your numbers will vary with scope, the state of your controls and the firm you choose.
| Phase | Typical duration | What happens |
|---|---|---|
| Readiness | 6 to 12 weeks | Scope, policies, gap fixes, evidence set up |
| Type I fieldwork | 2 to 4 weeks | Auditor tests design on the report date |
| Type II observation | 3 to 12 months | Controls run; you keep evidence every month |
| Type II fieldwork and report | 4 to 8 weeks after period end | Sampling, draft report, management response |
On cost, auditor fees depend on the firm, the number of criteria and systems, and whether it is a Type I or Type II. Smaller firms that serve Indian startups commonly quote in the low lakhs of rupees for a narrow Type I, with a Type II costing more; large international firms charge well above that. Budget separately for an annual penetration test, any compliance software, and the real cost: engineering time to close gaps. Ask every auditor for a written quote that names the criteria, the period and the number of systems.
Where SOC 2 audits usually find exceptions
Exceptions are not fatal, but customers read them. These are the ones that come up again and again.
- A leaver whose GitHub or AWS account stayed active for weeks after the last working day.
- An access review marked complete, with no evidence that the accounts flagged for removal were removed.
- Pull requests merged by an admin who bypassed branch protection.
- Policies approved after the audit period had already started.
- Contractors with production access and no background check or training record.
- A disaster recovery plan that was written but never tested.
- Critical vendors with no review in the past year.
After the report: keeping SOC 2 current
Customers treat a SOC 2 report as fresh for about a year. Most companies run back-to-back Type II periods, so the next period starts the day after the last one ended. When a customer asks during the gap between your period end and the next report, your management can issue a bridge letter (sometimes called a gap letter) stating that nothing material has changed since the period ended.
Plan for the recurring calendar: quarterly access reviews, annual policy reviews and acknowledgements, annual training, an annual penetration test, a yearly risk assessment and vendor review, and a restore test. If you also sell to enterprises that ask for ISO 27001, most of this evidence carries over; see our guide to ISO 27001 certification in India.
For how BeAuditReady maps these controls and keeps the evidence current, see the security compliance page.