# SOC 2 (2017 TSC) P5.2 — Correction and Amendment of Personal Information - Source: https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p5-2-correction-and-amendment-of-personal-information - 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) › Privacy — P5 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **SOC 2 (2017 TSC)**·Criterion `P5.2`·medium·Component: **Privacy** ## What this control requires > The entity corrects, amends, or appends personal information based on information provided by data subjects and communicates such information to third parties, as committed or required, to meet the entity's objectives related to privacy. If a request for correction is denied, data subjects are informed of the denial and reason for such denial to meet the entity's objectives related to privacy. > > — SOC 2 (2017 TSC), Criterion P5.2 ### In plain English The entity corrects, amends, or appends personal information based on information provided by data subjects and communicates such information to third parties, as committed or required, to meet the entity's objectives related to privacy. In practice, this means you can prove you information 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. ## 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 **Privacy**, the assessor will trace your implementation back to the catalogue reference (Criterion P5.2) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Secure Development **Pipeline.** Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline. **Branch protection.** Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence. #### Code Review Testing **Pipeline.** Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this. ### Operational checklist - **Information.** 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. - **Privacy.** Document the trigger, the owner and the cadence. - **Personal.** Document the trigger, the owner and the cadence. - **Scope:** objectives, protection, management. ## Evidence to collect - **Code Repo Scan.** Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports. Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: Correction and Amendment of Personal Information (Original component: Privacy). ## Common pitfalls - CI security checks set to warn-only; the merge button is faster than the security feedback. ## 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.8.28** — Secure coding](https://support.icompaas.com/compliance/iso-27001-2022/a-8-28-secure-coding) - [**CIS Controls v8 16.3** — Perform Root Cause Analysis on Security Vulnerabilities](https://support.icompaas.com/compliance/cis-controls-v8/16-3-perform-root-cause-analysis-on-security-vulnerabilities) - [**BSI C5:2020 DEV-08** — Version Control](https://support.icompaas.com/compliance/bsi-c5-2020/dev-08-version-control) - [**ISO/IEC 27701:2025 A.1.4.5** — PII minimization objectives](https://support.icompaas.com/compliance/iso-27701-2025/a-1-4-5-pii-minimization-objectives) - [**GDPR Article 97** — Commission reports](https://support.icompaas.com/compliance/gdpr/article-97-commission-reports) ## Related controls in SOC 2 (2017 TSC) - [**Criterion P1.1** — Privacy Notice to Data Subjects](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p1-1-privacy-notice-to-data-subjects) - [**Criterion P6.2** — Recordkeeping of Authorized Personal Information Disclosures](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-2-recordkeeping-of-authorized-personal-information-disclosures) - [**Criterion CC1.3** — Organizational Structure and Reporting Lines](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc1-3-organizational-structure-and-reporting-lines) - [**Criterion P4.2** — Personal Information Retention Aligned with Privacy Objectives](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p4-2-personal-information-retention-aligned-with-privacy-objectives) - [**Criterion P2.1** — Communication of Data Subject Choices and Consequences](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p2-1-communication-of-data-subject-choices-and-consequences) - [**Criterion P5.1** — Data Subject Access to Personal Information](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p5-1-data-subject-access-to-personal-information) ## 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 P5.2` Topics: application securitydata protectionsecure developmentcode review testingdevsecopsprivacy 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.