20 domains
AICPA TSC 2017 (updated 2022)
The engineer who left in March. Is their access gone?
Is customer data encrypted everywhere it moves?
How long has that unpatched vulnerability been open?
Most teams cannot answer all four. The enterprise customer asking for your SOC 2 report will expect you to.
Onboarding is capped each quarter so every organization gets a named compliance lead.
Procurement sends a questionnaire. You cannot answer it, so the contract sits while somebody guesses at the answers.
A SOC 2 takes months of evidence you should already have been collecting. Nobody tells you that until a customer asks.
Access was right in January. Someone added a contractor in April. There is no moment where anyone checks.
That first question is a real control. This is what it looks like when it lands in your queue.
Restrict logical access to systems, data, and other protected resources to authorized users only.
Use centralized identity (IdP) with SSO for all production systems. Enforce least privilege through role-based access. Disable shared/default accounts. Encrypt data in transit (TLS 1.2+) and at rest (AES-256 or equivalent). Document a logical access policy and reconcile actual access against approved access quarterly.
This is what the auditor tests
AICPA TSC 2017 (updated 2022)
Rev 5 (Sep 2020)
ISO/IEC 27001:2022
45 CFR Parts 160 & 164
v4.0 (Mar 2022)
CMMC 2.0 (Dec 2021)
Rev 5 Baselines (2023)
FISMA 2014 / OMB A-130
Pulled straight from AWS, or uploaded against the control it satisfies. Never a folder of loose screenshots.
Every upload, release and destruction is written to an append-only log, with the person who did it.
Your auditor sees exactly what was released for the audit. Nothing else, and no standing seat in your systems.
Tell us which framework you are being asked for and we will tell you what it takes.