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.

Related controls in SOC 2 (2017 TSC)

References

Topics: application securitydata protectionsecure developmentcode review testingdevsecopsprivacy management