Zum Hauptinhalt springen
ISO/IEC 27701:2025 · Annex A, Table A.2 · Control for PII processors

A.2.4.4 PII transmission controls

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27701:2025GDPR

A payroll bureau sends monthly payslips to its clients as email attachments. A clerk types “Miller” into the address field, autocomplete suggests the wrong Miller, and the salary list of a twelve-person craft business lands at a stranger’s company. The attachment was unencrypted, the sending was logged nowhere, and it takes hours to reconstruct who sent which file to whom and when. A.2.4.4 requires you to protect personal data sent over a network so that it reaches the intended recipient and does not fall into the wrong hands along the way.

Transmission is the moment data leaves your protected environment. Most mistakes here are entirely ordinary: wrong addresses, open sharing links and interfaces that anyone on the team can reach.

What does the standard require?

A.2.4.4 matches A.1.4.10 for controllers. For processors, coordination with the customer comes on top.

  • Secure the transmission. Personal data travelling over a data network is subject to measures that make sure it reaches its intended destination.
  • Limit access to transmission systems. Typically, only authorized people may work with the systems through which data is sent.
  • Defined procedures with an audit trail. Transmissions follow set procedures. This includes keeping log data, so that it can be traced that the data arrived intact at the right recipient.
  • Contract with the customer. Requirements for transmission can be written into the contract between processor and customer.
  • Ask when the contract is silent. Where no such requirements exist, it can be wise to seek the customer’s advice before sending.

In practice

Encrypt every route. Use current TLS for interfaces and web access, and secure protocols such as SFTP for file transfers. For emails with sensitive attachments, end-to-end encryption or a portal from which the recipient collects the file are suitable.

Identify recipients reliably. Mutual authentication for interfaces, stored and verified recipient addresses, no free-text entry for regular deliveries: this is how data reaches the right destination. For large exports, a second pair of eyes on recipient and content helps.

Restrict access to the transmission systems. Only those whose job it is may set up interfaces, change recipients or trigger bulk exports. Review these permissions regularly.

Log transmissions. Record who transmitted which data to which recipient and when, and whether the transmission succeeded. Decide how long these logs are kept, and make them available to the customer for audits.

Tame sharing links. Links for sharing files get an expiry time, access protection and a restriction to named recipients. Open links without expiry are among the most frequent causes of unintended disclosure.

Include subcontractors. Transmissions to and from subcontractors are part of this too. Agree in your contract with them which routes and safeguards apply, and check when connecting them that these are actually kept.

Typical audit evidence

For A.2.4.4, auditors typically expect:

  • List of transmission routes per service with encryption, authentication and logging
  • Rules for transmitting personal data (→ Information Transfer Policy)
  • Encryption requirements and the methods used (→ Cryptography Policy)
  • Overview of permissions for transmission systems with review date
  • Logs of transmissions and rules on keeping them
  • Documented queries to the customer in cases without a contractual rule

KPI

% of PII transmissions using approved encryption and transfer controls

In practice, you measure by the listed transmission routes: how many of them use approved encryption, restricted access and logging? The target is 100%. A route that misses one of these requirements is shut down or given a time-limited, justified exception.

Supporting KPIs:

  • Number of misdirected transmissions of personal data per quarter
  • Share of sharing links with an expiry time
  • Share of transmission systems whose permissions were reviewed in the last six months

Article 5(1)(f) GDPR requires processing that ensures appropriate security, including protection against unauthorized processing. Article 32(1)(a) names encryption as an example of suitable measures, and Article 32(2) explicitly highlights the risks arising for transmitted data, such as unauthorized disclosure. Under Article 28(3)(c), the processor takes these measures. If something still goes wrong, you report the breach to your customer without undue delay under Article 33(2) (→ GDPR General Data Protection Regulation).

A.2.4.4 protects data on the move:

Sources

Frequently asked questions

Is transport encryption enough?

It is the foundation and covers only part of the control. The standard aims at data reaching the right recipient. That also takes checking the recipient, restricted access to the transmission systems and logs that prove what went where.

Is a misdirected email a data breach?

If personal data goes to the wrong recipient, this is usually a personal data breach. As a processor, you report it to your customer without undue delay. The customer decides whether the supervisory authority and the data subjects have to be informed.

What do I do if the contract says nothing about transmission?

Ask the customer before sending which route and which safeguards they expect, and record their answer. The standard names exactly this step for cases without a contractual rule. You then add the rule to the contract for the future.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.