# SOC 2 (2017 TSC) CC7.1 — Change Detection - Source: https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc7-1-change-detection - 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) — CC7 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **SOC 2 (2017 TSC)**·Criterion `CC7.1`·high·Component: **Common Criteria (Security)** ## What this control requires > To meet its objectives, the entity uses detection and monitoring procedures to identify (1) changes to configurations that result in the introduction of new vulnerabilities, and (2) susceptibilities to newly discovered vulnerabilities. > > — SOC 2 (2017 TSC), Criterion CC7.1 ### In plain English To meet its objectives, the entity uses detection and monitoring procedures to identify (1) changes to configurations that result in the introduction of new vulnerabilities, and (2) susceptibilities to newly discovered vulnerabilities. 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 CC7.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. #### Vulnerability Management **Scanners.** Pair an unauthenticated scanner (Nessus / Qualys / Tenable.io) for external surface with an authenticated agent for OS/library CVEs on every host. **SLA.** Document remediation SLAs by CVSS / EPSS: critical 7 days, high 30 days, medium 90 days; report monthly trend to leadership. **Containers.** Scan images in CI (Trivy / Grype / Snyk Container) AND at runtime; block deploys on critical findings without exception. ### 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. - **Scope:** objectives, detection, 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 Detection (Original component: System Operations). ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. - Scans that hit only the perimeter; missing authenticated scans of OS, runtime libs and base images so most CVEs are invisible. ## 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.12.2** — Plan of Action and Milestones](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-12-2-plan-of-action-and-milestones) - [**NIST SP 800-53 Rev. 5 CA-7(1)** — Independent Assessment](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ca-7-1-independent-assessment) - [**CIS Controls v8 7.1** — Establish and Maintain a Vulnerability Management Process](https://support.icompaas.com/compliance/cis-controls-v8/7-1-establish-and-maintain-a-vulnerability-management-process) - [**BSI C5:2020 OIS-05** — Contact with Relevant Government Agencies and Interest Groups](https://support.icompaas.com/compliance/bsi-c5-2020/ois-05-contact-with-relevant-government-agencies-and-interest-groups) ## Related controls in SOC 2 (2017 TSC) - [**Criterion CC8.1** — Change Management](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc8-1-change-management) - [**Criterion CC3.1** — Objective Setting](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc3-1-objective-setting) - [**Criterion CC3.2** — Risk Identification](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc3-2-risk-identification) - [**Criterion CC3.4** — Change Identification](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc3-4-change-identification) - [**Criterion CC3.3** — Fraud Risk Assessment](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc3-3-fraud-risk-assessment) - [**Criterion CC4.1** — Control Monitoring](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc4-1-control-monitoring) ## 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 CC7.1` Topics: governance riskchange managementcontinuous monitoringpolicy managementvulnerability 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.