A sub-processor is another processor engaged by a vendor to carry out specific processing of personal data on the controller's behalf. Under GDPR Article 28(2) and 28(4), it needs the controller's authorisation and must be bound by the same data protection obligations.
What Sub-processor means
Article 28(2) requires the processor to have the controller's prior specific or general written authorisation before engaging another processor. Under general authorisation, the processor must inform the controller of intended additions or replacements so the controller can object. Article 28(4) requires the same data protection obligations to be imposed on the sub-processor, and the initial processor remains fully liable for its performance.
The EDPB's Opinion 22/2024 says controllers should have information on the identity of all processors and sub-processors in the chain, so they can meet their own obligations. Vendors usually publish a list with each sub-processor's name, purpose and location, and offer email notice of changes.
Sub-processor lists are also your fourth-party map. The same hosting, support and AI model providers appear across many vendors, which is where concentration risk becomes visible. Collect the lists across vendors and look for the same names. A model provider added to several vendors' lists at once is a change worth noticing.
What to check in vendor documents
- A current list with the name, purpose, location and data involved for each sub-processor.
- The notice period for changes and how you are told.
- Your right to object, and what happens if you do, such as termination without penalty.
- Flow-down of the DPA obligations to each sub-processor.
- Consistency with the SOC 2 subservice organisations and the vendor's AI model providers.
In ProcureCortex
A sub-processor list that is missing, out of date or inconsistent with the vendor's other documents can be raised as a finding that keeps the excerpt and page.
How an assessment worksRelated terms
- GDPR Article 28GDPR Article 28 is the provision of Regulation (EU) 2016/679 that governs how a controller uses a processor: the processor must give sufficient guarantees, act only on documented instructions and be bound by a contract with set minimum terms.
- Data processing agreement (DPA)A data processing agreement (DPA) is the contract between a controller and a processor that sets the terms GDPR Article 28(3) requires for processing personal data on the controller's behalf, including instructions, security, sub-processors, deletion and audits.
- Fourth-party riskFourth-party risk is the risk that comes from the providers your vendors rely on to deliver their service to you, such as cloud hosting, data centres, payment processors or AI model providers, with whom you usually have no contract.
- Model provider sub-processorA model provider sub-processor is a company whose AI model a vendor uses to deliver its service and which processes your personal data in doing so. Under GDPR it is a sub-processor that needs authorisation and flow-down terms.
- Carve-out vs inclusive methodThe carve-out and inclusive methods are the two ways a SOC report can treat a vendor's subservice organisations. The carve-out method excludes their controls from the examination; the inclusive method describes and tests them within the report.
Sources
- Regulation (EU) 2016/679 (GDPR)eur-lex.europa.eu/eli/reg/2016/679/oj
- EDPB, Opinion 22/2024 on obligations when relying on processors and sub-processorswww.edpb.europa.eu/our-work-tools/our-documents/opinion-board-art-64/opinion-222024-certain-obligations-following_en
Summarised for practitioners, not legal advice. Check the source text for your own obligations.