SOC 2 · P - Privacy
SOC 2 P5.2: P5.2 Correction of personal information
SOC 2 P5.2 covers P5.2 Correction of personal information. The held text names 4 evidence records for it, the first being Correction request log and outcomes. The common gap an assessor flags is Corrections not propagated to third parties.
Personal information is corrected, amended or supplemented on information from data subjects, and passed to third parties where committed or legally required; denied correction requests are explained. Points of focus: denials of access are explained in writing with any legal basis and the right to challenge where law allows; data subjects can update or correct their information and corrections reach third parties that received it; and denials of correction are explained in writing with how to appeal. The 2022 revision adds, for data processors, handling data controllers' update and correction requests under the service agreement, and passing on updates, corrections and deletion requests to recipients.
What evidence supports P5.2?
- Data subject rightsCorrection request log and outcomes
- Data subject rightsEvidence corrections and deletion requests were propagated to recipients
- Data subject rightsTemplate letters explaining denials and appeal routes
- Data subject rightsLog of update requests received from customers acting as controllers (processor role)
Where this requirement comes from
This is our own statement of SOC 2 P5.2, read from the copy we hold (issuer free complete copy) and stated in our words, not the standard verbatim. The framework as we hold it.
Common gaps an assessor flags
- Corrections not propagated to third parties
- Denials not explained in writing
- No appeal route offered
How it maps to ISO 27001:2022
No reviewed link is held for this control.
A link is a topical overlap with a confidence and a reason. It does not establish that meeting one requirement satisfies the other, and it is not certification.