What evidence do auditors commonly ask for on A.1.5.5 Records of PII disclosures to third parties?

Disclosure log recording what data, to whom and when, for routine and exceptional disclosures alike; Source of the disclosure and the authority relied on, recorded per entry; Coverage of investigation and audit disclosures, not commercial sharing only; Retention and access controls over the disclosure log.

What is the most common gap auditors find on A.1.5.5?

Routine disclosures logged while law enforcement and audit disclosures are handled outside any record

ISO/IEC 27701:2025 · Annex A Table A.1 PIMS controls for PII controllers

`A.1.5.5` Records of PII disclosures to third parties

The organization must keep a record of each disclosure of personal data to a third party, stating which data went, to whom and when. The record covers disclosures in the ordinary course of business as well as others, for example those made for lawful investigations or outside audits, and for each it notes where the disclosure came from and what gave the authority to make it.

Source: ISO/IEC 27701:2025, A.1.5.5. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27701:2025 in the compliance library.

artefacts

held by a system

at each review

easy

to go live

SIEM / log platform

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Disclosure log recording what data, to whom and when, for routine and exceptional disclosures alike · SIEM / log platform
Retention and access controls over the disclosure log · SIEM / log platform

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Source of the disclosure and the authority relied on, recorded per entry · Document repository
Coverage of investigation and audit disclosures, not commercial sharing only · Policy repository / GRC workspace

First move

Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.

Common gaps auditors find

Routine disclosures logged while law enforcement and audit disclosures are handled outside any record
Authority for the disclosure not recorded, so the organization cannot later justify it
Log recording that a disclosure occurred without identifying what data left
Disclosures made by individual staff outside the logged route
Log kept by the function that made the disclosure rather than centrally, so no complete picture exists

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

A.1.5.4 Records of transfer of PII · A.2.2.2 Customer agreement