A provider of marketing automation software publishes a list of its subcontractors. It contains a single name: the hosting provider. In reality, the emails run through a delivery service, an error monitoring tool receives email addresses with every crash, and a translation service gets newsletter texts along with recipient data. A customer discovers the monitoring service during an audit of its own and asks what else it does not know. A.2.5.7 requires you to disclose to the customer every use of subcontractors for processing personal data before it begins.
The customer can only answer for data whose path they know. Every subcontractor is another place where data lies, and therefore another risk the customer has to be able to assess.
What does the standard require?
A.2.5.7 is the first of three controls on subcontractors. It governs what the customer learns.
- Disclosure before use. Every use of a subcontractor for processing personal data is communicated to the customer before the processing begins.
- Provisions in the contract. The customer contract contains provisions on the use of subcontractors.
- Content of the disclosure. You communicate the fact that subcontractors are used, their names, the countries and international organizations to which they can transfer data (see A.2.5.3), and how they are bound to meet or exceed your obligations (see A.2.5.8).
- Confidential disclosure where risk is high. If public disclosure would raise the security risk beyond an acceptable level, disclosure takes place under a confidentiality agreement or on request. In that case the customer learns that the details exist and how to obtain them.
- Countries always open. The list of countries does not fall under this exception. It is given to the customer in every case in a way that lets them inform the data subjects.
In practice
Capture every subcontractor. Go through the data flows of each service and ask for every external service whether it receives personal data from the assignment. Error monitoring, logging, support tools, AI services, email delivery and off-site backups are often overlooked.
Define the content of the list. Proven fields per entry: name and seat, service, data categories processed, place of processing, basis for transfers to third countries and a reference to the contractual obligation.
Choose the form of disclosure by risk. Assess once, with reasons, whether a public list actually creates a risk. Many providers publish their list because customers need it anyway. Where the assessment shows a risk, offer the list on request under confidentiality and say so in the contract.
Inform before use. Link the list to procurement and to the introduction of new services. A new subcontractor appears on the list before it receives its first data. For changes, A.2.5.9 applies as well.
Keep the list per service. If you offer several products, keep the list per product. A customer who uses only one product needs only the subcontractors used there.
Typical audit evidence
For A.2.5.7, auditors typically expect:
- List of subcontractors per service with names, service, data categories, location and obligation (→ Supplier Register)
- Separate country list that customers receive in every case
- Contract clauses on the use of subcontractors and the form of disclosure
- Reasoned risk assessment, if the list is only handed out confidentially
- Proof of information before new subcontractors are used (→ Supplier Security Policy)
KPI
% of subcontractors processing PII disclosed to the controller
What counts are all service providers that process personal data from assignments, identified from procurement, invoices and data flows. Disclosed means: they are on the list the customer received before they were used. The target is 100%.
Supporting KPIs:
- Number of subcontractors found in reviews that were missing from the list
- Share of new subcontractors that were on the list before their first data access
- Age of the list (days since the last review)
Link to the GDPR
Under Article 28(2) GDPR, a processor may engage another processor only with the controller’s prior specific or general written authorization. Article 28(4) requires the same data protection obligations to be imposed on the other processor and keeps the initial processor fully liable towards the controller. Article 28(3)(d) anchors these conditions in the contract. The customer also needs the details to inform data subjects about recipients and transfers to third countries under Article 13(1)(e) and (f) (→ GDPR General Data Protection Regulation).
Related controls
A.2.5.7 creates transparency about the processing chain:
- A.2.5.8 Engagement of a subcontractor to process PII: the conditions under which a subcontractor may be used.
- A.2.5.9 Change of subcontractor to process PII: announcing additions or replacements.
- A.2.5.3 Countries and international organizations to which PII can be transferred: the country list that always stays open.
- A.5.19 Information Security in Supplier Relationships: managing suppliers from the ISO 27001 perspective.
- A.5.21 Managing Information Security in the ICT Supply Chain: the risks along the chain of IT service providers.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.2, A.2.5.7, and Annex B, B.2.5.7: Disclosure of subcontractors used to process PII
- Regulation (EU) 2016/679 (GDPR), Articles 13 and 28
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles