Change Management Controls for SOC 2 CC8.1
Build a change management process that satisfies SOC 2 CC8.1 without slowing down your engineering team.
What CC8.1 Requires
SOC 2 CC8.1 (Change Management) requires that your organization authorizes, designs, develops, acquires, configures, documents, tests, approves, and implements changes to infrastructure, data, software, and processes. In plain English: changes to production must go through a controlled process that prevents unauthorized or untested changes.
The Minimum Control Set
For most SaaS companies, CC8.1 is satisfied by implementing the following:
1. Code review requirement No code merges to the production branch without at least one peer review. Enforced via GitHub/GitLab branch protection.
2. Automated testing in CI All merges to the production branch must pass automated tests. Enforced via required CI status checks.
3. Deployment authorization Production deployments require either an approval step in the CI/CD pipeline or a documented "deploy" event in your change log.
4. Emergency change procedure A documented (and sparingly used) process for breaking-glass changes — who can authorize, what documentation is required after the fact.
Building the Evidence Trail
The biggest challenge with CC8.1 is demonstrating the control operated consistently across the 12-month observation period. You need evidence of:
- Every pull request that merged to the production branch
- The reviewer who approved each PR
- Whether automated tests passed before merge
- Deployment events linked to the merge
Tagging Changes by Type
Categorize your production changes:
| Type | Risk level | Required approvals | Testing required |
| Standard | Low | 1 reviewer | Automated CI |
| Significant | Medium | 2 reviewers | CI + manual QA |
| Emergency | High | 2 reviewers + manager notification | CI minimum, post-deploy verification |
| Infrastructure | High | 2 reviewers + infra team | Staging environment test |
The Emergency Change Process
Emergency changes happen. Your auditor won't penalize you for having them — they'll penalize you for having undocumented ones. Every emergency change needs:
SecureSpect's change management module lets you log emergency changes with the same structure as standard changes, tagging them as emergency for auditor visibility.