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

A.1.4.10 PII transmission controls

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

Every month, HR sends a spreadsheet with salaries, tax classes and bank details to the external payroll bureau. In December, the mail client suggests a similar-sounding contact while the address is being typed: a former contact who now works for a competitor. The email goes out, unencrypted and without a second check. The payroll bureau waits in vain, and the competitor has the salary list. A.1.4.10 requires the transmission of personal data over networks to be secured so that the data arrives intact and only at the intended recipient.

The control covers every transmission over a network, whether by email, file transfer, interface or sharing link. It looks at two dangers at once: interception on the way and arrival at the wrong destination.

What does the standard require?

The control describes an outcome and names the usual means of achieving it.

  • Scope. It covers personal data that travels over a data transmission network, for example to another organization.
  • Outcome. Appropriate measures make sure the data reaches its intended destination, undamaged and at the right recipient.
  • Access to transmission systems. Only authorized people can use the systems through which data is transmitted.
  • Defined procedures. Transmissions follow set procedures, which include keeping audit logs.

The standard leaves open which technical means are suitable in detail. The choice depends on the protection need of the data and on the risk of the transmission channel.

In practice

Record the transmission channels. Email, encrypted file transfer, interfaces to partners, sharing links from cloud storage, customer portals, electronic data interchange, messengers. Every channel through which personal data leaves or reaches the organization goes on the list.

Set channels by protection need. Decide which data may travel over which channel. For health data, salary lists or copies of identity documents, a secured portal, encrypted file transfer or end-to-end encrypted email are suitable. For everyday correspondence, reliably enforced transport encryption is usually enough.

Secure the recipient. Warnings for external addresses, a short send delay, disabled address suggestions for sensitive mailboxes and a four-eyes principle for bulk transmissions prevent misdirected sends. Interfaces only transmit to fixed, authenticated endpoints. For the first transmission to a new recipient, the address is confirmed through a second channel.

Restrict access to transmission systems. A personal account for every individual, strong authentication, regularly renewed keys and certificates. Anyone who leaves the team loses access on the same day.

Check integrity. For file transfers and interfaces, checksums or signatures that show the data arrived unchanged have proven useful. For important deliveries, such as those to the payroll bureau or the health insurer, an acknowledgement of receipt helps. If it does not come, someone follows up before the data is sent a second time.

Log. Transmission systems record who sent what to whom and when. The logs are kept according to the Records Retention Schedule and analysed when something looks unusual.

Typical audit evidence

For A.1.4.10, auditors typically expect:

  • Transmission rules with permitted channels per protection level (→ Information Transfer Policy)
  • Overview of transmission channels with the safeguards for each and the responsible people
  • Authorization lists for transmission systems with personal accounts
  • Transmission logs and their retention period (→ A.8.15 Logging)
  • Encryption requirements for the transmission channels (→ Cryptography Policy)

KPI

% of PII transmissions using encrypted and authorized transfer channels

Encrypted means: the channel meets the encryption requirements for the protection level of the data. Authorized means: the channel is approved in the overview and is used through personal accounts. The target is 100% of regular transmissions. For email, the figure can be approximated through mail server reports.

Supporting KPIs:

  • Number of misdirected sends containing personal data per quarter
  • Share of transmission systems without shared accounts
  • Share of interfaces with mutual authentication

A.1.4.10 applies the principle of integrity and confidentiality under Article 5(1)(f) GDPR to transport. Article 32(1)(a) names encryption as an example of an appropriate measure, and point (b) the confidentiality and integrity of systems. Article 32(2) explicitly requires the risks of unauthorized disclosure of transmitted data to be considered. A misdirected send meets the definition of a personal data breach under Article 4(12) and has to be assessed under Article 33, with Article 34 applying in addition where the risk to data subjects is high (→ GDPR General Data Protection Regulation).

A.1.4.10 protects the route, while other controls govern the basis and the record of disclosure:

Sources

Frequently asked questions

Is transport encryption enough for email?

For data with a low protection need it often is, provided it is reliably enforced. It only protects the path between servers, though, and does nothing if the address is wrong. For sensitive data, end-to-end encryption, a secured portal or encrypted file transfer are the better choice.

Is a misdirected email already a personal data breach?

If it contains personal data and reaches an unauthorized recipient, yes. You then assess the risk to the data subjects and decide whether the supervisory authority has to be notified. Cases without a notification duty are documented as well.

What belongs in the transmission logs?

At least sender, recipient, time, transmission channel and a description of the scope, such as file, data category or number of records. The logs themselves contain no copy of the content and follow a defined retention period.

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.