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

A.2.2.6 Customer obligations

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

An insurer is preparing for a review of how it manages its service providers and asks its claims-handling provider for documents: security measures, subcontractors, the result of the last audit, evidence of deletions. Three weeks later, a glossy brochure from marketing arrives. The insurer cannot show its auditors that it has its provider under control. A.2.2.6 requires you to give the customer the information they need to demonstrate that they meet their own obligations.

The controller remains accountable for the processing, even when it takes place at your end. Without your information, they face their supervisory authority, their auditors and their own customers empty-handed.

What does the standard require?

A.2.2.6 follows on from the customer agreement. The agreement settles the support, and this control is about the information the customer needs for their evidence.

  • Supply suitable information. The customer gets from you what they need to show that they meet their own obligations. What is suitable depends on the processing and on the customer’s duties.
  • Audits as an example. The implementation guidance explicitly mentions whether you allow audits and take part in them. This means audits by the customer or by an auditor the customer has appointed or agreed to.
  • An open list. Beyond audits, the standard sets no closed list. Which information is needed follows from the obligations the customer has to demonstrate.

In practice

Create one entry point for requests. Decide through which channel customers request evidence, who accepts the request and within what time it is answered. A dedicated address or portal keeps requests from getting stuck in sales.

Define what the information covers. Decide which details customers receive as standard and which only on request under confidentiality, such as detailed audit reports or penetration test results.

Make audits plannable. Set out in the contract how an audit runs: advance notice, scope, confidentiality, on-site or remote, handling of costs. If many customers want to audit, joint audits by several customers or a recognized independent audit report that anticipates many questions will help.

Admit the customer’s auditors. The standard includes auditors appointed or accepted by the customer. Decide under which conditions you receive them, for example with a confidentiality agreement and without competitors acting as auditors.

Keep the information current. Evidence that is a year old helps the customer little. Link the evidence package to your change processes: when a subcontractor is added, a storage location changes or a certificate expires, the package is updated in the same step. Customers who have already received documents are told about significant changes.

Record what went out. For each request, document which information the customer received and when. This list shows you which documents are in demand and proves in the audit that the control is lived.

Typical audit evidence

For A.2.2.6, auditors typically expect:

  • Evidence package for customers with version, table of contents and date of the last update (→ Document Control Register)
  • Procedure for customer requests with responsibilities and response times
  • Contract clauses on information rights and audits
  • Records of customer audits carried out, with findings and actions (→ CAPA Register)
  • List of answered requests with date and content of the reply

KPI

% of customer obligations documented and tracked to completion

This covers the cases in which the customer needs information or cooperation for their obligations: requests for evidence, audits, questionnaires. Each case is recorded and followed until it has been answered in full. The target is 100%. Open cases past the agreed deadline belong in the management review.

Supporting KPIs:

  • Average response time to requests for evidence
  • Number of customer audits per year with open findings
  • Age of the evidence package (days since the last review)

Article 28(3)(h) GDPR obliges the processor to make available to the controller all information necessary to demonstrate compliance with the obligations in Article 28, and to allow for and contribute to audits, including inspections, by the controller or an auditor it mandates. Behind this stands the controller’s accountability under Articles 5(2) and 24. Under Article 28(1), the controller may only use processors that provide sufficient guarantees. Article 28(5) allows approved codes of conduct and certifications to serve as a factor for these guarantees (→ GDPR General Data Protection Regulation).

A.2.2.6 makes your implementation visible to the customer:

Sources

Frequently asked questions

Does a certificate replace my customers' right to audit?

Not automatically. A certificate to ISO 27001 or ISO 27701 or an independent audit report can answer many questions and make customer audits less frequent. The customer's right to audit or to appoint an auditor still stands wherever it has been agreed or is provided for by law.

May I set the conditions for customer audits?

Yes, within reason. Rules on advance notice, scope, confidentiality, duration and costs are common. The conditions must not make an audit impossible in practice, for example through disproportionate fees or cut-off periods.

Which information do customers ask for most often?

Typical requests cover the description of technical and organizational measures, the list of subcontractors with countries, certificates and audit reports, storage locations and deletion periods, and incident reports. Whoever keeps these documents current can answer most requests within a few days.

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.