What evidence do auditors commonly ask for on A.1.3.8 PII controllers' obligations to inform third parties?

Register of third parties who have received personal data, per processing activity; Documented notification mechanism per third party with a named owner; Notification records with acknowledgements of receipt; Evidence channels are tested and kept live rather than assumed.

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

Third parties recorded at the point of sharing and never maintained, so the register is stale when it is needed

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

`A.1.3.8` PII controllers' obligations to inform third parties

When personal data has been passed to third parties, the organization must let them know of any correction, withdrawal or objection that affects it, and must have policies, procedures or mechanisms in place to do so. It must take reasonable steps given the technology available, set up and keep working communication channels with those third parties, give someone responsibility for running and maintaining the channels, and track whether the third parties confirm they received each notice.

Source: ISO/IEC 27701:2025, A.1.3.8. 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

hard

to go live

Vendor register / contract repository

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

none for this control

periodic reviewEvidence produced at each review

Notification records with acknowledgements of receipt · HR system / LMS
Evidence channels are tested and kept live rather than assumed · Document repository

governing documentDocuments that govern the control

Register of third parties who have received personal data, per processing activity · Vendor register / contract repository
Documented notification mechanism per third party with a named owner · Vendor register / contract repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Third parties recorded at the point of sharing and never maintained, so the register is stale when it is needed
Notifications sent with no acknowledgement tracked, so nobody knows whether they landed
Channel is a named individual's email address, which fails when that person leaves
Only consent withdrawals propagated, with corrections and objections left behind
Historic recipients from before the register existed never brought into scope

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.3.7 Access, correction or erasure · A.1.3.9 Providing copy of PII processed