What evidence do auditors commonly ask for on A.2.2.6 Customer obligations?

Documented information package provided to customers for their own compliance evidence; Contract terms on audit rights and how they are exercised; Records of audits allowed or contributions made; Evidence the package is kept current.

What is the most common gap auditors find on A.2.2.6?

Assurance offered as a certificate whose scope does not cover the service the customer bought

ISO/IEC 27701:2025 · Annex A Table A.2 PIMS controls for PII processors

`A.2.2.6` Customer obligations

The organization must supply the customer with the information it needs to show that it meets its own obligations. This may cover whether the organization permits, and takes part in, audits carried out by the customer or by an auditor the customer appoints or approves.

Source: ISO/IEC 27701:2025, A.2.2.6. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27701:2025 in the compliance library.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

Records of audits allowed or contributions made · Document repository
Evidence the package is kept current · Document repository

governing documentDocuments that govern the control

Documented information package provided to customers for their own compliance evidence · Document repository
Contract terms on audit rights and how they are exercised · Vendor register / contract repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Assurance offered as a certificate whose scope does not cover the service the customer bought
Audit rights granted contractually and refused in practice through commercial friction
Information package written once and stale on control changes
Customer left to assemble compliance evidence from marketing material

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

A.2.2.5 Infringing instruction · A.2.2.7 Records related to processing PII