Zum Hauptinhalt springen
ISO/IEC 27701:2025 · Annex A, Table A.2 · Control for PII processors

A.2.5.4 Records of PII disclosures to third parties

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27701:2025GDPR

A hosting provider receives a request from the police for information on a user account that a customer runs on its platform. An administrator exports access logs and sends them by email. Months later, the customer asks about it because a data subject has requested access. Nobody can say which data exactly was handed over, on what basis and who approved it. A.2.5.4 requires you to record every disclosure of personal data to third parties: which data, to whom and when, together with its origin and the authority behind it.

Disclosures cannot be undone. That makes it all the more important that they can be explained later, to the customer, to data subjects and to a supervisory authority.

What does the standard require?

A.2.5.4 has the same title as A.1.5.5 for controllers. For the processor, the standard also stresses where a disclosure comes from and who authorized it.

  • Record disclosures. You record when personal data goes to third parties: which data, to whom and at what time.
  • Normal operations. Disclosures that happen in the ordinary course of business are recorded too.
  • Exceptional disclosures. Further disclosures, for instance as part of lawful investigations or external audits, are recorded as well.
  • Origin and authority. The record states where the disclosure came from and what authority it relied on.

In practice

Define third parties. Decide who counts as a third party for the control. Subcontractors and the customer itself are not among them. Typical third parties are authorities, courts, external auditors, insurers, lawyers and recipients to whom you pass data on the customer’s instruction.

Document routine by route. For regular disclosures on behalf of the customer, such as to a shipping or payment service, describe the route once: recipient, data scope, customer instruction. The technical logs then prove the individual transactions.

Record the exceptional one by one. Every disclosure to authorities, courts or auditors gets its own entry with date, recipient, data scope, source system, legal basis or order, approval and whether the customer was informed.

Record who stood behind it. As a processor, note on whose initiative you acted: on the customer’s instruction or at the demand of an authority. The answer to later questions differs considerably depending on which.

Involve the customer. Set out in the contract how the customer gains insight into the records, for example as an annual overview or on request. If a prohibition kept you from informing them at once, record when the information was given later.

Protect the records. Entries about requests from authorities can be confidential themselves. Restrict access and decide how long they are kept.

Typical audit evidence

For A.2.5.4, auditors typically expect:

  • Register of disclosures with data, recipient, date, origin and authority
  • Description of regular disclosure routes with recipient, scope and customer instruction
  • Technical logs proving individual disclosures (→ Asset Register for the systems involved)
  • Procedure for exceptional disclosures with approval and a duty to document
  • Retention rule for the records (→ Records Retention Schedule)

KPI

% of processor third-party disclosures with complete records

What counts are all exceptional disclosures and all regular disclosure routes. Complete means: data, recipient, time, origin and authority are recorded. The target is 100%. A good check is a comparison with the legal department’s inbox: every request from an authority that led to a handover should have an entry.

Supporting KPIs:

  • Number of exceptional disclosures per year
  • Share of entries with documented approval
  • Share of regular disclosure routes with a current description

Every disclosure is processing under Article 4(2) GDPR and, at the processor, may only take place on documented instructions under Article 28(3)(a), unless Union or Member State law requires it. Article 4(10) excludes processors from the definition of a third party. Under Article 4(9), public authorities that receive data in the framework of a particular inquiry are not regarded as recipients. The standard nevertheless explicitly includes such disclosures in the record. The customer needs your records to answer access requests under Article 15(1)(c) and for their accountability (→ GDPR General Data Protection Regulation).

Annex D of the standard also maps A.2.5.4 to Article 30(1)(d): the controller’s record names the categories of recipients to whom data have been or will be disclosed. Your records give the customer the basis for that.

A.2.5.4 makes disclosures traceable:

Sources

Frequently asked questions

Is a subcontractor a third party in the sense of the control?

In GDPR terms, no, because processors are excluded from the definition of a third party. Subcontractors are covered by the controls on their disclosure and engagement. Third parties are, for example, authorities, courts, external auditors, lawyers for the other side or other recipients to whom you pass data on instruction.

Do I have to record routine disclosures one by one?

No. For regular disclosures, such as through an interface to a payment service on the customer's behalf, a description of the route with recipient and data scope, backed by the technical logs, is usually enough. Individual entries are needed mainly for exceptional disclosures.

How long do I keep the records?

The standard sets no period. A common approach is to keep records of exceptional disclosures at least for the term of the customer contract and beyond that for the usual limitation periods. Record the period in your retention schedule.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.