An IT service provider looks after some forty customers: hosting, backups, a ticket system, remote maintenance. After a complaint, a supervisory authority asks for the record of processing activities. All that exists is the record for the provider’s own employees and customer contacts. What the provider does with which customer’s data, to which countries data flows and which measures protect it is summarized nowhere. A.2.2.7 requires you to determine and keep current the records that prove you meet your contractual obligations when processing for customers.
Records are the processor’s memory. They show what you do for whom, and they are the basis of every answer to customers, auditors and authorities.
What does the standard require?
A.2.2.7 is the counterpart of A.1.2.9 for controllers. The yardstick is the set of obligations in your customer contracts.
- Determine the records. You decide which records you need to prove that you meet your contractual obligations.
- Maintain the records. The records you have determined are kept and kept current.
- Content jurisdictions can require. The implementation guidance names three items some jurisdictions prescribe: the kinds of processing you perform per customer, any data flows to third countries or to international organizations, and a broad overview of the protective measures, technical and organizational.
In practice
Two roles, two records. Keep the record of your own processing as a controller apart from the record of processing on behalf of customers. The mandatory content differs, and the separation shows customers and authorities at a glance in which role you act.
Structure by customer. For each customer, record: name and contact details, their representative and data protection officer where applicable, the categories of processing, subcontractors used, transfers to third countries with their safeguards, and a reference to the description of security measures.
Maintain the description of measures once. A general description of technical and organizational measures is usually enough for all customers of a service. Refer to it in the record. It then stays equally current everywhere, and nobody has to reconcile copies.
Include further evidence. Beyond the record of processing, the records your contracts demand belong here too: documented instructions, incident notifications, deletion confirmations, results of customer audits, announcements of new subcontractors.
Set triggers for changes. A new customer, a new service, a new subcontractor or a new destination country triggers an update. Anchor this in the contract and change processes, or the record goes stale between two annual reviews.
Protect and retain the records. Decide who may change the record, how changes stay traceable and how long evidence is kept after a contract ends. You often need evidence precisely when a customer left long ago and questions come up later.
Typical audit evidence
For A.2.2.7, auditors typically expect:
- Record of processing on behalf of customers with the categories per customer and the date of the last update
- General description of security measures referred to by the record
- List of transfers to third countries with destination and safeguard
- Further records required by contract, such as deletion confirmations (→ Deletion Evidence Log)
- Rules on retaining the records themselves (→ Records Retention Schedule)
KPI
% of processor processing activities with complete records
Complete means: for every processing activity on behalf of customers, customer, categories, subcontractors, transfers and security measures are recorded, and the evidence required by contract exists. The target is 100%. A useful check is a comparison with the customer list from accounting: every customer whose data you process should appear in the record.
Supporting KPIs:
- Share of customers with processing that appear in the record
- Average time between a change and its entry in the record
- Number of discrepancies between the record and the list of subcontractors
Link to the GDPR
Article 30(2) GDPR requires the processor to keep a record of its own, containing the name and contact details of the processor and the controllers (point a), the categories of processing carried out for each controller (point b), transfers to third countries or international organizations (point c) and, where possible, a general description of the measures under Article 32(1) (point d). The record is kept in writing, electronic form included (paragraph 3), and made available to the supervisory authority on request (paragraph 4). The exemption for smaller organizations in paragraph 5 falls away, among other cases, when processing is more than occasional (→ GDPR General Data Protection Regulation).
Related controls
A.2.2.7 supplies the data for many other controls:
- A.1.2.9 Records related to processing PII: the controller record you keep for your own processing.
- A.2.2.6 Customer obligations: gives customers information that largely comes from these records.
- A.2.5.3 Countries and international organizations to which PII can be transferred: the country list that has to match the transfers in the record.
- A.2.5.4 Records of PII disclosures to third parties: a specific record of disclosures.
- A.5.33 Protection of Records: protects the records themselves against loss and falsification.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.2, A.2.2.7, and Annex B, B.2.2.7: Records related to processing PII
- Regulation (EU) 2016/679 (GDPR), Articles 30 and 32
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles