For a SOC 2 Type 2 examination, the auditor usually asks for a complete list of changes made during the audit period, then picks a sample to test. That list is the change population. If it is incomplete or inconsistent, the sample is not reliable and the auditor may ask for it again. This guide covers how to build one that holds up. Auditor expectations vary, so confirm format and scope with your audit firm.
For background, see audit population, audit sample, and change management.
What Belongs in a Change Population
Include every change that falls under your change management control during the audit period. Depending on your scope, that can mean:
- Application code deployments to production
- Infrastructure changes, including infrastructure as code updates
- Configuration changes to in-scope systems
- Emergency changes
- Database or schema changes
Choose the Source of Truth
| Source | Good for | Watch out for |
|---|---|---|
| Source control merges or pull requests | Code changes, see pull request approval | Merges that never deployed |
| Deployment or CI/CD logs | What actually reached production | Missing link back to the approval |
| Ticketing system | Approvals and change records, see Jira change tickets | Changes made without a ticket |
| Cloud or infrastructure logs | Infrastructure changes | Noisy entries that are not real changes |
Pick the source that best shows what changed in production, and explain how you cross-checked it against the others.
Steps to Build It
- Confirm the audit period dates and in-scope systems with your auditor
- Export from the chosen source with a timestamp, filters, and query recorded
- Remove entries that are not changes, and note why
- Add changes that bypassed the normal path, such as emergency changes
- Reconcile against a second source to look for gaps
- Add the fields auditors usually need: date, description, requester, approver, ticket or PR link
- Save the export with a note on who ran it and when
Check Completeness
Auditors often ask how you know the list is complete. Keep a short note on the reconciliation, for example comparing deployment counts with approved changes for the same period. Differences should be explained, not hidden. An unapproved change is a control deviation to record and discuss, not to leave out.
Common Mistakes
- Pulling only merged pull requests and missing direct deployments
- Using dates that do not match the audit period
- Removing records without documenting the reason
- Editing the export by hand so it no longer matches the source
- Leaving out emergency or hotfix changes
Checklist
- Audit period and scope confirmed
- Source of truth chosen and documented
- Export query, date, and owner recorded
- Reconciliation to a second source completed
- Emergency changes included
- Required fields present for each change
How AuditFlo.co Helps
AuditFlo.co helps teams keep audit-period evidence collection records organized, including change-related evidence from connected systems. It does not guarantee a population is complete, does not issue SOC 2 reports, does not certify compliance, and does not replace auditors. See also change management evidence for SOC 2.
Sources
- AICPA, SOC 2 Reporting on an Examination of Controls at a Service Organization, Guide
- AICPA, Trust Services Criteria (common criteria CC8.1, change management)