Loading…
Loading…
Free interactive tool
Answer 12 questions about your stack. Get a SOC 2 readiness checklist mapping your answers to specific Trust Services Criteria controls (CC1-CC9). Identifies gaps + tells you how to close them. Download as markdown for your team.
5 minutes. No signup. Runs entirely in your browser — your answers never leave the page.
Is MFA enforced for all human access to your production systems?
Includes admin consoles (AWS, GCP, Azure), GitHub org, deploy tooling, and any production database access. SSO with mandatory MFA counts.
Does every multi-tenant data query filter by workspace_id / org_id at the ORM layer?
If your app has multiple customers in one database, every Query.all() must scope to a tenant. A single missed filter = cross-tenant data leak.
Do you log every state-changing API call (create/update/delete) with actor + timestamp + before/after?
An audit trail lets you reconstruct who did what, when. Required for incident response, compliance review, and customer trust.
Is sensitive data encrypted at rest in your production database (AES-256 or equivalent)?
Most managed databases (RDS, Cloud SQL, Aurora) offer this with one checkbox. Verify it's actually enabled — defaults vary.
Is all traffic to your app behind HTTPS / TLS 1.2+ with valid certificates?
Includes API endpoints, frontend, internal service-to-service calls. Mixed-content warnings or http:// callbacks fail this.
Are all secrets (API keys, DB passwords, JWT secrets) stored in environment variables or a vault — not in source code?
Hardcoded secrets in git history are a SOC 2 finding even if you rotate them later. The history is the evidence.
Does your app enforce role-based access control (RBAC) at the route/endpoint level?
Not just hiding UI elements — actual server-side checks that a user with 'viewer' role can't POST to admin endpoints.
Do you have a written incident response playbook (what to do if a customer reports a security issue)?
Even one page is enough to start. Should include: who's notified, how to acknowledge the reporter, disclosure timeline, postmortem requirement.
Do you run automated dependency vulnerability scanning on every deploy?
GitHub Dependabot, Snyk, npm audit, pip-audit — any tool that catches known-vulnerable dependencies before they ship to prod.
Do you remove access for departed employees within 24 hours of termination?
Includes GitHub org membership, AWS IAM, Slack workspace, deploy tools, and shared customer accounts. Quarterly access review for active employees is the next bar.
Have you successfully restored from a backup in the last 90 days (test, not just schedule)?
Daily backups that have never been tested are not backups — they're hopeful files. A documented restore proves the backup actually works.
Do you have a written data retention + deletion policy that customers can read?
Should answer: how long is customer data kept after they delete an account? What about backups? Is there a way for them to request deletion (GDPR DSR)?