← All insights

SOC 2

SOC 2: the do's and don'ts

Lessons from both sides of the audit table — what helps a SOC 2 report land cleanly, and what quietly sinks it.

Trigun Advisory · October 2026 · 8 min read

For B2B SaaS and service companies selling to enterprises, a SOC 2 report has become close to mandatory. Procurement teams ask for it before signing and again before renewal. It is an attestation report issued by an independent CPA firm under AICPA standards, assessing your controls against the Trust Services Criteria: Security (always required), plus Availability, Processing Integrity, Confidentiality and Privacy where relevant.

A Type 1 report looks at whether controls are suitably designed at a point in time. A Type 2 report tests whether they operated effectively over a period — typically three to twelve months. Customers usually want Type 2.

We have worked on SOC 2 from both sides: helping organisations prepare, and partnering with CPA firms on the examination itself. These are the patterns we see again and again.

The do's

Do start with the customer question

Ask what your customers actually need. Which product or service are they relying on? Which criteria beyond Security matter to them — Availability for an uptime-critical platform, Confidentiality for sensitive business data? A tight, relevant scope produces a more useful report at lower cost.

Do write a system description that reflects reality

The system description is the part of the report customers actually read. It should describe your real infrastructure, software, people, procedures and data flows, and clearly identify subservice organisations (such as your cloud provider) and whether they are carved out. Auditors test against it, so anything aspirational becomes an exception.

Do design controls your teams can operate every month

A Type 2 tests operation over time. A quarterly access review that happens three times out of four is an exception. Design controls with the frequency and evidence trail your teams can sustain, and automate evidence collection where possible.

Do run a readiness assessment before the window starts

Close design gaps before the observation period opens, not during it. A readiness review — ideally by someone who thinks like the auditor — catches missing controls, weak evidence and documentation that doesn't match practice.

Do review evidence monthly during the Type 2 window

Don't wait for fieldwork to discover a missed review in month two. A monthly evidence check through the observation period turns would-be exceptions into fixable issues.

Do map once, report many times

Most SOC 2 controls overlap heavily with ISO 27001, and increasingly with privacy requirements like India's DPDP Act. Build one control framework and map it across frameworks so the same evidence serves multiple reports.

Do define complementary user entity controls clearly

Some controls depend on your customers — managing their own users, protecting their credentials. State these complementary user entity controls (CUECs) clearly so responsibilities are understood on both sides.

The don'ts

Don't buy a policy pack and call it done

Generic policies describing controls you don't run are the fastest route to exceptions. Auditors test what the policy says you do. Fewer, accurate policies beat a thick binder.

Don't let the tool become the programme

Compliance automation platforms are useful for collecting evidence, but they don't decide your scope, design controls around your architecture or answer an auditor's follow-up questions. Someone still has to own the programme.

Don't ignore people controls

Background checks, onboarding and offboarding, security awareness training and timely access removal for leavers are some of the most frequent sources of exceptions — and they sit with HR and IT, not just engineering.

Don't forget your vendors

You are expected to monitor the subservice organisations and vendors you rely on — collecting their SOC reports, reviewing them and following up on exceptions and their CUECs. "Our cloud provider is SOC 2 compliant" is not a control.

Don't treat change management as paperwork

Auditors sample changes to production. Every change needs evidence of review and approval — and emergency changes need a documented path, not an exemption.

Don't confuse the adviser with the auditor

Your SOC 2 auditor must be independent. The firm that designs your controls should not be the firm that issues the opinion on them. Keep the roles separate — it protects the credibility of your report.

Don't let the report lapse

A SOC 2 report covers a specific period. Plan the next period so there are no gaps in coverage, and provide a bridge letter to customers between reports. An expired report raises the same procurement questions as having none.

The short version: scope it to what customers need, describe what you actually do, operate controls consistently and check the evidence before the auditor does.
Schedule a meeting