Skip to main content

SOC 2 Compliance Readiness Checklist

All 5 Trust Service Criteria with linked tools for each control

F

0 / 32 controls complete

Not Started — 0%

🔐

Security (CC6)

Protection against unauthorized access, use, or disclosure

TLS/SSL encryption enforced

All traffic uses HTTPS with valid certificates

Use TLS Certificate Checker

Security headers configured

HSTS, CSP, X-Frame-Options, X-Content-Type-Options

Use Security Headers Analyzer

Content-Security-Policy in place

Prevents XSS, clickjacking, and data injection

Use CSP Generator

CORS properly configured

Cross-origin access restricted to known origins

Use CORS Tester

Session cookies secured

Secure, HttpOnly, SameSite flags set

Use Cookie Security Analyzer

Authentication mechanism

JWT, SAML, or OIDC with proper validation

Use JWT Debugger

Multi-factor authentication

TOTP or hardware keys for admin access

Use TOTP Generator

Password policies enforced

Strong password requirements and hashing

Use Password Strength Analyzer

Data encrypted at rest

AES-256 or equivalent for stored data

Use Encrypt/Decrypt Tool

API keys and secrets managed

Secure generation, storage, and rotation

Use Token Generator

Availability (A1)

System operational and accessible as committed

Uptime monitoring

Automated alerts for service disruption

Incident response plan

Documented procedures for outages

Backup and recovery

Tested backup procedures with RTO/RPO

Capacity planning

Monitoring and alerting for resource limits

Disaster recovery plan

Documented DR with regular testing

⚙️

Processing Integrity (PI1)

System processing is complete, valid, accurate, and authorized

Input validation

Data validation at all entry points

Use JSON Validator

Error handling

Graceful errors without data leakage

Data integrity checks

Checksums or hashes for critical data

Use Hash Generator

Audit logging

All processing logged with timestamps

Change management

Documented approval process for changes

🔒

Confidentiality (C1)

Information designated as confidential is protected

Data classification policy

Documents labeled by sensitivity level

Access controls

Role-based access to confidential data

Encryption in transit

TLS for all data transmission

Use TLS Certificate Checker

Encryption at rest

Encrypted storage for sensitive data

Use Encrypt/Decrypt Tool

Data retention policy

Defined retention and deletion schedule

NDAs with sub-processors

Contractual confidentiality obligations

🛡️

Privacy (P1)

Personal information is collected, used, and disclosed in accordance with commitments

Privacy policy published

Clear notice about data collection and use

Consent mechanism

Opt-in/opt-out for data processing

Data subject rights

Process for access, correction, deletion

Cookie consent

Tracking cookies require consent

Use Cookie Security Analyzer

Data minimization

Only collect data necessary for purpose

Third-party data sharing

Documented sub-processor list

About the Soc2 Checklist

SOC 2 (System and Organization Controls 2) is the auditing framework used by service organizations to demonstrate how they handle customer data. It covers five Trust Service Criteria: Security (required), Availability, Processing Integrity, Confidentiality, and Privacy (optional). Most B2B SaaS companies need SOC 2 Type II to close enterprise deals.

This interactive checklist breaks down each criterion into specific, actionable controls. Where possible, it links directly to free tools on this site that help you implement or verify the control. Track your progress as you complete items — the grade updates in real time (A = audit ready).

How to use

  1. Start with the Security criterion (CC6) — it is required for all SOC 2 audits.
  2. Check off each control you have implemented.
  3. Click the linked tools to verify controls (e.g., use the Security Headers Analyzer for CC6.1).
  4. Work through Availability, Processing Integrity, Confidentiality, and Privacy.
  5. Aim for 90%+ completion before scheduling your audit.

Frequently Asked Questions

What is the difference between SOC 2 Type I and Type II?

Type I audits the design of controls at a point in time. Type II audits the operating effectiveness of controls over a period (typically 3-12 months). Type II is more valuable and takes longer because it requires evidence of consistent operation.

Which Trust Service Criteria are required?

Security (CC6) is always required. Availability, Processing Integrity, Confidentiality, and Privacy are optional — most SaaS companies include Availability and Confidentiality. The checklist above covers all five.

How long does SOC 2 compliance take?

For a typical startup with cloud infrastructure: 3-6 months for Type I, 6-12 months for Type II. The Readiness Checklist above gives you an honest assessment of where you are today.

Can I use these tools as audit evidence?

Yes — screenshots and output from these tools serve as evidence of control verification. For example, Security Headers Analyzer results demonstrate CC6.1 compliance, and the TLS Checker output documents encryption in transit.

Is this tool free to use?

Yes! This tool is 100% free. No signup, no credit card, no limits. It's part of Formatho's privacy-first developer toolkit.

Is my data safe? Does this tool send data to a server?

Absolutely. This tool runs entirely in your browser. Your data never leaves your device. Zero server-side processing, zero tracking.