SOC 2 (2017 TSC) P3.2 — Consent Management for Personal Information Collection

What this control requires

Obtains explicit consent for sensitive information. Documents explicit consent to retain information.

In plain English

Obtains explicit consent for sensitive information. In practice, this means you can prove you information management-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 Privacy, the assessor will trace your implementation back to the catalogue reference (Criterion P3.2) 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.

Operational checklist

• Information. Document the trigger, the owner and the cadence.
• Risk. 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: 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: Consent Management for Personal Information Collection (Original component: Privacy).

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

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.5 — Contact with authorities
• India DPDP Act 2023 LB-001 — Consent Quality & Management
• GDPR Article 2 — Material Scope
• NIST SP 800-53 Rev. 5 PL-2(3) — Plan And Coordinate With Other Organizational Entities
• HIPAA (45 CFR Part 164) 164.308(a)(5)(i) — Security Awareness and Training

Related controls in SOC 2 (2017 TSC)

• Criterion P4.1 — Limitation of Personal Information Use to Defined Purposes
• Criterion P3.1 — Personal Information Collection Aligned with Privacy Objectives
• Criterion P4.3 — Secure Disposal of Personal Information
• Criterion P7.1 — Maintenance of Accurate and Relevant Personal Information
• Criterion P8.1 — Inquiry and Complaint Management Process
• Criterion P1.1 — Privacy Notice to Data Subjects

References

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

Topics: governance riskprivacy managementpolicy management