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

A.2.5.5 Notification of PII disclosure requests

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

A cloud storage provider receives a court order to hand over the files of a specific user account. The account belongs to a business customer, a firm of tax advisers. Legal checks the order, the data is handed over, the case is closed. The firm hears nothing about it, although the order contains no secrecy requirement. A.2.5.5 requires you to notify the customer of every legally binding request to disclose their personal data.

The customer remains responsible for the data, even when an authority knocks on your door. They need to know what happens to it in order to meet their own obligations, towards data subjects for instance, and to respond legally themselves if needed.

What does the standard require?

A.2.5.5 governs the moment a state body wants access to data you process for a customer.

  • Notification of binding requests. If you receive a legally binding request to disclose personal data, for example from a law enforcement authority, you inform the customer.
  • Agreed period and agreed procedure. Notification takes place within the agreed time and according to a coordinated procedure. This procedure can be part of the customer contract.
  • Prohibition on notification. Some requests themselves demand that nobody be informed. As an example, the standard names a prohibition under criminal law that protects the confidentiality of an investigation.

In practice

Create an entry point. Letters from authorities reach companies in many ways: by post to head office, by email to support, by fax to accounting. Decide that all such letters go immediately to a named function.

Classify requests. The named function checks whether the request is legally binding, whether the requesting body is competent, which data is affected and whether a prohibition on notification exists. For the question of binding force, A.2.5.6 applies.

Inform the customer. The message names the requesting body, the legal basis, the scope of the data demanded, the deadline set and the planned response. This lets the customer consider steps of their own.

Deal with prohibitions. If a prohibition exists, document it with its basis and duration. It is common to give the notification later, once the prohibition lapses, and to record the date.

Anchor the procedure in the contract. Put the deadline, channel and content of the notification into the customer contract or an annex. Both sides then know what to expect when it matters.

Include subcontractors. Authorities sometimes approach your subcontractors directly. Oblige them by contract to inform you without delay about any such request, so that you in turn can notify the customer on time.

Consider a report. Some providers regularly publish a transparency report with the number of requests from authorities. The standard does not require this, and for many customers it is a sign of trustworthiness.

Typical audit evidence

For A.2.5.5, auditors typically expect:

  • Procedure for disclosure requests covering entry point, checks, notification and handling of prohibitions
  • Contract clause or annex with deadline and procedure for notification
  • Files on requests received with the result of the check, date of notification or a documented prohibition
  • Contact list of competent authorities and internal contacts (→ Stakeholder Communication Plan)
  • Training records for staff in contact with customers (→ Training Register)

KPI

% of PII disclosure requests with timely notification to controller

What counts are all legally binding requests without a prohibition on notification. Requests with a prohibition are kept separately and counted once the prohibition lapses. Timely means: within the agreed time. The target is 100%.

Supporting KPIs:

  • Number of legally binding requests per year
  • Share of requests with a prohibition on notification where the information was given later
  • Average time from receipt of a request to its classification by the named function

Article 28(3)(a) GDPR contains the matching rule: if Union or Member State law requires the processor to process, the processor informs the controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest. Article 48 applies to orders from courts and authorities in third countries: they are only recognized or enforceable if based on 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.5 belongs to a trio for handling requests from authorities:

Sources

Frequently asked questions

What do I do if I am prohibited from notifying?

Then you do not inform the customer for as long as the prohibition applies. Record the prohibition, its basis and its duration. A proven approach is to give the notification later, as soon as it becomes permissible, and to document the date.

Does the control also apply to requests that are not binding?

A.2.5.5 speaks of legally binding requests. You reject requests without binding force under A.2.5.6. Many processors still inform the customer about those as well, because such a request can be a sign of ongoing proceedings.

Who may handle such requests?

A named function, usually legal counsel together with the data protection officer. All other staff, especially in support, forward letters from authorities there at once and hand over no data themselves.

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.