An insurance broker moves to a cloud CRM. Sales orders it by credit card and accepts the terms of use, including a template data processing agreement. A year later, the provider moves support to a subcontractor outside the EU. The broker finds out from the press: the contract has no list of subcontractors, no right to object and no rule for returning the data. A.1.2.7 requires a written contract with every PII processor that makes the appropriate controls from Table A.2 of the standard binding.
Table A.2 holds the controls for PII processors. A.1.2.7 builds the bridge: through the contract, the controller makes sure its service provider actually implements those controls.
What does the standard require?
The control applies to every service provider that processes personal data on the organization’s behalf.
- Written contract. There is a written contract with every processor in use.
- Cover the Table A.2 controls. The contract commits the provider to the appropriate controls. Which ones these are follows from the information security risk assessment (clause 6.1.2) and from the scope of the processing at the provider.
- Everything relevant by default. The starting point is that all Table A.2 controls apply. If the organization waives one, it justifies the exclusion where it decides on applicability in general (clause 6.1.3).
- Free allocation, full consideration. The parties may divide responsibilities between themselves differently. Every control, however, has to be considered and reflected in the documented information.
In practice
Find every processor. The list includes cloud services, data centres, IT support with remote access, payroll, call centres, document shredding and marketing agencies with access to customer data. A comparison with the accounts payable list finds the services that departments ordered without procurement.
Classify the role properly. Not every service provider is a processor. Professionals bound by secrecy, such as tax advisors, usually count as controllers in their own right, and partners with shared purposes fall under A.1.2.8. The classification decides which contract fits in the first place.
Start from a proven template. The European Commission has published standard contractual clauses for the relationship between controllers and processors (Implementing Decision (EU) 2021/915). They cover the mandatory GDPR content and can be extended with the Table A.2 points, such as temporary files or disclosure to authorities.
Justify exclusions in concrete terms. A note saying “not applicable” is no justification. Write which processing the provider does not perform: “No transfers to third countries, hosting in Frankfurt only” explains why the transfer controls drop out.
Maintain contracts and check effectiveness. Record contract version, term and review date in the supplier register. Before renewals and after announced changes, the contract is read against Table A.2 again. Audit reports and certificates from the provider show that the agreed controls are actually practised.
Typical audit evidence
For A.1.2.7, auditors typically expect:
- List of processors with contract version, term and review date (→ Supplier Register)
- Concluded data processing agreements, including in electronic form
- Mapping table per contract covering all Table A.2 controls with justified exclusions (→ Statement of Applicability (SoA))
- Supplier assessment linked to the risk assessment (→ Supplier Security Policy)
- Evidence of checks such as audit reports, certificates or questionnaire responses
KPI
% of PII processors with compliant and up-to-date data processing agreements
Compliant means: the mandatory content under Article 28(3) GDPR is included and checked against Table A.2. Up to date means: the contract fits today’s processing and today’s subcontractors. The target is 100%.
Supporting KPIs:
- Share of contracts with a complete mapping table to Table A.2
- Number of services without a contract found when comparing with accounting records
- Share of processors with evidence of a check from the last twelve months
Link to the GDPR
A.1.2.7 implements Article 28 GDPR. Under paragraph 1, the controller may only use providers that offer sufficient guarantees of appropriate safeguards. Paragraph 3 requires a contract or other legal act and lists the mandatory content, from being bound by instructions and helping with data subject rights to deletion or return and audit rights. Paragraphs 2 and 4 cover subcontractors, and paragraph 9 allows electronic form. Under paragraph 5, approved codes of conduct and certifications can serve as evidence of sufficient guarantees. The accountability principle in Article 5(2) requires all of this to be demonstrable (→ GDPR General Data Protection Regulation).
Related controls
A.1.2.7 is the link between Table A.1 and Table A.2:
- A.2.2.2 Customer agreement: the counterpart at the processor, which commits to its duties in the contract.
- A.2.2.5 Infringing instruction: obliges the provider to report unlawful instructions.
- A.2.4.3 Return, transfer or disposal of PII: governs the end of the contract.
- A.2.5.8 Engagement of a subcontractor to process PII: ties further providers to the controller’s approval.
- A.1.2.8 Joint PII controller: applies when the partner helps decide purposes and means.
- A.5.19 Information Security in Supplier Relationships and A.5.20 Addressing Information Security Within Supplier Agreements: provide the general framework for supplier contracts.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.2.7, and Annex B, B.1.2.7: Contracts with PII processors
- Regulation (EU) 2016/679 (GDPR), Articles 5 and 28
- Implementing Decision (EU) 2021/915: standard contractual clauses between controllers and processors
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles