A software company in Leipzig uses a ticketing system from a US provider and has first-level support handled by a partner in India. Both were bought by the business units, and nobody ever reviewed the transfers. During a major customer’s due diligence, one of the first questions is: on what basis does our employees’ data go to India? Nobody in the company can answer it. A.1.5.2 requires the organization to identify, for every transfer of personal data to another jurisdiction, the basis that supports it and to document how the applicable requirements are met.
Transfers abroad are part of everyday life as soon as cloud services, group structures or outsourced services are involved. That is exactly why they often happen unnoticed, and the basis is only looked for once someone asks.
What does the standard require?
A.1.5.2 opens group A.1.5. The aim of that group is to know and record whether and when personal data leaves the organization’s hands, be it through sharing, through a transfer to third parties or to another jurisdiction, or through disclosure.
- Identify and document the basis. For transfers between jurisdictions, the organization records what it relies on in each case.
- Consider the law on both sides. Requirements can arise from the destination country or the receiving international organization, and also from the law of the country of origin.
- Evidence compliance. Documented compliance with these requirements forms the basis of the transfer.
- Know about regulatory review. Some legal systems require a supervisory authority to review transfer agreements. Organizations operating there need to know about such obligations.
- Within one jurisdiction. If a transfer stays within one jurisdiction, the same rules apply to sender and recipient.
In practice
Find the transfers. Go through the record of processing activities and the Supplier Register. Ask every service provider about storage location, support locations and subcontractors. Intra-group data flows and remote access belong on the list as well.
Choose the basis under the GDPR. For transfers from the EEA there is a fixed order. First, check whether the European Commission has adopted an adequacy decision for the destination country. If not, appropriate safeguards are needed: the Commission’s standard contractual clauses, binding corporate rules within a group, approved codes of conduct or certifications. Only when neither applies do the narrowly defined derogations for specific situations come into question, such as explicit consent.
Assess the destination country. With standard contractual clauses, it is common to check whether laws and the practice of authorities in the destination country allow them to be honoured. The result and any additional measures, such as encryption with keys under your own control, are documented.
Record regulatory requirements. In the Legal Compliance Register, note per country whether agreements have to be submitted to an authority, how long that takes and which further obligations apply. Outside the EU there are rules of their own too, for instance in Swiss data protection law (→ FADP Swiss Federal Act on Data Protection).
Keep it current. Adequacy decisions can change, and service providers move locations. An annual review and an ad hoc check for every new service provider have proven useful.
Typical audit evidence
For A.1.5.2, auditors typically expect:
- Register of transfers with destination country, recipient, data categories and chosen basis
- Signed standard contractual clauses or other safeguards with the related assessments of the destination country
- Approvals or review notes from authorities, where a legal system requires them
- Entries in the legal register on the transfer rules of the countries concerned (→ Legal Compliance Register)
- Service provider statements on processing locations and subcontractors (→ Supplier Register)
KPI
% of cross-border PII transfers with documented legal basis
Documented means: the basis is named, the related documents are available and, for standard contractual clauses, there is an assessment of the destination country. The target is 100%. The figure depends on how complete the register is: transfers nobody knows about are missing from the denominator.
Supporting KPIs:
- Share of service providers with known processing and support locations
- Number of transfers relying on derogations for specific situations
- Date of the last review of transfers
Link to the GDPR
The GDPR governs transfers to third countries and international organizations in Chapter V. Article 44 sets the general principle that the level of protection under the Regulation must not be undermined. Article 45 covers adequacy decisions, Article 46 appropriate safeguards such as the standard contractual clauses (Implementing Decision (EU) 2021/914) and Article 47 binding corporate rules. Individually negotiated contractual clauses need authorization by the supervisory authority under Article 46(3), which matches the regulatory review mentioned in the standard. Article 49 contains the derogations for specific situations. Article 30(1)(e) requires transfers in the record of processing, and Articles 13(1)(f) and 14(1)(f) in the information for data subjects (→ GDPR General Data Protection Regulation).
Annex D of the standard also maps A.1.5.2 to Article 15(2): where data are transferred to a third country, a person making an access request also learns which appropriate safeguards the transfer relies on.
Related controls
A.1.5.2 settles whether a transfer may happen, and the neighbouring controls cover where and what:
- A.1.5.3 Countries and international organizations to which PII can be transferred: names the possible destination countries.
- A.1.5.4 Records of transfer of PII: records the individual transfers.
- A.1.2.7 Contracts with PII processors: governs the contracts in which transfer clauses are embedded.
- A.2.5.2 Basis for PII transfer between jurisdictions: sets the requirement from the processor’s point of view.
- A.5.31 Legal, Statutory, Regulatory and Contractual Requirements: identifies the laws that apply to the transfer.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.5.2, and Annex B, B.1.5.2: Identify basis for PII transfer between jurisdictions
- Regulation (EU) 2016/679 (GDPR), Articles 13, 14, 15, 30 and 44 to 49
- Implementing Decision (EU) 2021/914 on standard contractual clauses for transfers to third countries
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles