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

A.2.2.2 Customer agreement

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

On a Friday evening, a payroll software provider notices that an export folder with salary data was publicly reachable. The contract with the affected customer only says the provider will “support to an appropriate extent”. When the customer is told, with which details and through which channel, is written nowhere. The customer hears about it on Tuesday and now has to decide under pressure whether to notify the supervisory authority and its employees, without knowing the facts. A.2.2.2 requires the contract with the customer to state how you support them with their own privacy obligations, matched to the nature of the processing and to what you know about it.

As a processor, you see things your customer cannot see: your systems, your security measures, your incidents. Many of the customer’s duties cannot be met without your help. The contract is where this dependency is put in order.

What does the standard require?

A.2.2.2 opens the conditions for collection and processing in the annex for PII processors. The control applies wherever it is relevant to the contractual relationship in question.

  • Put the support in the contract. The processing contract describes your part in the customer’s obligations. Two factors set its limits: the nature of the processing and the information actually available to you.
  • Typical content. The implementation guidance gives an open list of topics: privacy by design and by default, security of processing, reporting breaches to the supervisory authority, informing customers and data subjects about such breaches, privacy impact assessments, and your help if the customer has to consult an authority in advance.
  • Mind the customer’s role. Which points fit depends on whether your customer is a controller or a processor in its own right.
  • Mandatory details in some jurisdictions. Some jurisdictions require the contract to name the subject matter, duration, nature and purpose of the processing as well as the types of data and the groups of data subjects. The EU is one of them.

In practice

Maintain your own contract template. Create a template for processing on behalf of customers that covers every point of the standard, and map each clause to the point it meets. Every revision then shows at once whether a gap opens up.

Describe the processing per service. Subject matter, duration, nature and purpose, data types and groups of data subjects belong in an annex per service. A provider with three products needs three descriptions. One generic wording for everything convinces neither the customer nor an auditor.

Plan breach notifications to the customer. Decide internally who assesses a possible breach, who informs the customer and which details go into the first message. Keep your deadline short enough to leave the customer time for their own notification. The procedure belongs in your incident handling.

Keep documents ready for impact assessments. In a data protection impact assessment, customers ask the same questions again and again: a description of the processing, technical and organizational measures, subcontractors, storage locations. A ready package saves time on both sides and makes the promise in the contract deliverable.

Check customer templates against a checklist. When a customer presents their own contract template, check it against the same list. Frequent problems are unrealistic reporting deadlines, unlimited on-site inspections and duties that refer to systems you do not even operate.

Typical audit evidence

For A.2.2.2, auditors typically expect:

  • Contract template for processing on behalf of customers with a mapping of clauses to the topics of the standard and the date of the last review (→ Document Control Register)
  • Signed contracts per customer with an annex describing subject matter, duration, nature, purpose, data types and data subjects
  • Procedure for informing customers about personal data breaches (→ Incident Response Runbooks)
  • Incident entries showing when the customer was informed (→ Incident Register)
  • Standard documents for impact assessments and records of handing them to customers

KPI

% of processor agreements with complete data handling clauses

Complete means: the contract contains the description of the processing and settles every relevant support service with content, deadline and channel. The target is 100%. Older contracts that predate your own template often pull the rate down noticeably. They can be brought up to date at the next renewal.

Supporting KPIs:

  • Share of customer notifications about incidents within the contractually promised deadline
  • Average time to deliver the documents for a data protection impact assessment
  • Number of customer templates deviating from your own checklist per quarter

Article 28(3) GDPR requires a contract that names what is processed and for how long, how and why it is processed, which kinds of personal data are involved and whose data it is. Under Article 28(3)(f), the processor assists the controller with the obligations in Articles 32 to 36. The yardstick is the nature of the processing and what the processor knows. This covers security of processing, breach notification, the data protection impact assessment and prior consultation. Article 33(2) obliges you to inform the controller without undue delay once you become aware of a breach. Article 28(9) allows the contract to be in electronic form. For the content of the contract, the European Commission has provided standard contractual clauses under Article 28(7) (→ GDPR General Data Protection Regulation).

A.2.2.2 forms the contractual frame for many other controls in Table A.2:

Sources

Frequently asked questions

Do I have to sign every contract draft my customers send?

No. Many customers send their own templates, and these often do not fit your service. Check each template against your checklist of support services and negotiate deviations before signing. Whatever you cannot deliver has no place in the contract.

May I charge for supporting a data protection impact assessment?

The standard says nothing about fees. A common approach is a fixed package of standard documents included in the price, with extra effort billed at agreed rates. What matters is that the rule is in the contract beforehand, so that support never stalls over invoicing.

What changes if my customer is itself a processor?

Then you are a subcontractor in a chain. Your support goes to your customer, who passes it on to the controller. The contract content stays similar, yet your deadlines have to be short enough to leave time at the end of the chain.

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.