At a housing company, a man calls, introduces himself as a police officer and asks for a tenant’s phone number and rental history. The caretaker gives him both over the phone. A year later, the tenant asks who has received his data. Nobody knows about the call, and whether it really came from the police can no longer be established. A.1.5.5 requires every disclosure of personal data to third parties to be recorded: what was disclosed, to whom, when, from which source and on what authority.
Disclosures are moments in which the organization lets go of control over data. A clean record makes them verifiable afterwards, towards data subjects, supervisory authorities and auditors.
What does the standard require?
The control names three mandatory details, and the implementation guidance adds two more.
- What, to whom, when. Every disclosure to third parties is recorded with the data disclosed, the recipient and the time.
- Disclosures in normal operations. Sharing that is part of normal business is recorded as well.
- Additional disclosures. Disclosures for a particular reason also have to be recorded; the standard gives lawful investigations and external audits as examples.
- Source and authority. Every record states where the disclosure came from and what the authority to release the data rests on.
In practice
Capture regular disclosures. Reports to the tax office and social insurance, data sent to banks or tax advisers: these recipients follow from the record of processing activities and are kept as recurring entries with a frequency.
Route ad hoc disclosures through a central point. Requests from police, public prosecutors, courts, tax investigators, lawyers or insurers go to a designated function, usually privacy or legal. There, the request is asked for in writing, the authority is checked, the scope is limited to what is needed and the release is approved.
Define mandatory fields. Data categories and scope, recipient, date, source within the organization, basis of the authority with case reference, approving person. For requests from authorities, a copy of the written request belongs with it.
Secure telephone requests. Information is given over the phone only after calling back on an officially known number, and as a rule only after a written request. This protects against deception attempts by which unauthorized people try to obtain data.
Plan for external audits. Certification audits, statutory audits of financial statements and tax audits involve inspection of personal data. Record in advance which documents will be shown, and enter auditor, scope and date afterwards. That way, this disclosure stays traceable too.
Protect the records themselves. A log of investigation requests is sensitive. Access stays limited to a few people, and the retention period is set in the retention schedule.
Typical audit evidence
For A.1.5.5, auditors typically expect:
- Register of disclosures with content, recipient, date, source and authority
- Procedure for requests from authorities with a central point and approval (→ A.5.5 Contact with Authorities)
- Written requests and review notes for individual disclosures
- Legal provisions that require or permit disclosures (→ Legal Compliance Register)
- Confidentiality agreements with external auditors and evidence of the scope of their inspection
KPI
% of PII disclosures to third parties with complete records
Complete means: all five details are recorded, and for ad hoc disclosures also the request and the approval. The target is 100%. A sample is easy to draw from incoming mail from authorities: every request must have an entry.
Supporting KPIs:
- Share of requests from authorities that went through the central point
- Average time from receipt to decision for ad hoc disclosures
- Number of requests refused for lack of demonstrated authority
Link to the GDPR
Article 30(1)(d) GDPR requires the record of processing to list the categories of recipients to whom data has been or will be disclosed. Article 15(1)(c) gives data subjects the right to learn the recipients or categories of recipients, and the second sentence of Article 19 obliges the controller to inform them on request about the recipients to whom rectifications or erasures were communicated. Disclosures to authorities often rest on a legal obligation under Article 6(1)(c). Restrictions of data subject rights, for example to protect investigations, are only possible on the basis of legislative measures under Article 23. Article 5(2) requires all of this to be demonstrable (→ GDPR General Data Protection Regulation).
Related controls
A.1.5.5 completes the group of transfer controls:
- A.1.5.4 Records of transfer of PII: records transfers to and from third parties.
- A.1.4.3 Limit processing: limits disclosures to what is needed from the outset.
- A.2.5.4 Records of PII disclosures to third parties: places the same requirement on PII processors.
- A.2.5.6 Legally binding PII disclosures: governs how processors handle binding demands for disclosure.
- A.5.5 Contact with Authorities: sets who communicates with authorities.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.5.5, and Annex B, B.1.5.5: Records of PII disclosure to third parties
- Regulation (EU) 2016/679 (GDPR), Articles 5, 6, 15, 19, 23 and 30
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles