Compliance · · 7 min read
SOC 2 for a small SaaS team: the evidence auditors actually ask for
By Rushit Chandegara, Founder & CTO, InfraCloudEdge
A large customer asks for your SOC 2 report, and a small engineering team has to work out what that means. SOC 2 is less about specific tools than about showing, with evidence, that you do what your policies say. Here is what auditors actually look for.
Type I or Type II
A Type I report checks that your controls are designed properly at a single point in time. A Type II report checks that they actually operated over a period, commonly three to twelve months. Many customers accept a Type I first, as long as a Type II is on the way.
The trust services criteria
Security is required in every SOC 2 report. Availability, Confidentiality, Processing Integrity and Privacy are optional; include only the ones your customers need and you can evidence.
Evidence auditors commonly request
- Access reviews: who has access to production, the cloud console and code, reviewed on a schedule, with removals recorded.
- Onboarding and offboarding: accounts created on joining and removed promptly on leaving.
- Change management: code review and approval before changes reach production, with the history to prove it.
- Backups: taken on schedule, and restores actually tested.
- Monitoring and incident response: alerts, a written process, and records of real incidents.
- Risk assessment and vendor reviews, repeated at least yearly.
- Policies employees have read and accepted.
Where AWS helps
- CloudTrail records who did what in the account.
- AWS Config and Security Hub show configuration drift and failed best-practice checks.
- GuardDuty provides threat detection without running agents.
- IAM Identity Center gives named users with single sign-on instead of shared logins.
- Keyless CI/CD with OIDC removes long-lived deployment keys.
Tooling is optional
Compliance automation platforms collect evidence for you and can save time, but they are not required. A team can keep evidence, owners and due dates in the systems it already uses, as long as every control has an owner and every piece of evidence has a date.
Common mistakes
- Writing policies the team does not follow; auditors test what you do, not what you wrote.
- Shared accounts and credentials, which make access impossible to evidence.
- Calling the company "SOC 2 compliant" before the auditor has issued a report.
