A.5 Organizational controls

A.5.14 Information transfer

Not mandatory by default – decided in your SoA

What it means in plain language

Protect information when it is transferred – by email, file sharing, removable media or verbally – with rules and agreements.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Information transfers cross boundaries where the sender may lose control of recipients, copies and retention. A secure channel is only one part of the problem: the wrong recipient can still receive an encrypted file, and a legitimate recipient may keep it longer than agreed. Transfer rules therefore need to connect information sensitivity, destination assurance, recipient verification and the responsibilities of the parties involved.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Sensitive files are sent using personal sharing accounts because the approved service lacks a usable process for external recipients or large attachments.
  • Links remain accessible after the business purpose ends, or access is granted to a broad group without verifying the intended recipients.
  • A transfer agreement specifies encryption but omits ownership of onward sharing, incident communication, retention or deletion of information held by the recipient.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Inventory significant transfer routes, including email, shared workspaces, APIs, removable media and verbal exchanges. For each route, identify the information owner, sensitivity and intended recipient so the approved method reflects the actual risk rather than habit or convenience.
  • Define approved channels and recipient checks. For sensitive external sharing, consider named-user access, expiry and an independent confirmation of the destination. Document how staff request exceptions and what protection applies when the normal channel cannot support a necessary transfer.
  • Agree responsibilities with external parties before regular exchanges begin. Address permitted use, onward disclosure, protective measures, incident communication and end-of-purpose disposal. Use qualified legal input for applicable obligations instead of treating a generic confidentiality clause as a complete transfer agreement.
  • Test a sample transfer from approval through recipient access and eventual revocation or deletion. Review access logs and failed delivery cases without unnecessarily retaining the transferred content. Update the rules when new collaboration tools, destinations or contractual commitments change the risks.

What an auditor will ask to see

  • An information transfer policy and channel register showing permitted methods, sensitivity restrictions, recipient-verification steps and the route for approving exceptional transfers.
  • Representative sharing configurations and activity records demonstrating named recipients, appropriate protection, limited access duration and removal of access when the purpose ends.
  • Transfer agreements or approved instructions allocating responsibilities for handling, onward sharing, incident communication and disposal, supported by a completed operational sample.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.14. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.13 — Labelling of information and A.8.24 — Use of cryptography. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.