# SOC 2 (2017 TSC) P6.5 — Third-Party Breach Notification Commitments - Source: https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-5-third-party-breach-notification-commitments - 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.5`·high·Component: **Privacy** ## What this control requires > The entity obtains commitments from vendors and other third parties with access to personal information to notify the entity in the event of actual or suspected unauthorized disclosures of personal information. Such notifications are reported to appropriate personnel and acted on in accordance with established incident-response procedures to meet the entity's objectives related to privacy. > > — SOC 2 (2017 TSC), Criterion P6.5 ### In plain English The entity obtains commitments from vendors and other third parties with access to personal information to notify the entity in the event of actual or suspected unauthorized disclosures of personal information. 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.5) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Incident Response **Runbook.** Maintain a runbook keyed by incident type with named roles (IC, comms, scribe), an out-of-band comms channel, and a 72-hour timeline for external notification. **Tabletop.** Run a quarterly tabletop exercise (ransomware, insider, supply-chain) and feed gaps back into the runbook. ### Operational checklist - **Information.** Document the trigger, the owner and the cadence. - **Risk.** Document the trigger, the owner and the cadence. - **Access.** Document the trigger, the owner and the cadence. - **Incident.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Scope:** objectives, response, management, breach notification commitments. ## Evidence to collect - **Vendor Risk Management.** `vendor_risk_management` evidence - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Signed policy or standard documents the safeguard. Focus: Third-Party Breach Notification Commitments (Original component: Privacy). ## Common pitfalls - Runbooks that name a role but no person, or list a paging channel that no longer exists. ## 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. - [**CIS Controls v8 15.4** — Ensure Service Provider Contracts Include Security Requirements](https://support.icompaas.com/compliance/cis-controls-v8/15-4-ensure-service-provider-contracts-include-security-requirements) - [**BSI C5:2020 PS-01** — Physical Security and Environmental Control Requirements](https://support.icompaas.com/compliance/bsi-c5-2020/ps-01-physical-security-and-environmental-control-requirements) - [**NIST SP 800-53 Rev. 5 MA-3(1)** — Inspect Tools](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ma-3-1-inspect-tools) - [**ISO/IEC 27001:2022 A.5.19** — Information security in supplier relationships](https://support.icompaas.com/compliance/iso-27001-2022/a-5-19-information-security-in-supplier-relationships) - [**ISO/IEC 27701:2025 A.2.5.5** — Notification of requests](https://support.icompaas.com/compliance/iso-27701-2025/a-2-5-5-notification-of-requests) ## 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 P6.1** — Third-Party Disclosure with Data Subject Consent](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-1-third-party-disclosure-with-data-subject-consent) - [**Criterion P6.6** — Breach and Incident Notification to Stakeholders](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-6-breach-and-incident-notification-to-stakeholders) - [**Criterion P3.1** — Personal Information Collection Aligned with Privacy Objectives](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p3-1-personal-information-collection-aligned-with-privacy-objectives) - [**Criterion P6.3** — Logging and Retention of Unauthorized Disclosure Incidents](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-3-logging-and-retention-of-unauthorized-disclosure-incidents) - [**Criterion P8.1** — Inquiry and Complaint Management Process](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p8-1-inquiry-and-complaint-management-process) ## 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.5` Topics: governance riskvendor riskvendor managementincident responseprivacy managementsupply chain security ## 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.