Frameworks / SOC 2 / SOC2-P6.6 SOC 2 SOC2-P6.6: P6.6 Notifying breaches and incidents Affected individuals, regulators and others are told of breaches and incidents as privacy objectives require. Points of focus: a process determines whether a privacy breach must be notified, by what method, by when and to whom (added in 2022); and notice of breaches and incidents is given to affected individuals, regulators and others.
Maintained by Gerard Blokdyk · Control text last updated 21 May 2026 What else in your programme already covers this This control maps to 74 controls across 26 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
6.1 General 6.13.1 Management of information security incidents and improvements 6.15.1 Compliance with legal and contractual requirements 7.2.7 Joint PII controller 7.3 Obligations to PII principals 7.3.1 Determining and fulfilling obligations to PII principals 7.3.10 Automated decision making 7.3.3 Providing information to PII principals 7.3.7 PII controllers' obligations to inform third parties 7.3.9 Handling requests 7.5.2 Countries and international organizations to which PII can be transferred 8.3 Obligations to PII principals 8.3.1 Obligations to PII principals 8.5.1 Basis for PII transfer between jurisdictions 8.5.2 Countries and international organizations to which PII can be transferred 8.5.4 Notification of PII disclosure requests 8.5.5 Legally binding PII disclosures 8.5.6 Disclosure of subcontractors used to process PII 5.19 Information security in supplier relationships 5.24 Information security incident management planning and preparation 5.26 Response to information security incidents 5.31 Legal, statutory, regulatory and contractual requirements 5.34 Privacy and protection of personal identifiable information (PII) 5.5 Contact with authorities CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents CIS-17.4 Establish and Maintain an Incident Response Process CIS-17.6 Define Mechanisms for Communicating During Incident Response CIS-17.9 Establish and Maintain Security Incident Thresholds 5.26 Response to information security incidents 5.31 Legal, statutory, regulatory and contractual requirements 5.34 Privacy and protection of PII 5.5 Contact with authorities 7.4 Communication A.8 Information for interested parties of AI systems A.8.4 Communication of incidents A.8.5 Information for interested parties IR-2 Incident Response Training IR-4 Incident Handling IR-6 Incident Reporting IR-2 Incident Response Training IR-4 Incident Handling IR-6 Incident Reporting NIST-CSF-RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents NIST-CSF-RS.CO-03 Information is shared with designated internal and external stakeholders GDPR-Art.33 Notification of a personal data breach to the supervisory authority GDPR-Art.34 Communication of a personal data breach to the data subject 4.2.2 Legal and regulatory requirements 8.4.3 Warning and communication APPI-A26 Report of Leakage to the Commission and Notification to the Person CPS234-35 APRA Notification of Material Incidents within 72 Hours C5-OPS-21 Involvement of Cloud Customers in the Event of Incidents Art.23.1 Notify significant incidents to the CSIRT or competent authority, and warn affected service recipients 03.06.02 Incident Monitoring, Reporting, and Response Assistance 12.10.1 12.10.1 Incident response plan ready for activation Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected .
Other controls in P - Privacy You are reading one control. How much of SOC 2 have you already done? SOC 2 SOC2-P6.6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of SOC 2 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 49 of 61 SOC 2 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 193 were rejected on the NIST SP 800-53 Rev 5 pair alone.
Query this from an agent The graph holds this control, the 74 it maps to, and the evidence behind each claim, over MCP and REST.