Can You Get SOC 2 Without a Compliance Platform?
ISO Cloud Consulting editorial team
Yes. You can get SOC 2 without a compliance-automation platform, because only a licensed CPA firm issues the report and auditors accept well-organized evidence from any source. A platform saves time on evidence collection and monitoring. Whether it is worth paying for depends on your size, stack complexity, internal capacity and how many frameworks you need.
Key facts
- SOC 2 is an attestation report by a licensed CPA firm; no software vendor can issue it.
- The Trust Services Criteria (61 criteria, Security always in scope) do not require any particular tool.
- Auditors test controls and evidence, whatever system the evidence comes from.
- A Type 2 requires evidence across a period, commonly 3 to 12 months, so collection is a recurring task either way.
What does a compliance platform actually do?
A compliance-automation platform connects to your cloud, identity, code and HR systems, pulls evidence automatically and flags controls that fail. It also usually provides policy templates, a control library, task tracking and a portal for your auditor.
The real value is continuous monitoring. Instead of discovering in month five that someone disabled MFA in month two, you get an alert the same day. For a Type 2, that can be the difference between a clean control and an exception. Platforms also give you one place to track tasks, which helps when several people share the work.
What does a compliance platform not do?
A platform does not run your controls, make security decisions or issue the report. Someone still has to review access, triage vulnerabilities, approve changes, train staff and answer the auditor.
- It does not write a system description that matches your real architecture without significant input from you.
- It does not tailor generic policies to your processes; you still edit and approve them.
- It cannot see controls that live outside its integrations, such as manual reviews, physical security or some HR steps.
- Green dashboards are not an audit opinion. The CPA firm forms its own view.
When is a compliance platform worth it?
A platform is usually worth it when evidence collection would otherwise eat significant engineering time, or when you need several frameworks at once.
- Many systems: multiple cloud accounts, dozens of SaaS tools, several code repositories.
- Fast growth: frequent hiring and offboarding, where automated checks catch slips.
- Multiple frameworks: SOC 2 plus ISO 27001 or other requirements that share controls.
- Little internal capacity: no one can own a manual evidence calendar reliably.
- Buyer pressure for continuous assurance: customers who want a live trust page or frequent updates.
When does the lean templates-plus-auditor route work?
The lean route works when your environment is simple and one person can own a disciplined routine. You trade a subscription for a few hours a month of structured manual work.
- Small team with a single cloud provider and a modest set of tools.
- One framework: SOC 2 only, Security with perhaps one optional category.
- A named owner with time and authority, plus a backup.
- Auditor fit: a CPA firm that is comfortable receiving evidence as exports and dated screenshots.
- Budget focus: you would rather spend on security tools you need anyway, such as device management and single sign-on.
How do the two routes compare?
Both routes can reach the same audit. They differ in where the effort sits and what you pay for.
| Factor | With a platform | Lean: templates plus auditor |
|---|---|---|
| Evidence collection | Largely automated through integrations | Manual, on a calendar |
| Monitoring between audits | Continuous alerts | Periodic checks you schedule |
| Policies | Library inside the platform, still needs tailoring | Templates you tailor and own |
| Ongoing cost | Annual subscription plus internal time | Mostly internal time |
| Portability | Evidence and workflows tied to the vendor | Files you control |
| Main risk | Paying for automation you do not use; trusting the dashboard over the evidence | Missed evidence when the owner is busy |
| Best fit | Complex stacks, fast growth, several frameworks | Simple stacks, small teams, SOC 2 only |
How do you run SOC 2 without a platform?
Run it like a small operations process: one control matrix, one evidence calendar, one folder structure and one owner who checks it monthly.
- Build a control matrix listing each control, owner, frequency, criteria IDs and evidence location.
- Create an evidence folder per control, named by criteria ID, with subfolders by month or quarter.
- Turn frequencies into calendar events with named owners: quarterly access review, monthly vulnerability triage, annual risk assessment, restore test.
- Capture evidence properly: exports with dates, screenshots showing the system, the date and the account, and tickets linked to approvals.
- Hold a 30-minute monthly check where the owner confirms every due item is filed and chases what is missing.
- Keep a change log of new systems, vendors and people so your scope and system description stay accurate.
- Agree formats with your auditor early so there are no surprises in fieldwork.
The SOC 2 Audit Prep & System Description Kit ($49) helps with the system description and fieldwork preparation, and the SOC 2 Compliance Toolkit ($249, was $286) combines it with policies, the readiness matrix and risk and vendor registers.
What does SOC 2 evidence look like without a platform?
Without a platform, evidence is ordinary exports, tickets and screenshots, filed on schedule and linked to a control. These are typical examples.
| Control | Evidence | Frequency | Criteria |
|---|---|---|---|
| Access review | User list export per system, reviewer sign-off, removal tickets | Quarterly | CC6.2, CC6.3 |
| Offboarding | Leaving date and access-removal ticket with timestamps | Each leaver | CC6.2 |
| Code review | Pull request history showing approval before merge | Every change | CC8.1 |
| Vulnerability management | Scan reports and tickets showing fixes within deadlines | Monthly | CC7.1 |
| Security training | Completion report or signed records | At hire and annually | CC1.4, CC2.2 |
| Risk assessment | Updated risk register with approval date | Annually | CC3.2 |
| Vendor review | Vendor register and notes on key vendors' reports | Annually | CC9.2 |
| Restore test | Record of date, system and result | As policy states | A1.3 (if Availability is in scope) |
What are the hidden costs of each route?
With a platform, the overlooked cost is setup and tailoring: connecting integrations, mapping controls, rewriting generic policies and handling controls the platform cannot see. There is also the risk of renewing a subscription after your needs have changed.
With the lean route, it is the owner's attention. Someone must run the monthly check without fail, including during busy quarters, holidays and fundraising. If that person leaves, the knowledge must survive in the control matrix and folders, not in their head.
What does a sensible decision look like?
Consider two fictional companies. Maple Route (fictional) has 12 people, one cloud account structure, a handful of SaaS tools and only SOC 2 on its roadmap. A tailored template set, a control matrix and a monthly evidence check fit it well. Tessellate Data (fictional) has 90 people, three cloud providers, dozens of tools and ISO 27001 planned next year. For Tessellate, a platform's automation will likely earn its fee.
Can you mix both approaches?
Yes, and many companies do. A common pattern is to prepare the first audit with templates and a manual calendar, then adopt a platform once headcount, systems or frameworks grow. Another is to buy a platform for monitoring but keep your own tailored policies and system description.
If you move later, your templates, matrix and evidence history still count. The criteria and your auditor care about the controls, not the software.
What should you ask before deciding?
- How many hours a month would manual evidence collection really take us?
- Which of our controls would a platform actually monitor, and which stay manual?
- Does our chosen CPA firm have a preference, or accept any organized evidence?
- Will we need another framework in the next 12 to 24 months?
- Who owns SOC 2 day to day, and do they have the time?
- Can we export our evidence and policies if we leave a platform later?
- Which controls failed or nearly failed in our readiness review, and would automation have caught them?
For budget context, see what drives SOC 2 cost. Whichever route you choose, templates and platforms help you prepare; only the CPA firm's examination produces the report, and neither guarantees a clean opinion. The Trust Services Criteria are the same either way.
Last reviewed: 29 September 2026