1. What sub-processors are
When a cloud supplier processes personal data on your behalf, it may entrust part of the work to other parties: companies that run data centres, technical support providers, email services, monitoring or support tools. In the language of the GDPR (Regulation (EU) 2016/679) these parties are sub-processors: they process data on behalf of the supplier, which remains your main point of contact. Their significance must be verified case by case.
The critical point is that the chain can lengthen without your being informed. A seemingly simple service may depend on several suppliers in cascade, each with its own storage location and its own access. For this reason verification does not stop at the first level, but must follow the chain to where the data actually goes. Ask therefore who the parties involved are, not just how many there are.
2. Why the supply chain is a risk
Each sub-processor is an entry point for data and access. If one of them suffers an incident, responsibility towards you usually remains with the main supplier, but the real problem is understanding what happened and which data is involved. Without an up-to-date list, the response to a breach starts late and with incomplete information.
The NIS2 Directive (Directive (EU) 2022/2555, transposed in Italy by D.Lgs. 138/2024) makes supply chain security one of the matters to manage. For many organisations this means knowing their critical suppliers and, as far as possible, the suppliers of those suppliers. Check with an adviser whether and to what extent the rules apply to you. Each new link changes the perimeter of the data.
3. The steps of the verification
Verification should be carried out in order, because each step produces the document needed for the next. The final result is a dated list, with the linked contractual guarantees and an internal owner who keeps it up to date. If a step cannot be closed, note the gap and decide with the owner whether to accept the risk or look for an alternative. Each step has a result that must be archived.
- Request the list of sub-processors relating to your contract, with the service provided, data location and update date.
- Check that the list includes technical support, backups, log management and communications with customers.
- Ask what contractual guarantees the supplier imposes on its sub-processors regarding the processing of data.
- Ask whether prior notice is provided before new additions or replacements, and with what timeframes.
- Ask how transfers to third countries are managed and with what safeguards.
- Record the list in an internal document with the date of the check and the name of the person who received it.
- Repeat the check at every renewal and every time the supplier communicates changes.
4. What the contract should say
The contract, or its data processing annex, should govern the use of sub-processors. The elements to look for are general or specific authorisation, the right to be informed of changes and the possibility to object within a reasonable timeframe. Not all suppliers accept the same terms, but the clauses must be written down, not merely stated in a presentation.
Also check the consequences of refusal: what happens if you do not accept a new sub-processor? The contract should provide an exit route, otherwise the right to object remains theoretical. This point is often overlooked at the time of purchase, and it is precisely what is needed when the chain changes midway through the relationship. Repeat the check at every renewal and every time the supplier communicates changes, linking the review to the contract cycle.
5. Assessing the risk of each link
Not all sub-processors carry the same weight. A supplier that stores copies of personal data presents a different risk from a technical monitoring tool that does not see the content. The table helps classify the links of the chain by priority, so that questions focus where the potential damage is greatest. Use concrete criteria to assign the priorities, not intuition.
Use the priority to decide where to invest time. For high-priority levels ask for written documents and a description of the controls; for more marginal ones a formal response from the supplier may suffice, provided it relates to the service you actually use. For high-priority levels, verification must be complete before signing, and cannot be postponed to the first renewal.
| Type of sub-processor | Data it can see | Priority | What to ask in addition |
|---|---|---|---|
| Data centre management | All hosted data | High | Location, physical access and staff controls |
| Backup and copies | Full copy of the data | High | Location of the copies and declared restore times |
| Technical support | Data visible during the intervention | High | Limited access, logged and revoked at the end of the intervention |
| Logs and monitoring | Technical data that may include personal data | Medium | Content of the logs and retention period |
| Communication tools | Messages and contact details | Medium | Location of the data and retention rules |
6. Common mistakes
The first mistake is accepting a public web page as the official list. Pages can be generic, not referred to your contract, and not always up to date. The second is stopping at the first level: the main supplier may be reliable, but if it cannot tell you who works for it, the verification remains incomplete and surprises arrive later. An up-to-date list also serves to demonstrate due diligence.
The third is failing to keep track of the versions received. When a sub-processor changes, you need to know which list was valid at the time of an incident or a dispute. Archive every version with its date and sender, even if it appears superseded. Each version of the list should be linked to the contract and to the date it was received, so that the situation can be reconstructed at any time.
7. How to start
This week, identify the cloud supplier that processes the most personal or sensitive data for your company and ask it for the list of sub-processors relating to your contract. If it does not have one, ask in writing when it can provide it, and note the date of the request as evidence of your initiative. Also note who received the request and in what form, because the date of the request is part of the evidence.
When the list arrives, apply the table in section five and the steps in section three. Bring any open points to the data protection officer or an adviser, with the written answers in hand. The first goal is to have a dated and verified document, not a perfect chain. Every answer received should be archived together with its date, because you will need it at the next renewal.
Frequently Asked Questions
Is the cloud supplier responsible for its sub-processors?
In general the supplier remains your point of contact and is accountable to you under the contract and the law. This does not mean you can stop verifying. The concrete responsibility depends on the clauses signed and the specific case: have an adviser read the contract together with the data processing clauses, and do not assume that every link in the chain is covered.
Do I need to approve every new sub-processor?
It depends on the contract. Some suppliers provide for general authorisation with a duty of prior notice, others require specific authorisation for each new entry. The important point is having the right to be informed in advance and a clear route if you do not agree, otherwise the right to object is merely formal.
What happens if a sub-processor has an incident?
The main supplier must handle it in accordance with its contractual and legal obligations, and inform you of the relevant information within agreed timeframes. Under the GDPR, a personal data breach must be handled within the timeframes set for the data controller. Ask the supplier what procedure it follows, with which contacts and how it informs you, and include this information in your response plan.
Is a sub-processor outside Europe a problem?
Not automatically, but it must be assessed. If data is transferred to third countries, the GDPR requires appropriate safeguards, and the supplier must declare them. Check where the data is located, who accesses it and which safeguard applies. It is not enough to know where the sub-processor is based: you need to understand what actually happens to the data.
What should I do if a supplier does not want to answer?
A refused or generic answer is information in itself. Record the gap in writing, ask for a deadline and a reason, and assess with your manager whether the risk is acceptable. If it is not, consider alternatives or stricter clauses at renewal. Do not sign anything you cannot verify.