ISO 27001 Control A.5.14: Information Transfer
Information is only useful when it moves. Contracts go to customers, logs go to suppliers, payroll goes to the bank, and a founder reads out a figure over a video call. Every one of those movements is a moment when information leaves the place where you control it. A.5.14 is the control that asks you to decide, in advance, how that should happen. It is the 14th of 37 organizational controls in our walk through Annex A.
The control is broader than most people expect. It is not only about encrypted email. It covers file sharing links, courier packages, USB drives handed across a desk and sensitive conversations in a corridor. The practical question is simple: for each way information travels, do people know what is allowed, and can you show it?
What the control requires
Annex A control 5.14 of ISO 27001:2022 states that information transfer rules, procedures, or agreements shall be in place for all types of transfer facilities within the organization and between the organization and other parties.
The key elements:
- Rules, procedures or agreements - you can meet the control with internal rules for staff, procedures for specific channels, or agreements with outside parties, and often you need all three
- All types of transfer facilities - electronic, physical and verbal; email, messaging, file transfer, post, couriers and conversation
- Within the organization and between the organization and other parties - internal movement between teams and sites counts, as does anything sent to customers, suppliers and partners
A.5.14 is a preventive control in ISO/IEC 27002:2022. It reduces the chance of information being intercepted, misdirected, altered or lost in transit. Annex A states the control; ISO 27002 gives guidance, including topics such as controls against interception and malware, attachment handling, retention, and the responsibilities of senders and recipients. It also mentions that transfers need to respect the classification of the information being moved.
How to implement information transfer
Map how information actually moves
Start by listing the channels in real use, not the ones in the policy. Ask each team how they send files to customers, how they receive data from suppliers, and what they do when the official tool is awkward. Shadow channels such as personal messaging apps and free file-sharing sites are the ones that cause incidents, and you cannot write rules for something you have not seen.
For each channel, record what kinds of information it carries, who uses it and whether it crosses the organizational boundary. A simple table is enough: channel, purpose, approved for which classification levels, and owner. This also feeds your inventory of information and other associated assets.
Set rules by classification
Rules are easiest to follow when they are tied to the level of the information. If you have a scheme from classification of information and visible labels from labelling of information, the logic is straightforward. For example:
- Public information may go through any channel
- Internal information may be sent through approved company tools but not to personal accounts
- Confidential information requires an approved secure channel, encryption in transit and confirmation of the recipient
- Restricted information may need additional steps such as encrypted attachments with the key sent separately, or in-person handover
Keep the matrix to one page. Include the practical details people ask about: which file-sharing tool to use, whether expiring links are required, whether attachments are allowed, and what to do when a recipient cannot use the approved method.
Cover physical and verbal transfer too
Courier and postal transfers need tracking, tamper-evident packaging for sensitive items and a way to confirm receipt. Media sent by post should be handled as set out for storage media, including encryption where the information warrants it. For information carried off-site by staff, the rules for security of assets off-premises apply.
Verbal transfer is the one people forget. Give brief guidance on discussing sensitive matters in public places, on speakerphone and in open-plan offices, and remind people that meeting recordings and transcripts are information too. Short and sensible beats long and ignored.
Put agreements in place with outside parties
Where information regularly flows to another organization, agree the terms. That might be a clause in the contract, a data exchange schedule or a separate agreement. It should say what is exchanged, in what format, over which channel, who is responsible at each end, how the information is protected, how long it is kept and what happens when something goes wrong. For individuals and contractors, confidentiality or non-disclosure agreements complement these arrangements. If personal data is involved, check with your privacy adviser what additional terms the relevant law may require, as the details vary by jurisdiction.
Also think about the transfer of information between your own environments and between sites. A nightly job copying a database export to a reporting server is a transfer, and it needs to be covered by the same thinking.
Finally, keep the rules honest by testing them. Once or twice a year, pick a few recent transfers of sensitive information and trace them: which channel was used, whether the recipient was verified, and whether the agreement on file matches what happened. Treat gaps as improvement points, not blame. This also gives you ready evidence for the auditor and a natural input to your management review.
Related controls and clauses
A.5.12 connection. Classification of information determines how careful a given transfer needs to be.
A.5.13 connection. Labelling of information lets the sender and the recipient see what rules apply.
A.5.10 connection. Acceptable use of information and other associated assets sets the general expectations that the transfer rules refine.
A.6.6 connection. Confidentiality or non-disclosure agreements bind the individuals who receive your information.
A.7.9 connection. Security of assets off-premises covers information carried outside your buildings.
A.7.10 connection. Storage media covers drives and tapes that travel by hand or post.
Clause 4.2 connection. Clause 4.2, Understanding the needs and expectations of interested parties, often reveals transfer requirements set by customers and regulators.
Forward reference. Access control, A.5.15, is the next control in the series. It governs who can reach information once it has arrived.
What auditors check
Rules for each channel. Auditors look for documented rules or procedures covering email, file sharing, messaging, physical delivery and verbal exchange, and compare them with the channels staff actually use.
Alignment with classification. They check that higher-classified information has stronger transfer requirements, and sample recent transfers of sensitive data to see whether the rules were followed.
Agreements with external parties. Expect requests for contracts, data exchange agreements or confidentiality terms for your main customers and suppliers.
Technical enforcement. Where rules say encryption or approved tools, auditors may ask to see settings such as enforced TLS, restrictions on external sharing or blocking of unapproved services.
Staff knowledge. Interviews reveal whether people know which channel to use for which kind of data and what to do when it does not fit.
Handling of mistakes. They look at how misdirected emails and wrongly shared links are reported, linked to your information security event reporting process.
Common mistakes to avoid
Writing rules for email only. Most real leakage happens through shared links, chat tools and exports. Cover them all.
No approved route for the awkward case. If the approved tool cannot handle a large file or an external user, people will improvise. Provide an alternative.
Ignoring physical and verbal transfer. Auditors regularly ask about courier packages and discussions in shared spaces. A line in the procedure goes a long way.
Relying on trust in agreements. A signed agreement does not prove that the other party applies it. For high-risk flows, ask for evidence or test the arrangement.
Permanent sharing links. Links that never expire and can be opened by anyone with the address slowly turn a controlled transfer into open access. Use expiry and recipient restrictions.
Forgetting internal transfers. Moving data between environments, regions or teams deserves the same attention as sending it to a customer.
How 27kay can help
We help organizations map how information really moves and turn it into rules that people can follow without slowing down. As part of ISO 27001 implementation, we build a short channel and classification matrix, review your key agreements with outside parties and prepare the evidence an auditor will ask for. For the full picture, see our ISO 27001 knowledge hub.
If a colleague had to send a confidential file to a customer in the next five minutes, would they know exactly how? Get in touch - we will help you make that easy and safe.