# ISO/IEC 27701:2025 A.2.2.3 — Organization's purposes

- Source: https://support.icompaas.com/compliance/iso-27701-2025/a-2-2-3-organization-s-purposes
- Section: [Compliance](https://support.icompaas.com/compliance) › [ISO/IEC 27701:2025 PIMS Controls](https://support.icompaas.com/compliance/iso-27701-2025) › Conditions for collection and processing (processors)
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**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.

-   [**India DPDP Act 2023 DP-001** — Data Processing Agreements (DPA) - Full Compliance](https://support.icompaas.com/compliance/india-dpdp-act-2023/dp-001-data-processing-agreements-dpa-full-compliance)
-   [**SOC 2 (2017 TSC) P6.1** — Third-Party Disclosure with Data Subject Consent](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p6-1-third-party-disclosure-with-data-subject-consent)

## Related controls in ISO/IEC 27701:2025

-   [**Annex A A.2.2.2** — Customer agreement](https://support.icompaas.com/compliance/iso-27701-2025/a-2-2-2-customer-agreement)
-   [**Annex A A.2.2.4** — Marketing & advertising use](https://support.icompaas.com/compliance/iso-27701-2025/a-2-2-4-marketing-advertising-use)
-   [**Annex A A.2.2.5** — Infringing instruction](https://support.icompaas.com/compliance/iso-27701-2025/a-2-2-5-infringing-instruction)
-   [**Annex A A.2.2.6** — Customer obligations](https://support.icompaas.com/compliance/iso-27701-2025/a-2-2-6-customer-obligations)
-   [**Annex A A.2.2.7** — Records related to processing PII](https://support.icompaas.com/compliance/iso-27701-2025/a-2-2-7-records-related-to-processing-pii)
-   [**Annex A A.1.5.2** — Basis for transfer](https://support.icompaas.com/compliance/iso-27701-2025/a-1-5-2-basis-for-transfer)

## References

-   [ISO/IEC JTC 1/SC 27 — ISO/IEC 27701:2025](https://www.iso.org/standard/85819.html)
-   Catalogue identifier: `Annex A A.2.2.3`

Topics: governance riskdata protectionvendor riskprivacy managementvendor management