The real reasons
1. Sales. A large customer sends a security questionnaire with hundreds of questions. Questions like "Do you have a SOC 2 Type II?" or "Are you ISO 27001 certified?" come early. A "no" can end the deal or add months of extra review. A report or certificate answers most of the questionnaire in one document.
2. Law. Privacy and health laws apply on their own. Fines, regulator orders and public breach notices are the cost of ignoring them.
3. Contracts. Customers write requirements into the agreement: keep your SOC 2 current, notify us of breaches within a set time, let us audit you.
4. Insurance and investors. Cyber insurers ask about MFA, backups and incident response before pricing a policy. Investors ask in due diligence.
5. It makes the company safer. Done properly, the controls do reduce risk. Done badly, it is paperwork.
Who uses what
| Situation | Usually asked for |
|---|---|
| SaaS selling to US businesses | SOC 2 Type II |
| Selling to Europe, the Middle East, Asia, government | ISO 27001 |
| Indian IT services for global clients | ISO 27001, often SOC 2 too |
| Payroll, billing, payments | SOC 1, and often SOC 2 |
| US healthcare vendors | HIPAA compliance, BAA, often HITRUST |
| Any company with EU users | GDPR |
| Any company with Indian users | DPDPA |
Even the giants publish theirs
AWS, Microsoft Azure and Google Cloud publish their own SOC 1, SOC 2, SOC 3 and ISO 27001 reports and certificates:
- AWS Artifact
- the Microsoft Service Trust Portal
- the Google Cloud compliance reports manager
A customer of theirs can download them. It is a good first look at what a real report contains.
Compliance is usually bought by the sales team and paid for by the security team.
1. What most often drives a startup's first SOC 2?
2. An Indian IT services firm bidding for a European client is most likely asked for...
3. Where can an AWS customer download AWS's own SOC 2 report?