SOC 2 (2017 TSC) P5.1 — Data Subject Access to Personal Information

What this control requires

The entity grants identified and authenticated data subjects the ability to access their stored personal information for review and, upon request, provides physical or electronic copies of that information to data subjects to meet the entity's objectives related to privacy. If access is denied, data subjects are informed of the denial and reason for such denial, as required, to meet the entity's objectives related to privacy.

In plain English

The entity grants identified and authenticated data subjects the ability to access their stored personal information for review and, upon request, provides physical or electronic copies of that information to data subjects 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.1) and look for objective evidence on the latest two assessment cycles.

How to implement

1. Write a short policy stating intent, scope and named owner.
2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
4. Review on a documented cadence and capture the review in the risk register or compliance tracker.

Operational checklist

• Information. Document the trigger, the owner and the cadence.
• Access. Document the trigger, the owner and the cadence.
• Physical. 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.
• Scope: objectives, protection, management.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Data Subject Access to Personal Information (Original component: Privacy).

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.

• NIST SP 800-171 Rev. 3 3.13.4 — Information in Shared System Resources
• ISO/IEC 27001:2022 A.8.23 — Web filtering
• NIST SP 800-53 Rev. 5 SC-4 — Information In Shared System Resources
• BSI C5:2020 IDM-08 — Confidentiality of authentication information
• CIS Controls v8 9.2 — Use DNS Filtering Services

Related controls in SOC 2 (2017 TSC)

• Criterion P6.7 — Data Subject Request for Information and Disclosure Accounting
• Criterion CC6.4 — Physical Access Controls
• Criterion P1.1 — Privacy Notice to Data Subjects
• Criterion P6.2 — Recordkeeping of Authorized Personal Information Disclosures
• Criterion CC1.5 — Accountability for Internal Control Responsibilities
• Criterion P4.2 — Personal Information Retention Aligned with Privacy Objectives

References

• AICPA / ASEC — SOC 2 (2017 TSC)
• Catalogue identifier: Criterion P5.1

Topics: identity accessdata protectionidentity managementaccess reviewprivacy managementprivileged access