# SOC 2 (2017 TSC) CC8.1 — Change Management - Source: https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc8-1-change-management - Section: [Compliance](https://support.icompaas.com/compliance) › [SOC 2 Trust Services Criteria (2017, with 2022 points of focus)](https://support.icompaas.com/compliance/soc-2-trust-services-criteria) › Common Criteria (Security) — CC8 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **SOC 2 (2017 TSC)**·Criterion `CC8.1`·high·Component: **Common Criteria (Security)** ## What this control requires > The entity authorizes, designs, develops or acquires, configures, documents, tests, approves, and implements changes to infrastructure, data, software, and procedures to meet its objectives. > > — SOC 2 (2017 TSC), Criterion CC8.1 ### In plain English The entity authorizes, designs, develops or acquires, configures, documents, tests, approves, and implements changes to infrastructure, data, software, and procedures to meet its objectives. In practice, this means you can prove you risk objectives-level controls on a defined cadence. ## Why it matters Every SOC 2 audit opinion is built control-by-control from the Trust Services Criteria. A missing or failing criterion produces an exception in the report, which buyers, partners and procurement teams read line-by-line during vendor reviews. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A SOC 2 auditor (under AT-C §§ 105/205) tests both design and operating effectiveness over the audit window. For each criterion they expect a written control, a control owner, a population of events, and a sample tested against the population — including remediation tickets for exceptions. Within **Common Criteria (Security)**, the assessor will trace your implementation back to the catalogue reference (Criterion CC8.1) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Risk.** Document the trigger, the owner and the cadence. - **Change.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Management.** Document the trigger, the owner and the cadence. - **Data.** Document the trigger, the owner and the cadence. - **Scope:** objectives, management. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Signed policy or standard documents the safeguard. Focus: Change Management. ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**ISO/IEC 27001:2022 A.5.11** — Return of assets](https://support.icompaas.com/compliance/iso-27001-2022/a-5-11-return-of-assets) - [**NIST SP 800-171 Rev. 3 3.13.10** — Cryptographic Key Establishment and Management](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-13-10-cryptographic-key-establishment-and-management) - [**HIPAA (45 CFR Part 164) 164.308(a)(5)(i)** — Security Awareness and Training](https://support.icompaas.com/compliance/hipaa/164-308-a-5-i-security-awareness-and-training) - [**GDPR Article 1** — Subject-matter and objectives](https://support.icompaas.com/compliance/gdpr/article-1-subject-matter-and-objectives) - [**NIST SP 800-53 Rev. 5 SC-12(2)** — Symmetric Keys](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-12-2-symmetric-keys) ## Related controls in SOC 2 (2017 TSC) - [**Criterion CC5.2** — Technology Control Activities to Support Objectives](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc5-2-technology-control-activities-to-support-objectives) - [**Criterion CC7.1** — Change Detection](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc7-1-change-detection) - [**Criterion CC2.2** — Internal Communications](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc2-2-internal-communications) - [**Criterion CC5.1** — Control Selection and Development](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc5-1-control-selection-and-development) - [**Criterion CC2.3** — External Communication on Internal Control Matters](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc2-3-external-communication-on-internal-control-matters) - [**Criterion CC5.3** — Control Deployment Through Policies](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc5-3-control-deployment-through-policies) ## References - [AICPA / ASEC — SOC 2 (2017 TSC)](https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2) - Catalogue identifier: `Criterion CC8.1` Topics: governance riskchange managementpolicy managementkey management ## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Start with the full SOC 2 implementation guide — scope, roadmap, evidence and how the assessment runs. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): The certificate most non-US customers ask for instead of SOC 2; the controls overlap enough to run one matrix for both. - [HIPAA compliance for SaaS: a practical implementation guide](https://support.icompaas.com/compliance/hipaa): If health-tech customers ask for SOC 2, they will also ask about the Security Rule; the two are usually evidenced from the same controls.