SOC 2 Requirements: The Controls Auditors Actually Test
Harsh
Cybersecurity Experts
Table of Contents
- 01SOC 2 requirements are criteria, not a control list
- 02The five Trust Services Criteria categories
- 03What are SOC 2 controls?
- 04The controls auditors test, by Common Criteria area
- 05CC1: Control environment
- 06CC2: Communication and information
- 07CC3: Risk assessment
- 08CC4: Monitoring activities
- 09CC5: Control activities
- 10CC6: Logical and physical access
- 11CC7: System operations
- 12CC8: Change management
- 13CC9: Risk mitigation
- 14Additional criteria if you add categories
- 15How auditors test: the evidence side of SOC 2 compliance requirements
- 16Controls that most often produce exceptions
- 17Points of focus: guidance, not obligations
- 18Building a control set that fits
- 19How Digisecuritas helps
- 20Find the gaps in your control set
- 21Frequently Asked Questions
SOC 2 requirements are criteria, not a control list
SOC 2 requirements are set out in the AICPA Trust Services Criteria. They describe outcomes a service organization has to achieve, such as restricting access to authorized users. They do not prescribe how. Each company designs controls that meet the criteria for its own systems, and the auditor tests those controls.
This is why two SOC 2 reports can list different controls and both be valid. It is also why "what are the requirements?" has a two-part answer: the criteria you have to meet, and the controls auditors expect to find when they test a company like yours.
The five Trust Services Criteria categories
Category | What it addresses | Required?
|
|---|---|---|
Security | Protection of systems and data against unauthorized access and damage | Yes, in every SOC 2 report |
Availability | Systems are available for operation as committed | Optional |
Processing Integrity | Processing is complete, valid, accurate and timely | Optional |
Confidentiality | Information designated confidential is protected | Optional |
Privacy | Personal information is handled according to commitments | Optional |
Security is assessed through the Common Criteria, numbered CC1 to CC9. Most first reports cover Security alone. Availability and Confidentiality are the most frequent additions for SaaS companies.
What are SOC 2 controls?
What are SOC 2 controls? They are the specific policies, procedures and technical settings your company uses to meet each criterion. A criterion says logical access must be restricted. Your controls might be single sign-on with multifactor authentication, role-based permissions, quarterly access reviews and removal of access within one business day of termination.
Auditors test controls, so the control wording matters. A control that says "access is reviewed quarterly" will be tested four times in a 12-month period. Write controls to describe what you do, at the frequency you do it.
The controls auditors test, by Common Criteria area
CC1: Control environment
Code of conduct acknowledged by employees
Organization chart and defined security responsibilities
Background checks for new hires
Management or board oversight of security, with meeting records
Performance evaluations
CC2: Communication and information
Security policies published to staff
Security awareness training at hire and annually
A channel for reporting security concerns
Customer-facing commitments, such as terms of service and a security page
Communication of system changes to customers
CC3: Risk assessment
Annual risk assessment with a documented register
Consideration of fraud risk
Review of risks when the business or technology changes
CC4: Monitoring activities
Internal reviews of control performance
Penetration testing and vulnerability assessments
Tracking of deficiencies to resolution
CC5: Control activities
Policies and procedures for each control area, reviewed annually
Segregation of duties, or compensating controls where teams are small
CC6: Logical and physical access
Unique user IDs and multifactor authentication
Role-based access with documented approval
Periodic user access reviews
Timely removal of access on termination
Encryption of data in transit and at rest
Network protections such as firewalls and security groups
Endpoint protection and disk encryption
Physical access controls, usually inherited from the cloud provider
CC7: System operations
Vulnerability scanning and patching
Logging and alerting on security events
A documented incident response plan
Incident records with root cause analysis
An annual incident response exercise
CC8: Change management
Peer review of code changes
Testing before deployment
Approval of production releases
Separation of development and production environments
Controls over emergency changes
CC9: Risk mitigation
Vendor inventory and risk assessments
Review of vendor SOC reports
Business continuity planning
Cyber insurance, where held
Additional criteria if you add categories
Availability (A1): capacity monitoring, backups, restore tests, disaster recovery plan and testing
Confidentiality (C1): data classification, retention schedules, secure disposal
Processing Integrity (PI1): input validation, processing checks, error handling, output reconciliation
Privacy (P1 to P8): notice, consent, collection limits, access and correction rights, disclosure, quality, monitoring
How auditors test: the evidence side of SOC 2 compliance requirements
The SOC 2 compliance requirements an auditor checks in fieldwork are about evidence. For each control, the auditor uses one or more of four methods:
Inquiry. Asking the control owner how the control works.
Observation. Watching the control performed.
Inspection. Examining documents, tickets, configurations and logs.
Reperformance. Repeating the control independently to see whether the result matches.
For a Type 2 report, the auditor requests a population, such as all employees hired in the period, and selects a sample. Each sampled item needs complete evidence. One new hire out of 25 without a background check is an exception in the report.
Controls that most often produce exceptions
Control | What goes wrong
|
|---|---|
Access removal on termination | Account disabled days after the policy deadline |
User access reviews | Review performed late, or no evidence of follow-up on findings |
Change approval | Production deployment with no recorded review |
Security training | New hire missed the completion window |
Vulnerability remediation | Critical finding open beyond the stated timeline |
Vendor reviews | Annual review of a critical vendor not performed |
Policy review | Policy not reviewed within the year |
Every item in the table is a recurring task. Exceptions come from missed occurrences, and a monthly internal check catches most of them.
Points of focus: guidance, not obligations
Each criterion comes with points of focus from the AICPA. These are examples of what a control might address. They help when designing controls, and auditors refer to them. You are not required to have a control for every point of focus, and not every one applies to every organization.
Building a control set that fits
Define the system and the criteria in scope.
List the risks to your commitments.
For each criterion, write controls that describe what you do now.
Identify criteria with no control and design one.
Assign an owner and an evidence source to every control.
Test the set before the auditor does.
Companies that copy a generic control list often end up with controls they cannot operate. A smaller set that matches reality produces a cleaner report.
How Digisecuritas helps
Digisecuritas designs and maps controls to the Trust Services Criteria, produces a control matrix with ownership and evidence requirements and performs readiness testing with an exception register and remediation roadmap. An independent CPA firm performs the examination. See the SOC 2 readiness page.
Find the gaps in your control set
Send us your current control list or policy set. We will compare it with the criteria and show you what is missing and what is unnecessary.
