SOC 2 (Trust Services Criteria) Controls Checklist
AICPA · 20 controls
Curated subset of the SOC 2 Common Criteria (CC) used for service-organization trust reporting.
CC6.1Logical access security
Access
Logical access to systems, data, and resources is restricted to authorized users.
Evidence: Access-control policy, MFA configuration export, role-to-permission matrix.
CC6.2User access provisioning
Access
New internal and external users are registered and authorized before being granted access.
Evidence: Sample of approved access-request tickets for recent new hires.
CC6.3User access deprovisioning
Access
Access is removed timely when a user is terminated or no longer requires it.
Evidence: Termination list reconciled against access-removal timestamps.
CC6.4Physical access restriction
Security
Physical access to facilities and infrastructure is restricted to authorized personnel.
Evidence: Badge-access list and visitor logs for in-scope facilities.
CC6.6Boundary protection
Security
The system protects against threats from sources outside its logical boundaries.
Evidence: Firewall / security-group rule export and the most recent review.
CC6.7Data-in-transit protection
Data
Information in transit is encrypted to protect confidentiality and integrity.
Evidence: TLS configuration scan results and cipher policy.
CC6.8Malicious software prevention
Security
Controls prevent or detect the introduction of unauthorized or malicious software.
Evidence: EDR coverage report and recent detection/response samples.
CC7.1Vulnerability management
Security
Vulnerabilities are identified, evaluated, and remediated on a defined cadence.
Evidence: Vulnerability-scan reports with remediation tickets and dates.
CC7.2Security monitoring
Security
The system is monitored to detect anomalies and potential security events.
Evidence: SIEM alert configuration and a sample of triaged alerts.
CC7.3Incident response
Security
Identified security incidents are evaluated and responded to per a defined process.
Evidence: Incident-response plan and post-incident reviews / tabletop results.
CC7.4Incident recovery
Security
The entity recovers from identified security incidents and restores operations.
Evidence: Recovery runbooks and a recent incident recovery record.
CC8.1Change management
Change
Changes to infrastructure, data, software, and procedures are authorized, tested, and approved.
Evidence: Sample of change tickets showing test evidence and approvals.
CC9.1Risk mitigation
Other
The entity identifies, selects, and develops risk-mitigation activities.
Evidence: Current risk register and evidence of periodic review.
CC9.2Vendor and third-party risk
Vendor
The entity assesses and manages risks associated with vendors and business partners.
Evidence: Vendor inventory with risk tier and most recent SOC report review.
CC1.1Control environment — integrity and ethics
Other
The entity demonstrates a commitment to integrity and ethical values.
Evidence: Code of conduct and acknowledgment completion report.
CC2.1Information and communication
Other
The entity obtains and uses relevant, quality information to support controls.
Evidence: Control documentation describing information flows and ownership.
CC3.2Risk identification and assessment
Other
The entity identifies risks to objectives and analyzes them to determine management.
Evidence: Risk-assessment methodology and the latest assessment output.
CC4.1Control monitoring activities
Other
The entity evaluates whether components of internal control are present and functioning.
Evidence: Internal control monitoring / self-assessment results.
CC5.2Control activities over technology
Change
The entity selects and develops general control activities over technology.
Evidence: ITGC control matrix mapped to in-scope systems.
A1.2Availability — backup and recovery
Data
Backups and recovery capabilities support availability commitments.
Evidence: Backup success reports and the most recent restore test.
Import SOC 2 (Trust Services Criteria) into Compliance Hub
One click imports these controls into your register — then run reviews, attach evidence, and export for auditors.
Explore Compliance Hub