# ISO/IEC 27701 A.2.4.3 — Return/transfer/disposal

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_iso27701_a243_e5c5ea4d4d-isoiec-27701-a243-returntransferdisposal
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [ISO/IEC 27701 (Privacy Information Management)](https://support.icompaas.com/support/solutions/c_gen_iso27701) › [Privacy by design / default (processors)](https://support.icompaas.com/support/solutions/folders/f_gen_cgeniso27701_privacybydesigndefaultprocessors)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

ISO/IEC 27701 · Control A.2.4.3 · Priority: high · Component: Privacy by design / default (processors)

### What this control covers

Be able to return/transfer/dispose of PII securely and make policy available to customer. Implementation: Implement return/disposal procedures; include in contract and publish policy. Justification: Ensures data portability and secure end-of-contract handling.

### Why it matters

Encryption and key management make data unreadable to attackers and unintelligible under data-breach safe-harbour clauses — a meaningful regulatory benefit.

### How to implement

#### AWS

Default to **SSE-KMS** with customer-managed keys for S3/EBS/RDS/Secrets Manager. Use **S3 Bucket Keys** and **S3 Block Public Access** at the account level, and turn on **S3 Object Lock** on backup buckets for ransomware resilience.

#### Azure

Store secrets in **Key Vault** (HSM-backed where required) with soft-delete + purge protection; use **customer-managed keys** for Storage, SQL, and Azure Disk Encryption. Tag PII data via **Microsoft Purview**.

#### GCP

Use **Cloud KMS** with customer-managed encryption keys (CMEK) for BigQuery, GCS, and Compute. **Sensitive Data Protection** (DLP API) inspects/de-identifies PII at scale.

#### Google Workspace

Enable **client-side encryption** for Drive/Docs and turn on **Drive Labels + DLP** rules to prevent external sharing of regulated data classes.

#### On-premises

Operate a **Records of Processing Activity (RoPA)** and a **data-subject-request (DSR) workflow** with named owners, SLA per regulation (GDPR 30 days, DPDP 30 days, CCPA 45 days). iCompaas users can track requests + evidence inside the Privacy module.

### Evidence to collect

-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.
-   `vendor_risk_management` — See the iCompaas Evidence library for the canonical source for this evidence type.

Signed policies, procedures, and registers document the safeguard. Processor due diligence, contracts, and disclosure registers evidence third-party controls. Focus: Return/transfer/disposal.

### Quick checklist

-   Implement — Return / Transfer
-   Ensure — Return / Transfer
-   Publish — Return / Transfer

### Related articles on this site

-   [164.308(b)(3) - Implementation specifications: Written contract or other arrangement](https://support.icompaas.com/support/solutions/articles/62000230579-164-308-b-3-implementation-specifications-written-contract-or-other-arrangement)
-   [Ensure to Implement Identity and Access Management (IAM)](https://support.icompaas.com/support/solutions/articles/62000234479-ensure-to-implement-identity-and-access-management-iam-)
-   [Ensure Secure Password Policy Implementation](https://support.icompaas.com/support/solutions/articles/62000234498-ensure-secure-password-policy-implementation)
-   [Implement and Enforce a Global Dependency Usage Policy](https://support.icompaas.com/support/solutions/articles/62000234956-implement-and-enforce-a-global-dependency-usage-policy)