# ISO/IEC 27701 A.2.5.3 — Countries to which PII transferred

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_iso27701_a253_c8e7e01b9f-isoiec-27701-a253-countries-to-which-pii-transferred
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [ISO/IEC 27701 (Privacy Information Management)](https://support.icompaas.com/support/solutions/c_gen_iso27701) › [PII sharing, transfer & disclosure (processors)](https://support.icompaas.com/support/solutions/folders/f_gen_cgeniso27701_piisharingtransferdisclosureprocessors)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

ISO/IEC 27701 · Control A.2.5.3 · Priority: high · Component: PII sharing, transfer & disclosure (processors)

### What this control covers

Specify and document countries / organizations to which PII can be transferred. Implementation: Maintain list and provide to customers; include subcontractor country details. Justification: Transparency to customers and principals.

### 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: Countries to which PII transferred.

### Quick checklist

-   Maintain — Countries To Which Pii Transferred
-   Implement — Countries To Which Pii Transferred
-   Document — Countries To Which Pii Transferred

### Related articles on this site

-   [Maintain current contact details](https://support.icompaas.com/support/solutions/articles/62000081044-maintain-current-contact-details)
-   [NIST 800-171 3.1.9 Provide privacy and security notices consistent with applicable CUI rules.](https://support.icompaas.com/support/solutions/articles/62000229233-nist-800-171-3-1-9-provide-privacy-and-security-notices-consistent-with-applicable-cui-rules-)
-   [CMMC 2.0 AC.2.005 Provide privacy and security notices consistent with applicable CUI rules.](https://support.icompaas.com/support/solutions/articles/62000229394-cmmc-2-0-ac-2-005-provide-privacy-and-security-notices-consistent-with-applicable-cui-rules-)
-   [1.1 Maintain Current Contact Details (Manual)](https://support.icompaas.com/support/solutions/articles/62000233102-1-1-maintain-current-contact-details-manual-)