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

A.2.5.9 Change of subcontractor to process PII

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

A hosting provider moves its customers’ backups from a regional data centre operator to a large cloud provider headquartered in the United States. The migration runs over a weekend, and customers learn about it in the next newsletter. A hospital among the customers would have objected because of the parent company outside the EU. Now its patient data is already with the new provider. A.2.5.9 requires you, where general written authorization exists, to inform the customer of every planned addition or replacement of a subcontractor and so give them the opportunity to object.

General authorization saves effort on both sides, because not every subcontractor has to be approved individually. It only works, though, if the customer learns of changes in time and can genuinely say no.

What does the standard require?

A.2.5.9 completes the series of controls on subcontractors. It concerns the moment the chain changes.

  • Announcement under general authorization. If the customer has given general written authorization for the use of subcontractors, you inform them of every intended addition or replacement.
  • Opportunity to object. The information exists so that the customer can object to the change. It therefore has to come before the change.
  • Authorization before processing. If you change the organization to which you pass processing, the customer’s written authorization is needed before the new subcontractor processes data.
  • Form of authorization. It can consist of suitable clauses in the customer contract or of a separate agreement for the individual case.

In practice

Set up a fixed procedure. Decision on the change, announcement to the customers concerned, end of the objection period, handling of objections, activation. Each step has a responsible person and a date.

Make the announcement complete. It names the new or replaced subcontractor, its service, the data concerned, the place of processing, the basis for transfers to third countries, the planned start and the objection period.

Offer a channel customers can subscribe to. An email notification or a customer portal with subscriptions reaches the right contacts. A changed web page without any notice is hardly enough.

Take objections seriously. Review every objection, discuss alternatives with the customer and document the decision. Where the contract provides for it, the customer has a special termination right.

Identify the customers concerned. A change often affects only the customers of a particular service. Use the list per service to work out whom it concerns, and inform exactly those customers. Sending every change to everyone creates noise in which important announcements get lost.

Settle emergencies in advance. If a subcontractor fails suddenly, through insolvency for example, there is no time for a regular period. Set out in the contract how to proceed then, for instance with a pre-approved replacement service.

Enforce the change process downwards too. Oblige your subcontractors to inform you in advance about their own changes. Only then can you tell your customers in time.

Typical audit evidence

For A.2.5.9, auditors typically expect:

  • Contract clauses on general authorization, the notice period, objections and emergencies
  • Announcements to customers with date, content and objection period (→ Stakeholder Communication Plan)
  • Proof that the new subcontractor started after the period had passed (→ Change Log)
  • Documented objections and the decisions taken on them
  • Updated list of subcontractors (→ Supplier Register)

KPI

% of subcontractor changes announced to customers before processing starts

What counts are all additions and replacements of subcontractors that process personal data from assignments. Announced means: the information reached every customer concerned, and the agreed objection period had passed before the first data flowed. The target is 100%.

Supporting KPIs:

  • Number of objections per change and how they were resolved
  • Average time between announcement and start
  • Number of emergency changes with information given afterwards

The second sentence of Article 28(2) GDPR contains the same duty: where general written authorization exists, the processor informs the controller of every planned addition or replacement of other processors, so that the controller can object. The provision distinguishes specific authorization for each individual processor from general authorization with announcement. Under Article 28(4), the same data protection obligations apply to the new subcontractor, and Article 28(3)(d) writes these conditions into the customer contract (→ GDPR General Data Protection Regulation).

A.2.5.9 keeps the disclosure of subcontractors current:

Sources

Frequently asked questions

How long do I have to wait after the announcement?

The standard sets no period. It requires the customer to have a real opportunity to object. A few weeks, written into the customer contract, are common. You activate the new subcontractor only once the period has passed without objection or an objection has been resolved.

What happens if a customer objects?

Then you look for a solution together: additional safeguards, an exception for this customer, a different subcontractor. Many contracts give the customer a special termination right if no agreement can be reached. Record every objection and the decision taken on it.

What applies if a subcontractor fails suddenly?

The customer's authorization remains a precondition even then. Settle in the contract in advance how such emergencies are handled, for example with a shortened period or a pre-approved replacement service. This way you never have to choose between keeping operations running and keeping the contract.

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.