# SOC 2 (2017 TSC) P6.1 — Third-Party Disclosure with Data Subject Consent - Source: https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-1-third-party-disclosure-with-data-subject-consent - 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 — P6 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **SOC 2 (2017 TSC)**·Criterion `P6.1`·high·Component: **Privacy** ## What this control requires > The entity discloses personal information to third parties with the explicit consent of data subjects and such consent is obtained prior to disclosure to meet the entity's objectives related to privacy. > > — SOC 2 (2017 TSC), Criterion P6.1 ### In plain English The entity discloses personal information to third parties with the explicit consent of data subjects and such consent is obtained prior to disclosure 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. 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 P6.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. - **Risk.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Vendor.** Document the trigger, the owner and the cadence. - **Management.** Document the trigger, the owner and the cadence. - **Scope:** objectives, protection, management. ## Evidence to collect - **Vendor Risk Management.** `vendor_risk_management` evidence Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Focus: Third-Party Disclosure with Data Subject Consent (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. - [**BSI C5:2020 OIS-03** — Interfaces and Dependencies](https://support.icompaas.com/compliance/bsi-c5-2020/ois-03-interfaces-and-dependencies) - [**ISO/IEC 27001:2022 A.5.20** — Addressing information security within supplier agreements](https://support.icompaas.com/compliance/iso-27001-2022/a-5-20-addressing-information-security-within-supplier-agreements) - [**GDPR Article 76** — Confidentiality](https://support.icompaas.com/compliance/gdpr/article-76-confidentiality) - [**ISO/IEC 27701:2025 A.1.5.2** — Basis for transfer](https://support.icompaas.com/compliance/iso-27701-2025/a-1-5-2-basis-for-transfer) - [**NIST SP 800-53 Rev. 5 PL-8(2)** — Supplier Diversity](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pl-8-2-supplier-diversity) ## Related controls in SOC 2 (2017 TSC) - [**Criterion P6.4** — Third-Party Privacy Commitments](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-4-third-party-privacy-commitments) - [**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 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 P6.5** — Third-Party Breach Notification Commitments](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-5-third-party-breach-notification-commitments) - [**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) ## 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 P6.1` Topics: data protectionvendor riskvendor managementprivacy managementsupply chain securitythird party monitoring ## 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.