ISO/IEC 27701:2025·Annex A A.2.2.3·high·Component: Conditions for collection and processing (processors)

What this control requires

Ensure PII processed on behalf of customer are only for purposes expressed in customer's instructions. Implementation: Process design to accept documented instructions; verifiability for customer. Justification: Prevents unauthorized use of customer PII.
— ISO/IEC 27701:2025, Annex A A.2.2.3

In plain English

Ensure PII processed on behalf of customer are only for purposes expressed in customer's instructions. In practice, this means you can prove you implement organization's purposes-level controls on a defined cadence.

Why it matters

ISO 27701 is the international way to evidence the GDPR principle of accountability: certified PIMS controls translate directly into the records, contracts and rights-handling that supervisory authorities want, and into the privacy-engineering evidence SOC 2 + Privacy auditors and enterprise procurement teams ask for.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

PIMS auditors expect ISO 27001 to be implemented first and then the 27701-additional controls tested. For PII controllers they look at lawful-basis and rights-handling evidence; for PII processors they look at customer-instructions, sub-processor controls and return/transfer/disposal evidence.

Within Conditions for collection and processing (processors), the assessor will trace your implementation back to the catalogue reference (Annex A A.2.2.3) and look for objective evidence on the latest two assessment cycles.

How to implement

  1. Write a short policy stating intent, scope and named owner.
  2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
  3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
  4. Review on a documented cadence and capture the review in the risk register or compliance tracker.

Operational checklist

  • Implement. Document the trigger, the owner and the cadence.
  • Document. Document the trigger, the owner and the cadence.
  • Ensure. Document the trigger, the owner and the cadence.
  • Scope: organization's purposes.

Evidence to collect

  • Policy Document. A signed and version-controlled policy / standard / procedure document.
  • Vendor Risk Management. vendor_risk_management evidence

Signed policies, procedures, and registers document the safeguard. Processor due diligence, contracts, and disclosure registers evidence third-party controls. Focus: Organization's purposes.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

Related controls in ISO/IEC 27701:2025

References

Topics: governance riskdata protectionvendor riskprivacy managementvendor management