SOC 2 Readiness Assessment Checklist

Use this SOC 2 Readiness Assessment Checklist to identify control gaps before audits, covering governance, access, change management, encryption & vendor risk.

SOC 2 Readiness Assessment Checklist



100 questions in 13 sectionsInteractive preview: try the answers

Section 1 of 13 · 7 questions

Audit Scope And Planning

  1. The report type has been selected (Type 1: point-in-time design assessment, or Type 2: operating effectiveness over 3–12 months)

  2. The in-scope Trust Services Criteria have been confirmed with leadership (Security is mandatory; Availability, Processing Integrity, Confidentiality, and Privacy are optional)

  3. The system description boundary is documented, identifying all services, infrastructure, and data flows in scope

  4. All in-scope cloud environments, data centers, and third-party systems are listed

  5. An audit firm has been identified or engaged

  6. A target audit window or report date has been established

  7. Internal ownership of the SOC 2 program is assigned to a named individual or team

Section 2 of 13 · 8 questions

Governance And Risk Management

  1. A formal information security policy is documented, approved by leadership, and reviewed within the last 12 months

  2. Security roles and responsibilities are defined and documented (RACI or equivalent)

  3. Board or executive meeting minutes reference security and risk oversight at least annually

  4. A risk assessment methodology is documented and includes likelihood and impact ratings

  5. A current risk register exists with named owners for each identified risk

  6. The risk register has been reviewed and updated within the last 12 months

  7. Risk treatment decisions are documented for all high and medium risks

  8. Acceptable use policies for systems, data, and devices are in place and acknowledged by staff

Section 3 of 13 · 6 questions

Security Policies And Documentation

  1. All security policies required by the Common Criteria are in place (access control, incident response, change management, vendor management, business continuity)

  2. Policies specify review frequency and have been reviewed within that period

  3. Policies are stored in a version-controlled, accessible location

  4. Staff have acknowledged security policies in writing, with records retained

  5. Security awareness training is conducted at least annually, with completion records

  6. New hire security onboarding includes security policy review and acknowledgment

Section 4 of 13 · 13 questions

Logical Access Controls (CC6)

  1. A formal access provisioning process requires documented approval before access is granted

  2. Role-based access control (RBAC) is implemented for all production systems

  3. Access follows the principle of least privilege for all user roles

  4. Multi-factor authentication (MFA) is enforced for all production system logins

  5. MFA is enforced for email, VPN, and administrative consoles

  6. A formal access de-provisioning process revokes access within one business day of termination

  7. Terminated employee de-provisioning tickets are retained with timestamps

  8. Privileged access (admin, root, superuser) is limited to named individuals with documented justification

  9. Privileged access activity is logged for the full observation period

  10. Periodic access reviews are conducted on a defined schedule (quarterly is standard) with reviewer sign-off retained

  11. Access review records identify each user reviewed, the reviewer, the date, and the approval or removal decision

  12. Shared and service account credentials are managed and rotated on a documented schedule

  13. Production database and cloud console access is restricted and reviewed on the same schedule as other privileged access

Section 5 of 13 · 11 questions

System Operations, Monitoring, And Incident Response (CC7)

  1. Logs are collected from all production systems, including application, infrastructure, and network layers

  2. Logs are retained for a minimum period aligned to the observation window (12 months recommended)

  3. Log access is restricted to authorized personnel

  4. Automated alerting is configured for security-relevant events (unauthorized access attempts, privilege escalation, configuration changes)

  5. Alert reviews are documented and retained, not just performed

  6. An incident response plan is documented and includes classification criteria, escalation paths, and response steps

  7. The incident response plan has been tested within the last 12 months (tabletop exercise or equivalent), with results documented

  8. Security incidents are recorded in a formal incident log with date, classification, response actions, and resolution

  9. Vulnerability scanning is performed on a defined schedule and results are documented

  10. A formal patch management process exists with defined remediation timeframes by severity

  11. Patch compliance is tracked and exceptions are formally documented

Section 6 of 13 · 8 questions

Change Management (CC8)

  1. All production changes are tracked in a ticketing or change management system

  2. Change requests require documented approval before deployment to production

  3. Separation of duties exists between the person developing and the person approving or merging changes to production

  4. Pre-deployment testing is required and evidence of test results is retained per change

  5. A documented emergency change procedure exists, including a post-implementation review requirement

  6. Emergency changes are tracked and reviewed after deployment

  7. Configuration baselines are documented for critical systems

  8. Deviations from configuration baselines are tracked and approved

Section 7 of 13 · 9 questions

Data Protection And Encryption

  1. A data classification policy is in place, defining sensitivity tiers and handling requirements for each

  2. Customer and sensitive data is identified, mapped, and categorized within the classification framework

  3. Encryption is applied to all sensitive data at rest (AES-256 or equivalent)

  4. Encryption is applied to all data in transit (TLS 1.2 minimum on all external endpoints)

  5. Encryption key management is documented, including key rotation schedules

  6. Key rotation logs are retained and demonstrate the schedule is followed

  7. Data retention periods are documented for each data category

  8. Secure data disposal procedures are documented and disposal records are retained

  9. Portable media and device encryption is enforced where sensitive data may be stored

Section 8 of 13 · 8 questions

Vendor And Third-Party Risk Management (CC9)

  1. A vendor inventory lists all third parties with access to in-scope systems or customer data

  2. Each vendor is classified by risk level based on data access and criticality

  3. Vendor security assessments are conducted before onboarding and on a periodic schedule (annually for high-risk vendors)

  4. Current vendor assessment files are retained for all high-risk vendors (SOC 2 reports, security questionnaires, or equivalent)

  5. Vendor contracts include security and data protection obligations (data processing agreements or equivalent)

  6. Complementary User Entity Controls (CUECs) from vendor SOC 2 reports have been reviewed and implemented

  7. A process exists to re-evaluate vendors following significant security incidents or contractual changes

  8. Vendor offboarding includes revocation of all system access and data disposal confirmation

Section 9 of 13 · 8 questions

Availability And Business Continuity (A1 — Include If Availability Is In Scope)

  1. System availability commitments are documented (uptime targets or SLA terms)

  2. Infrastructure capacity is monitored against defined thresholds

  3. A business continuity and disaster recovery (BCP/DR) plan is documented

  4. The BCP/DR plan has been tested within the last 12 months, with test results retained

  5. Recovery time objectives (RTO) and recovery point objectives (RPO) are defined and tested

  6. Data backups are performed on a defined schedule

  7. Backup restoration is tested periodically, with results documented

  8. System redundancy and failover mechanisms are documented and tested

Section 10 of 13 · 4 questions

Processing Integrity (PI1 — Include If Processing Integrity Is In Scope)

  1. Input validation controls are implemented and documented for all data entry points

  2. Data processing errors are detected, logged, and resolved through a documented process

  3. Processing completeness is verified and monitored for all in-scope workflows

  4. Unauthorized data modification is detected and alerted

Section 11 of 13 · 4 questions

Confidentiality (C1 — Include If Confidentiality Is In Scope)

  1. Confidential data is identified and classified under the data classification policy

  2. Access to confidential data is restricted to authorized individuals and reviewed on a defined schedule

  3. Confidential data is not retained beyond its documented retention period

  4. NDAs or confidentiality agreements are in place with employees and contractors who access confidential data

Section 12 of 13 · 7 questions

Privacy (P1–P8 — Include If Privacy Is In Scope)

  1. A privacy notice is published and describes the data collected, its use, and the individual's rights

  2. Consent mechanisms are documented and records of consent are retained where required

  3. Personal data collection is limited to what is necessary for the stated purpose

  4. Individuals can request access to, correction of, or deletion of their personal data, and a process exists to fulfill these requests

  5. Personal data is not shared with third parties without a lawful basis and documented agreement

  6. Cross-border data transfer mechanisms are documented where applicable

  7. Privacy incidents (unauthorized disclosure of personal data) are tracked and reportable to regulators within required timeframes

Section 13 of 13 · 7 questions

Evidence And Remediation Readiness

  1. A control inventory maps each in-scope Trust Services Criterion to the control(s) addressing it

  2. Evidence for each control is identified, collected, and stored in an organized, audit-ready location

  3. Evidence covers the full observation period (for Type 2) and is not limited to point-in-time snapshots

  4. Identified control gaps have a documented remediation plan with assigned owner and target date

  5. Remediation progress is tracked and reviewed on a regular cadence

  6. A management representation letter process is understood and a draft is in preparation

  7. The system description (Section III of the SOC 2 report) is drafted and reviewed by relevant stakeholders

Checklist by GoAudits. This checklist is an example: we do not guarantee compliance with the laws applicable to your territory or industry. Seek professional advice to adapt it to your workplace or jurisdiction.

Free PDF

Download the SOC 2 Readiness Assessment Checklist

By downloading this checklist you agree to the GoAudits privacy policy and terms of service.

NEW! Try generating a custom checklist with our free AI tool:

Easy inspection app for your digital checklists