SOC 2 Change Management Policy Template (CC8.1)
A SOC 2 Change Management Policy documents how code and infrastructure changes move from development into production, requiring ticket tracking, independent peer code review, automated testing, and segregation of duties. Auditors test CC8.1 by sampling 15–25 production deployments across your Type II window.
Free Markdown Template
Copy or download the change management policy
Replace bracketed [PLACEHOLDERS] with your actual stack
# Change Management and SDLC Policy (SOC 2 CC8.1)
**Document Owner:** [VP Engineering / CTO]
**Approved By:** [CEO / CTO]
**Effective Date:** [YYYY-MM-DD]
**Review Cadence:** Annual
**Applies To:** All production application code, infrastructure-as-code (IaC), database migrations, and configuration changes
---
## 1. Purpose
This policy ensures that all changes to [Company Name]'s production systems are authorized, tested, independently peer-reviewed, and logged prior to deployment.
## 2. Change Categories
- **Standard Changes:** Routine feature releases, bug fixes, dependency updates, and IaC updates deployed through the normal Pull Request (PR) and CI/CD pipeline.
- **Emergency Changes:** Urgent security patches or production outage hotfixes requiring immediate deployment outside normal lead times.
- **Configuration / Schema Changes:** Production infrastructure settings, feature flags affecting security, or database migrations tracked through version control or change tickets.
## 3. Standard Change Lifecycle
1. **Change Request:** Changes are tracked in [Linear / Jira / GitHub Issues] describing scope and intent (or documented directly in the linked Pull Request).
2. **Development & Isolation:** Code is developed on feature branches isolated from production. Production data is not copied into local developer machines.
3. **Automated Testing:** Every PR targeting `main` triggers automated CI checks ([GitHub Actions / CircleCI]) including unit/integration tests and security/lint checks.
4. **Independent Peer Review (Segregation of Duties):**
- Protected branches (`main` / `production`) enforce at least **one independent reviewer approval** before merge.
- Authors cannot approve their own pull requests.
- Force pushes and direct commits to protected branches are blocked via repository rulesets (including for administrators).
5. **Deployment:** Production releases deploy exclusively through automated CI/CD pipelines linked to merged commits, maintaining a complete commit-to-deploy audit trail.
## 4. Emergency Changes (Hotfixes)
When an active production outage or critical vulnerability requires immediate action:
1. Verbal or Slack authorization is obtained from [CTO / On-Call Lead] and logged in an incident or change ticket.
2. If branch protection must be temporarily bypassed, the override is logged, and an independent peer review is completed retrospectively within **[24 / 48] hours**.
## 5. Rollback Procedures
Every production deployment must support rapid rollback via CI/CD re-deployment of the previous verified artifact or Git revert commit. Database migrations are designed to be backward-compatible whenever possible.
## 6. Infrastructure as Code (IaC)
Production cloud infrastructure changes ([Terraform / Pulumi / CloudFormation]) follow the same PR review and approval workflow as application code. Manual console changes are limited to break-glass emergencies and must be reconciled back into IaC within [5] business days.
## 7. Policy Review
This policy is reviewed annually and updated whenever CI/CD tooling, branch protection rules, or deployment workflows change.
Evidence Mapping
What auditors test beyond this policy
A signed policy document only satisfies design intent. During SOC 2 fieldwork, your CPA auditor samples operating evidence against each clause below:
| Policy Requirement | Control | Evidence Your Auditor Requests |
|---|---|---|
| Branch protection enforces ≥1 review & blocks direct pushes | CC8.1 | GitHub branch protection / ruleset API output or screenshot showing required approving reviews, status checks, and admin enforcement enabled. |
| Complete population of production changes | CC8.1 | Full list of merged PRs or production deployments across the observation period so the auditor can pick 15–25 random samples. |
| Sampled PRs show independent approval & passing CI | CC8.1 | For each sampled deployment: linked ticket/PR, author vs. approver identity, approval timestamp prior to merge, and passing CI run. |
| Emergency overrides documented & retroactively reviewed | CC8.1 | Audit log of any emergency hotfix or branch-rule bypass paired with its incident ticket and post-deploy peer review. |
- Leaving 'Include administrators' unchecked in GitHub branch protection, allowing founders to merge their own PRs without review and creating audit exceptions.
- Writing 'all changes require a formal Change Advisory Board (CAB) meeting' in a 15-person startup policy when you actually ship 10 times a day via GitHub PRs.
- Making untracked Terraform or AWS console clicks in production without reconciling them through a reviewed pull request.
Related guide: What auditors expect for SOC 2 change approval evidence
Frequently Asked Questions
Change Management Policy FAQ
- Do we need a Change Advisory Board (CAB) for SOC 2?
- No. Modern SOC 2 auditors accept automated CI/CD workflows where GitHub branch protection enforces independent peer code review, automated tests, and commit-to-deploy traceability. Never copy legacy CAB language into a startup policy.
- What if we only have one engineer or two co-founders?
- If two engineers exist, cross-review each other's PRs. If there is literally only one engineer, document a compensating control (such as automated CI/security checks plus periodic secondary code review by an advisor or CTO) and confirm it with your auditor upfront.
- How many PRs do SOC 2 Type II auditors sample?
- For an annual Type II period with daily deployments, AICPA sampling guidance typically leads auditors to pull 15 to 25 random merged PRs from your full deployment population.
Skip manual fill-in-the-blank edits
Draft this policy directly from your real infrastructure.
Screenata scans your AWS, GCP, GitHub, and identity provider read-only, writes auditor-ready policies tied to real controls, and collects signed evidence automatically.