SOC 2 Compliance Checklist: What to Fix Before the Auditor Arrives
Harsh
Cybersecurity Experts
Table of Contents
- 01How to use this SOC 2 compliance checklist
- 021. Scope and governance
- 032. Risk assessment
- 043. Policies and procedures
- 054. People
- 065. Logical access
- 076. Change management
- 087. System operations and monitoring
- 098. Incident response
- 109. Availability and recovery
- 1110. Vendor management
- 1211. Evidence
- 13SOC 2 readiness checklist vs SOC 2 audit checklist
- 14The gaps that cause the most exceptions
- 15What a checklist cannot do
- 16Get the checklist and a second opinion
- 17Frequently Asked Questions
How to use this SOC 2 compliance checklist
This SOC 2 compliance checklist covers the controls and evidence a CPA firm will test under the Security criteria, which every SOC 2 report includes. Work through it before fieldwork begins. Each item you cannot tick is a gap to close or an exception waiting to appear in your report.
The checklist is ordered the way a project runs: decisions first, then documents, then the controls that have to operate every week. If you added Availability, Confidentiality, Processing Integrity or Privacy to your scope, you will need further controls for those.
1. Scope and governance
☐ The system in scope is defined: product, infrastructure, people, data and locations
☐ Trust Services Criteria are selected and documented
☐ Report type (Type 1 or Type 2) and review period are agreed with the CPA firm
☐ A system description is drafted
☐ A security owner is named, with management oversight recorded in meeting notes
☐ An organization chart and role descriptions exist
☐ Subservice organizations (cloud host, key vendors) are identified
2. Risk assessment
☐ A risk assessment was performed in the last 12 months
☐ Risks are recorded in a register with ratings, owners and treatment decisions
☐ Fraud risk is considered
☐ Changes to the business or technology trigger a review of the register
3. Policies and procedures
☐ Information security policy
☐ Access control policy
☐ Change management policy
☐ Incident response plan
☐ Business continuity and disaster recovery plan
☐ Vendor management policy
☐ Data classification and retention policy
☐ Acceptable use policy and code of conduct
☐ Vulnerability management policy with remediation timelines by severity
☐ Every policy has an owner, an approval date and a review within the last year
☐ Employees have acknowledged the policies that apply to them
4. People
☐ Background checks are completed for new hires where law allows
☐ Security awareness training is completed at hire and annually, with records
☐ Confidentiality agreements are signed
☐ An onboarding checklist grants access by role
☐ An offboarding checklist removes access within the time your policy states
☐ Performance reviews or equivalent accountability measures are in place
5. Logical access
☐ Multifactor authentication is enforced on the identity provider, cloud console, source control and production systems
☐ Access is granted on a least-privilege basis and tied to roles
☐ Access requests and approvals are recorded in tickets
☐ User access reviews are performed on schedule, with evidence of the review and of removals
☐ Shared and default accounts are eliminated or controlled
☐ Administrative access to production is restricted and logged
☐ Password and session settings meet your policy
☐ Data is encrypted in transit and at rest
☐ Encryption keys and secrets are stored in a managed vault
6. Change management
☐ Code changes go through pull requests with peer review
☐ Branch protection prevents direct commits to the main branch
☐ Changes are tested before deployment
☐ Deployments to production are approved and traceable to a ticket
☐ Development, staging and production environments are separated
☐ Emergency changes follow a documented process and are reviewed afterward
☐ Infrastructure changes are tracked the same way as code
7. System operations and monitoring
☐ Logging is enabled for cloud accounts, applications and authentication events
☐ Alerts are configured for security-relevant events, and someone responds to them
☐ Vulnerability scans run on a set schedule
☐ Findings are tracked and fixed within policy timelines
☐ A penetration test was performed in the last 12 months, inside the review period for Type 2
☐ Endpoint protection and disk encryption are active on company laptops
☐ Patching follows a documented schedule
☐ An asset inventory is maintained
8. Incident response
☐ The incident response plan names roles and escalation paths
☐ Incidents are logged with timeline, impact and root cause
☐ The plan was tested with a tabletop exercise in the last 12 months
☐ Customer notification obligations are documented
9. Availability and recovery
☐ Backups run automatically and are monitored for failures
☐ A restore test was performed in the last 12 months
☐ Recovery time and recovery point objectives are defined
☐ The disaster recovery plan was tested, and results were recorded
☐ Capacity and uptime are monitored
10. Vendor management
☐ An inventory of vendors with access to systems or data exists
☐ Critical vendors have been risk-assessed
☐ SOC 2 reports or equivalent assurance from critical vendors are collected and reviewed annually
☐ Contracts include security and confidentiality terms
☐ Complementary user entity controls from vendor reports are mapped to your own controls
11. Evidence
☐ Every control has a named owner
☐ Every control has a defined piece of evidence and a place it is stored
☐ Evidence shows dates that fall inside the review period
☐ Populations are available for sampling: lists of hires, terminations, changes and incidents
☐ A request tracker is ready for the auditor's evidence list
SOC 2 readiness checklist vs SOC 2 audit checklist
The two terms describe the same controls at different moments.
A SOC 2 readiness checklist is used months before the examination. It asks whether each control is designed and in place. Gaps here lead to remediation work.
A SOC 2 audit checklist is used in the weeks before fieldwork. It asks whether evidence exists for each control across the whole period. Gaps here are harder to repair, since you cannot produce an access review for a quarter that has already passed.
Run the readiness version early enough that every control operates for the full period.
The gaps that cause the most exceptions
Terminated employees whose access stayed active beyond the policy window
Access reviews performed late or without evidence of follow-up
Production changes with no recorded approval
Policies with no annual review
New hires missing training or background check records
Vulnerabilities left open past the remediation deadline
Vendor reviews not performed
Each one is a routine task that was missed, and each is preventable with a monthly check.
What a checklist cannot do
A checklist tells you what auditors look for. It cannot tell you whether your access review would pass sampling, or whether your change tickets contain what an auditor needs to see. That takes someone reading your real evidence against the criteria.
Digisecuritas runs readiness assessments that produce a control gap register, evidence observations and remediation priorities. We then test readiness before the CPA firm does. The service is described on the SOC 2 readiness page.
Get the checklist and a second opinion
Download the checklist as a spreadsheet to assign owners and track status. When you have marked it up, book a readiness assessment and we will review the gaps with you.
Download the checklist, then book a readiness assessment
