Skip to content
Blogs

Blogs

SOC 2 Compliance Checklist for SaaS Companies: 2026 Edition 

Posted on November 17, 2026November 17, 2026 By Finstein.ai No Comments on SOC 2 Compliance Checklist for SaaS Companies: 2026 Edition 

A good SOC 2 checklist turns an intimidating framework into a sequence of tasks your team can actually finish. SOC 2 does not hand you a fixed list of controls. Instead, the AICPA Trust Services Criteria describe outcomes, and each company designs controls that achieve them in its own environment. 

That flexibility is helpful but confusing for SaaS teams preparing for their first audit. This 2026 edition sets out the SOC 2 requirements in plain language, maps them to the controls, policies and evidence auditors typically expect, and gives you a process to get from kickoff to fieldwork without surprises. 

How SOC 2 requirements are structured 

SOC 2 requirements come from the 2017 Trust Services Criteria, updated with revised points of focus in 2022. Security, also called the Common Criteria, is mandatory for every SOC 2 report. Availability, Processing Integrity, Confidentiality and Privacy are optional and added based on customer needs. 

The Common Criteria are grouped into nine series. The table below shows what each covers and the kind of controls auditors look for. 

Series Area Typical controls for SaaS 
CC1 Control environment Code of conduct, org chart, board or leadership oversight, background checks 
CC2 Communication and information Security policies published, customer commitments documented, internal reporting channels 
CC3 Risk assessment Annual risk assessment, fraud risk consideration, risk register 
CC4 Monitoring activities Internal control reviews, vulnerability scanning, remediation tracking 
CC5 Control activities Policies and procedures deployed, segregation of duties, technology controls 
CC6 Logical and physical access SSO and MFA, access provisioning and removal, encryption, access reviews 
CC7 System operations Logging, monitoring, alerting, incident response, vulnerability management 
CC8 Change management Code review, approvals, testing, separate environments, deployment controls 
CC9 Risk mitigation Vendor management, business continuity, cyber insurance where relevant 

Step 1: scoping checklist 

Scope defines what the auditor tests, so get it right before you build anything. Most SaaS companies scope the production platform that delivers their service, its supporting infrastructure and the people who run it. 

  • Name the system that will appear in the report (product and environment) 
  • List cloud accounts, regions, databases and key third-party services 
  • Identify subservice organisations and decide on the carve-out or inclusive method 
  • Collect the SOC 2 reports of carved-out providers such as your cloud host 
  • Choose the Trust Services Criteria: Security plus any optional categories customers require 
  • Decide on Type 1 or Type 2 and, for Type 2, the observation period dates 
  • Confirm locations and teams in scope, including remote employees 

Step 2: SOC 2 policies checklist 

Auditors expect written, approved and communicated SOC 2 policies. Keep them short, accurate and aligned with what your team actually does; a policy you do not follow creates exceptions. The core set for most SaaS companies: 

  • Information security policy (umbrella policy approved by leadership) 
  • Acceptable use policy 
  • Access control policy 
  • Change management policy 
  • Risk assessment and risk management policy 
  • Incident response plan 
  • Business continuity and disaster recovery plan 
  • Vendor and third-party management policy 
  • Data classification, retention and disposal policy 
  • Encryption and key management policy 
  • Human resources security policy (onboarding, training, exit) 
  • Vulnerability and patch management policy 
  • Logging and monitoring policy 
  • Code of conduct and disciplinary process 

Each policy needs an owner, a version history, an approval date and evidence that staff have acknowledged it. Review them at least annually. 

Step 3: SOC 2 controls list for SaaS 

A SOC 2 controls list for a typical SaaS company runs to somewhere between several dozen and a hundred-plus controls, depending on scope and criteria. There is no fixed number. The checklist below captures the controls auditors most frequently test in cloud-native environments. 

Identity and access 

  • Single sign-on and multi-factor authentication for all production and admin access 
  • Role-based access with least privilege, documented per role 
  • Joiner, mover and leaver process with timely de-provisioning 
  • Quarterly user access reviews for production, cloud console and key SaaS tools 
  • No shared accounts; break-glass accounts controlled and monitored 

Infrastructure and data 

  • Encryption of data at rest and in transit 
  • Network segmentation and security groups reviewed regularly 
  • Hardened, patched base images and managed endpoints (MDM, disk encryption, screen lock) 
  • Backups configured, encrypted and restore-tested 
  • Production data not used in non-production environments without controls 

Operations and monitoring 

  • Centralised logging with retention and alerting on security events 
  • Vulnerability scanning and an annual third-party penetration test 
  • Defined severity levels and remediation timelines for vulnerabilities 
  • Incident response plan tested at least annually through a tabletop exercise 
  • Uptime and capacity monitoring if Availability is in scope 

Change management 

  • Version control with protected main branches 
  • Peer review and approval before merge 
  • Automated testing in the pipeline 
  • Separation of developer and deployment rights, or compensating review 
  • Emergency change procedure with retrospective approval 

People and vendors 

  • Background verification for new hires, as permitted by local law 
  • Security awareness training at onboarding and annually 
  • Signed confidentiality agreements 
  • Vendor inventory with risk rating and annual review of critical vendors 
  • Board or leadership review of security risks and programme status 

CTA: Want this in a format your team can work through? Download the SOC 2 Checklist PDF: every item above organised by Trust Services Criteria, with owners, evidence examples and a status column you can track to audit day. 

Step 4: SOC 2 evidence checklist 

Controls only count if you can prove them. SOC 2 evidence is what the auditor inspects to confirm design (Type 1) and operating effectiveness across the period (Type 2). Weak evidence is the most common reason first audits drag on. 

Control area Example evidence auditors request 
Policies Approved policy documents, version history, staff acknowledgements 
Onboarding Offer letters, background check confirmations, training completion records 
Offboarding Exit tickets with timestamps, access removal screenshots or logs 
Access reviews Quarterly review records with reviewer sign-off and actions taken 
Change management Pull requests showing reviewer approval, pipeline logs, deployment records 
Vulnerability management Scan reports, pen test report, remediation tickets 
Incident response Incident log, post-incident reviews, tabletop exercise notes 
Vendor management Vendor inventory, risk assessments, vendor SOC 2 reports reviewed 
Risk assessment Risk register, management review minutes 
Backups Backup configuration, restore test records 

Good evidence habits: 

  • Capture evidence when the control runs, not weeks later 
  • Show dates, system names and the person who performed the action 
  • Store everything in one organised repository mapped to control IDs 
  • Keep population lists (all leavers, all changes) so auditors can sample 
  • Do not edit or recreate evidence after the fact 

Step 5: system description and management assertion 

Every SOC 2 report includes a description of your system prepared by management. It covers the services you provide, infrastructure, software, people, procedures, data, principal service commitments and system requirements, and any complementary user entity controls your customers must operate. 

Management also signs an assertion that the description is fairly presented and that the controls were suitably designed (and, for Type 2, operated effectively). Draft both early. Writing the description often exposes scope gaps that are cheaper to fix before fieldwork. 

SOC 2 for SaaS: a 10-step preparation process 

Here is the order in which we recommend SaaS teams work through this SOC 2 checklist. 

  1. Appoint an owner. Give one person accountability and a working group across engineering, HR and finance. 
  1. Confirm customer needs. Identify the report type and criteria your buyers expect. 
  1. Fix scope. Define the system, subservice organisations and Trust Services Criteria. 
  1. Run a SOC 2 readiness assessment. Map existing controls to each criterion and log gaps with owners and dates. 
  1. Write and approve policies. Keep them aligned with real practice and collect staff acknowledgements. 
  1. Implement and configure controls. Prioritise identity, logging, change management and endpoint controls. 
  1. Set up evidence collection. Build a control calendar and a central repository mapped to criteria. 
  1. Perform an internal dry run. Sample your own evidence as an auditor would and fix what fails. 
  1. Draft the system description. Prepare it with the management assertion and review it with leadership. 
  1. Engage the auditor. Agree scope, timelines and the evidence request list, then support fieldwork. 

Common SOC 2 checklist mistakes 

The same mistakes appear in many first-time programmes. Avoiding them saves weeks. 

  • Copying long policy templates that describe controls you do not run 
  • Starting the Type 2 observation period before controls are live 
  • Forgetting non-engineering controls such as HR, training and vendor reviews 
  • Treating access reviews as a click-through rather than a genuine review 
  • Leaving optional criteria in scope that no customer asked for 
  • Relying on screenshots without dates or system identifiers 

Frequently asked questions 

What are the SOC 2 requirements for SaaS companies? 

SOC 2 requirements for SaaS come from the AICPA Trust Services Criteria. Security is mandatory and covers the nine Common Criteria series, from control environment to risk mitigation. Availability, Processing Integrity, Confidentiality and Privacy are optional. You design your own controls to meet the criteria, then prove them with evidence. 

Which policies are required for SOC 2? 

SOC 2 does not prescribe exact policy titles, but auditors expect documented coverage of information security, access control, change management, risk assessment, incident response, business continuity, vendor management, data retention, encryption, HR security and acceptable use. Policies must be approved, communicated, acknowledged by staff and reviewed at least annually. 

What evidence do SOC 2 auditors ask for? 

Auditors request evidence that each control is designed and operating, such as approved policies, access review records, pull request approvals, onboarding and exit records, training completion, vulnerability scans, penetration test reports, incident logs and vendor assessments. For a Type 2, they sample evidence from across the observation period, so it must exist for every period. 

How many controls are in SOC 2? 

There is no fixed number. The Trust Services Criteria define outcomes, and each organisation designs controls to meet them. A typical SaaS company’s SOC 2 controls list runs from several dozen to over a hundred controls, depending on system complexity and the optional criteria included in scope. 

Does SOC 2 require penetration testing? 

The Trust Services Criteria do not name penetration testing explicitly, but they require you to identify and evaluate vulnerabilities and monitor controls. In practice, most auditors and customers expect an annual third-party penetration test alongside regular vulnerability scanning, so it belongs on any realistic SOC 2 checklist. 

How do I use a SOC 2 checklist to prepare for an audit? 

Work through it in order: scope, policies, controls, evidence and the system description. Assign an owner to each item, record status, and run an internal dry run where you sample your own evidence. Fix gaps before the auditor’s fieldwork or, for a Type 2, before the observation period starts. 

How Finstein Cyber can help 

Finstein Cyber, the cyber security and compliance practice of Finstein Advizory Service LLP, helps SaaS companies turn this SOC 2 checklist into a working programme: readiness assessment, policy writing, control design, evidence set-up and audit support. Our India-based team includes 20 CISA holders, 15 CEH professionals and 50 ISO 27001 Lead Auditors, with remote delivery from Chennai, Hyderabad, Bangalore, New York and Singapore. We also provide VAPT and 24×7 managed SOC, two controls auditors look for in almost every SaaS audit. 

Cyber

Post navigation

Previous Post: SOC 2 Type 1 vs Type 2: Which Report Your US Customers Will Ask For ?
Next Post: Odoo vs ERPNext for Manufacturing in India: Which ERP Is Better?

Related Posts

SOC 2 Type 1 vs Type 2: Which Report Your US Customers Will Ask For ? Cyber
Is HITRUST Only for HIPAA-Covered Entities?  Cyber
What Security Awareness Training Does HITRUST Actually Require? What Security Awareness Training Does HITRUST Actually Require?  Cyber
How Often Do You Need to Renew Your HITRUST Certification? Cyber
Can You Share Your HITRUST Report with Customers and Partners? Cyber
One Small Bug, One Big Risk: Why PHP Security Updates Matter for Your Business Cyber

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Categories

  • Ai
  • Cyber
  • Data Sciences
  • ERPNext
  • Technology

Copyright © 2026 Blogs.

Powered by PressBook Masonry Blogs