Information Security | SOC 2 Compliance
SOC 2 Compliance Checklist: The Controls Indian Companies Actually Need
Most SOC 2 checklists circulating online are vendor lead magnets dressed as guidance. They list forty items, nine of which are the vendor's own product, and none of which map cleanly to what an auditor will actually test. If you are preparing for a first SOC 2 engagement from India, the more useful exercise is to work backwards from the structure the auditor uses, because that structure is public and it has not changed in years.
SOC 2 rests on the AICPA Trust Services Criteria. There are five: Security, Availability, Processing Integrity, Confidentiality and Privacy. Security is mandatory and is referred to as the common criteria. The other four are optional, included only if they are relevant to the service commitments you make to customers. Teams familiar with ISO 27001 often expect a fixed control list like Annex A, and are unsettled to find that SOC 2 does not prescribe controls at all. It describes criteria, and you design controls that meet them. Understanding the trust criteria before you start building is what prevents six months of work on the wrong things.
Table of Contents
Decide scope before you decide controls
Three scope decisions drive everything downstream, and getting them wrong is the most expensive mistake available to a first-time applicant.
The first is which criteria to include. Adding Availability, Confidentiality or Privacy because it sounds impressive adds real audit effort and real control obligations. Include a category only if customers ask for it or your contracts commit to it.
The second is Type 2 or Type 1. A Type 1 report assesses whether controls are suitably designed at a single point in time. A Type 2 assesses whether they operated effectively across a period, usually between three and twelve months. Enterprise buyers increasingly accept nothing but Type 2, so a Type 1 is best understood as an interim artefact rather than a destination.
The third is the system boundary. SOC 2 applies to a defined system, not to your company. Drawing the boundary around the production platform that serves customers, rather than around every laptop and internal tool your business owns, keeps the audit proportionate.
The common criteria, and what each one really asks
The common criteria run from CC1 to CC9 and are organised around the COSO internal control framework. Here is what each series asks for in practice.
CC1, control environment. Governance and people. Board or leadership oversight of security, defined security roles, background verification at hiring, a code of conduct, and annual security awareness training with evidence of completion.
CC2, communication and information. Internal and external communication of security responsibilities. Published policies that staff can actually find, a security page or trust centre for customers, and a channel for reporting concerns.
CC3, risk assessment. A documented risk assessment performed at least annually, covering fraud risk and significant change. Auditors look for a risk register with owners, ratings and treatment decisions, not a one-off spreadsheet from two years ago.
CC4, monitoring activities. Evidence that you check your own controls, through internal audit, control self-assessment or automated monitoring, and that findings get remediated and tracked.
CC5, control activities. The link between identified risks and the controls selected to address them, including technology controls and segregation of duties.
CC6, logical and physical access. The largest series, and where most findings originate. Joiner, mover and leaver processes with evidence of timely deprovisioning, multi-factor authentication, least privilege, quarterly access reviews, encryption in transit and at rest, and physical controls for any office or data centre in scope.
CC7, system operations. Vulnerability management, logging and monitoring, intrusion detection, and incident response. Auditors expect periodic VAPT with evidence that findings were remediated on a defined timeline, plus an incident response plan that has been tested rather than merely written.
CC8, change management. Changes to infrastructure and application code are authorised, tested, reviewed and documented. For most engineering teams this means demonstrating pull request review, separation between development and production, and an approval trail.
CC9, risk mitigation. Business disruption and vendor risk. Vendor inventory, risk-based due diligence, contractual security terms and periodic reassessment of critical suppliers.
What auditors actually ask Indian companies for
| Area | Evidence typically requested | Where first-timers fail |
|---|---|---|
| Access reviews | Quarterly review records with reviewer, date, action taken | Reviews performed but never documented |
| Offboarding | Ticket and system logs showing revocation within policy SLA | Contractor accounts left active |
| Change management | Sample of change tickets with approval and test evidence | Hotfixes pushed outside the process |
| Vulnerability management | Scan reports plus remediation tracking against SLA | Findings identified, closure not evidenced |
| Risk assessment | Dated risk register with treatment owners | Last updated before the audit period began |
| Vendor management | Vendor list, risk ratings, security reviews | Subprocessors never assessed |
| Training | Completion records for all in-scope personnel | Missing records for joiners mid-period |
| Policies | Approved, versioned, communicated | Approved the week before fieldwork |
The pattern is consistent. Indian technology companies usually have reasonable controls operating. What they lack is contemporaneous evidence that the controls operated throughout the audit window, and evidence cannot be created retrospectively for a Type 2 period.
When to add the optional categories
Security alone satisfies a surprising number of enterprise buyers, so the decision to add categories should be driven by contracts rather than ambition.
Availability belongs in scope when you publish an uptime commitment or sign service level agreements with credits attached. It brings obligations around capacity planning, monitoring, backup and recovery testing, and a disaster recovery exercise your auditor can inspect. Teams that have never tested a restore should expect this category to surface uncomfortable findings.
Confidentiality applies when customers entrust you with information they classify as confidential and expect defined handling and disposal. The controls centre on classification, retention schedules and secure deletion, including deletion from backups and analytics copies. It is lighter than Availability for most SaaS businesses.
Processing Integrity is narrow and often misapplied. It concerns whether system processing is complete, valid, accurate, timely and authorised. It matters for payment processing, payroll, claims adjudication and similar transactional services. It is rarely relevant to a collaboration tool, and including it without reason simply adds testing.
Privacy is the heaviest addition, covering notice, choice, collection, use, retention, disclosure, access and quality for personal information. Indian companies that already run a privacy programme for the DPDP Act or the GDPR will find meaningful overlap. Those that do not should finish Security first.
Evidence collection is the real project
The single biggest determinant of how a first Type 2 goes is whether evidence accumulates by itself or has to be hunted for. Controls that produce their own artefacts survive audit. Controls that depend on somebody remembering to save a screenshot do not.
In practice this means pushing control execution into systems that log. Access reviews run through a ticketing workflow leave a record. Access reviews conducted in a meeting do not. Change approvals captured in a pull request leave a record. Changes approved over chat do not. Vulnerability remediation tracked against a dated SLA leaves a record, while remediation confirmed verbally leaves an auditor with nothing to sample.
Compliance automation platforms help here, though they are frequently oversold. They are effective at continuous evidence collection from cloud infrastructure and identity providers. They are considerably less effective at the governance criteria in CC1 to CC5, which still require human judgment, documented decisions and real meetings. Buying a tool and assuming it delivers a report is the most common way Indian startups lose a quarter.
A realistic sequence
- Confirm scope, criteria and audit window, and write a system description covering infrastructure, software, people, procedures and data.
- Run a gap assessment against the common criteria rather than a vendor template.
- Remediate the access management and change management gaps first, since these generate the highest volume of exceptions.
- Stand up evidence collection before the window opens, so logs, tickets and review records accumulate naturally.
- Complete a penetration test and close findings before the period starts, not during it.
- Operate the controls for the full observation period without exception, resisting the temptation to shorten it.
- Engage the CPA firm early, since availability is constrained and the fieldwork date shapes everything.
Budget and timeline
A first Type 2 report typically takes six to nine months in India from kickoff to issued report, assuming a three month observation window. Readiness and remediation consume most of that. The direct audit cost is only part of the total, with readiness consulting, penetration testing, tooling and internal engineering effort usually exceeding the auditor's fee.
One point of confusion worth settling. SOC 2 is an attestation performed by a licensed CPA firm, not a certification issued by a registrar. You receive a report containing management's assertion, the auditor's opinion, a system description and the detailed tests performed. There is no certificate to frame, and any provider promising one does not understand the standard.
Final Thoughts
Where remediation requires hands-on security work, our cybersecurity team supports implementation alongside readiness, so the gap register turns into closed items rather than a longer document. To scope a SOC 2 programme for your organisation, speak to our consulting team for a readiness assessment and a defensible timeline.
Frequently Asked Questions
Is there an official SOC 2 checklist published by the AICPA?
No. The AICPA publishes the Trust Services Criteria, which describe outcomes rather than prescribing controls. Any checklist you find is someone's interpretation of those criteria, which is why the criteria themselves are the better starting point.
How many controls does SOC 2 require?
There is no fixed number. Organisations typically design between sixty and a hundred and twenty controls to satisfy the common criteria, depending on system complexity and which optional categories are in scope.
Do we need ISO 27001 before SOC 2?
No, they are independent. That said, an operating ISO 27001 management system covers a large share of the common criteria, and companies holding it generally reach SOC 2 readiness faster.
How long must the Type 2 observation period be?
Commonly three to twelve months. First reports often use three months to reach the market sooner, with subsequent annual reports covering twelve.
Can an Indian firm issue the SOC 2 report?
The report must be issued by a licensed CPA firm. Indian companies typically engage a US CPA firm, or an Indian practice affiliated with one, and the work is usually performed remotely.
What happens if the auditor finds exceptions?
Exceptions are disclosed in the report rather than causing failure. A report with explained, remediated exceptions remains usable, though a clean opinion is obviously preferable in enterprise sales.








