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

A.2.5.6 Legally binding PII disclosures

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

A support employee at a booking software provider receives a call. The caller introduces himself as a police officer and, citing “imminent danger”, asks for the contact details and bookings of a guest. Shortly afterwards, an email arrives from an address that looks official. The employee sends the data. It later turns out that the request was forged and a stalker was behind it. A.2.5.6 requires you to reject requests to disclose personal data that are not legally binding, to consult the customer concerned before any disclosure, and to make contractually agreed disclosures only with the customer’s authorization.

Data you process for a customer has only been entrusted to you. Whoever hands it over without being obliged to or authorized by the customer leaves their role and endangers people whose data was placed in their care.

What does the standard require?

A.2.5.6 contains three rules that together form a chain of checks for every disclosure request.

  • Reject what is not binding. You turn down disclosure requests that have no binding legal force.
  • Consult the customer first. Before personal data is disclosed, you talk to the customer concerned.
  • Contractually agreed requests only with authorization. You accept requests for which the contract provides disclosure if the customer has authorized them.
  • Details in the contract. The implementation guidance allows details of the implementation to be set out in the customer contract.
  • Many sources. Requests can come from courts, tribunals and administrative authorities, and from any jurisdiction.

In practice

Check authenticity. Call the requesting body back on an official number you looked up yourself. Contact details in the request itself can be forged. Forged emergency requests are a known pattern for getting hold of data.

Check binding force. The named function, usually legal counsel together with the data protection officer, checks the legal basis, competence and form. You reject non-binding requests in writing and record the reason.

Treat foreign requests separately. If the request comes from a third country, it may not simply be binding under European law. In such cases, always clarify with legal counsel whether a mutual legal assistance route is foreseen.

Consult the customer. Inform the customer before the handover, state the request, basis, scope and deadline, and record who was consulted when and what they decided. If a prohibition on notification exists, document it under A.2.5.5.

Hand over only what is needed. Disclose only the data the request actually demands. Record every disclosure under A.2.5.4.

Secure contractual disclosures. If the contract provides for disclosures, for example to the customer’s auditors, obtain authorization for each request and file it. Without authorization, the request counts as not authorized.

Typical audit evidence

For A.2.5.6, auditors typically expect:

  • Procedure for checking disclosure requests covering authenticity, binding force, competence and consultation
  • Files on requests with the result of the check, rejection or release, and reasons
  • Proof of consultation with the customer, with date and decision
  • Authorizations for contractually agreed disclosures
  • Assessment of the legal bases for duties to hand over data (→ Legal Compliance Register)

KPI

% of legally binding disclosures with documented compliance review

What counts are all disclosures made in response to a binding request. Documented means: authenticity, binding force, competence, scope and consultation of the customer have been checked and recorded. The target is 100%.

Supporting KPIs:

  • Number of non-binding requests rejected per year
  • Share of disclosures with prior consultation of the customer
  • Number of forged requests detected

Disclosure is processing under Article 4(2) GDPR. Under Articles 28(3)(a) and 29, the processor may only carry it out on instructions, unless Union or Member State law requires it. A processor that decides on a handover itself determines the purpose of the processing and is treated as a controller in that respect under Article 28(10). For judgments and decisions from third countries, Article 48 states that they are only recognized or enforceable on the basis of an international agreement such as a mutual legal assistance treaty, without prejudice to other grounds for transfer under Chapter V (→ GDPR General Data Protection Regulation).

A.2.5.6 is where decisions on disclosure are made:

Sources

Frequently asked questions

How do I tell whether a request is legally binding?

A request is binding if it rests on a legal basis that obliges you to hand over data and comes from a competent body in the prescribed form, such as a court order or a formal order from an authority. An informal request by email or phone usually does not qualify. When in doubt, legal counsel decides.

Do I have to consult the customer before a binding disclosure as well?

The standard provides for consultation before every disclosure. If the law exceptionally prohibits any information, for example to protect an investigation, consultation is not possible. You then document the prohibition and give the information later, as soon as it is permitted.

What are contractually agreed disclosure requests?

These are requests for which the customer contract provides for disclosure, for example to the customer's statutory auditor or insurer. Here too, you hand over data only if the customer has authorized the specific request, and you keep the authorization on file.

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.