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

A.2.5.8 Engagement of a subcontractor to process PII

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

A development team at a call centre service provider tests a new AI service for transcribing calls. The account is set up quickly with the company credit card, and the terms of use are accepted with a click. A few weeks later, all of the customers’ call recordings run through the service. There is no customer authorization, no processing agreement, and nobody knows whether the provider uses the recordings to train its models. A.2.5.8 requires you to use subcontractors for processing personal data only as the customer contract allows, with prior written authorization and a written contract that passes on the appropriate controls.

Every subcontractor lengthens the chain in which your customers’ data is processed. The obligations you have taken on towards your customers have to travel along that chain.

What does the standard require?

A.2.5.8 governs the conditions under which a subcontractor may work at all.

  • Only within the customer contract. Subcontractors are used solely in the way the contract with the customer permits.
  • Written authorization in advance. Before a subcontractor processes data, the customer’s written authorization is in place. It can take the form of clauses in the customer contract or of a separate agreement for the individual case.
  • Written contract with the subcontractor. There is a written contract with every subcontractor that governs the implementation of the appropriate controls from Table A.2.
  • Basis for the selection. Which controls fit follows from the risk assessment under clause 6.1.2 and from the scope of the processing the subcontractor takes on.
  • All controls count as relevant at first. If you do not require a control from the subcontractor, you justify the exclusion.
  • Consider every control. The contract can divide responsibilities in different ways. All controls are nevertheless considered and recorded in the documented information.

In practice

A gate before the first data flow. Make approval by the data protection officer a precondition before customer data goes to a new service. Anchor it where access is set up and contracts are signed: in procurement and in IT.

Check the authorization per customer. Look in the customer contracts to see whether general or specific authorization applies. With general authorization, A.2.5.9 applies, with announcement and the chance to object. With specific authorization, you obtain the consent of every customer concerned.

Check the subcontractor. A review comes before the contract: certificates, audit reports, technical and organizational measures, storage locations, their own subcontractors and their terms of use, especially on using the data for purposes of their own.

Pass the controls on by contract. The contract with the subcontractor takes up the controls of Table A.2: purpose limitation, the advertising ban, reporting unlawful instructions, information for evidence, records, support with data subject rights, temporary files, deletion and return, transmission, transfers, disclosures and their own subcontractors.

Justify exclusions. Justify every exclusion where you document applicability anyway, for example in a statement of applicability per subcontractor. “Not applicable” is no justification. Name the processing the subcontractor does not perform.

Typical audit evidence

For A.2.5.8, auditors typically expect:

KPI

% of subcontractor engagements with complete PII processing agreements

What counts are all subcontractors that process personal data from assignments. Complete means: customer authorization before the start, a written contract, a mapping of all Table A.2 controls and justified exclusions. The target is 100%.

Supporting KPIs:

  • Number of services without approval found when reconciling with invoices
  • Share of subcontractors reviewed before the contract was signed
  • Share of contracts checked against the Table A.2 controls in the last year

Article 28(2) GDPR prohibits engaging another processor without the controller’s prior specific or general written authorization. Under Article 28(4), the same data protection obligations are imposed on the other processor by contract, in particular sufficient guarantees of appropriate measures. If it fails to fulfil its obligations, the initial processor remains liable towards the controller. Article 28(3)(d) writes these conditions into the contract with the customer, and Article 28(9) allows electronic form (→ GDPR General Data Protection Regulation).

A.2.5.8 holds the obligations together along the chain:

Sources

Frequently asked questions

Is it enough if my subcontractor offers click-through standard terms?

Only if those terms contain the necessary content. Many cloud services offer their own processing agreement that is concluded electronically. Check it against the controls of Table A.2 and document which points it covers and where you have to renegotiate or compensate.

Do I really have to pass all Table A.2 controls on to the subcontractor?

The standard assumes that all of them are relevant. You may exclude individual controls, and you have to justify each exclusion. A justification names the specific processing the subcontractor does not perform, such as no transfers to third countries.

What is the difference between specific and general authorization?

With specific authorization, the customer approves each subcontractor individually. With general authorization, they allow the use in principle, and you inform them of every change so they can object. Which model applies is set out in the customer 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.