Skip to content
Work smarter with our new enhanced navigation!
See how IO makes compliance easier.
Read the blog

Purpose of Control 5.14

Control 5.14 is a preventive type of control that requires organisations to put in place appropriate rules, procedures, and/or agreements to maintain the security of data when it is shared within an organisation or when transmitted to third parties.

Attributes of Control 5.14

Control Type Information Security Properties Cybersecurity Concepts Operational Capabilities Security Domains
#Preventive #Confidentiality #Protect #Asset Management #Protection
#Integrity #Information Protection
#Availability

Ownership of Control 5.14

While the development and implementation of rules, procedures, and agreements require the support and approval of high-level management, the cooperation and expertise of different stakeholders within an organisation, including the legal team, IT staff, and upper management, is of critical importance.

For instance, the legal team should ensure that the organisation enters into transfer agreements with third parties and that these agreements are in line with the requirements specified in Control 5.14. Likewise, the IT team should take an active part in defining and implementing controls to maintain the security of data as set out in 5.14.




ISMS.online gives you an 81% Headstart from the moment you log on

ISO 27001 made easy

We’ve done the hard work for you, giving you an 81% Headstart from the moment you log on. All you have to do is fill in the blanks.




General Guidance on Control 5.14

Compliance with 5.14 entails the development of rules, procedures, and agreements, including a topic-specific information transfer policy, that provides data in transit with a level of protection appropriate to the classification assigned to that information.

In other words, the level of protection should match the level of criticality and sensitivity of information transmitted.

Furthermore, Control 5.14 specifies that organisations must sign transfer agreements with recipient third parties to guarantee secure transmission of data.

Control 5.14 groups the types of transfer into three categories:

  • Electronic transfer
  • Physical storage media transfer
  • Verbal transfer

Before, moving on to describe the specific requirements for each type of transfer, Control 5.14 lists the elements that must be included in all rules, procedures, and agreements for all three types of transfers in general:

  • Organisations must define controls appropriate to the level of classification of the information to protect the information in transit from unauthorised access, modification, interception, copying, destruction, and denial-of-service attacks.
  • An organisation must keep control over the chain of custody while it is in transit and must define and implement controls to ensure traceability of information.
  • Relevant parties involved in the transfer of information should be defined and their contact details should be provided. This may include information owners and security officers.
  • Allocation of liabilities in case a data breach occurs.
  • Using a labeling system.
  • Ensuring the availability of the transfer service.
  • Creating topic-specific guidelines on the information transfer methods.
  • Guidelines for storage and deletion of all business records, including messages.
  • Analysis of the impact any applicable laws, regulations, or other obligations may have over the transfer.



climbing

Embed, expand and scale your compliance, without the mess. IO gives you the resilience and confidence to grow securely.




Supplementary Guidance on Electronic Transfer

After listing the minimum content requirements for rules, procedures, and agreements common across all three types of transfer, Control 5.14 lists specific content requirements for each type of transfer.

Rules, agreements, and procedures should address the following issues when information is transferred electronically:

  • Detection and prevention of malware attacks.
  • Protecting sensitive information contained in the attachments transferred.
  • Ensuring that all communications are sent to the correct recipients and the risk of sending communications to wrong email addresses, addresses, or phone numbers is eliminated.
  • Obtaining prior authorization before starting to use any public communication services.
  • Implementing stricter authentication methods when data is transmitted via public networks.
  • Imposing restrictions on the use of e-communication services such as banning automatic forwarding.
  • Advise personnel on not using short message or instant message services to share sensitive data because this content may be seen by unauthorised individuals in public spaces.
  • Advising staff and other relevant parties on the security risks presented by fax machines such as the risk of unauthorised access or re-routing of messages to specific numbers.

Supplementary Guidance on Physical Storage Media Transfer

When information is shared via physical means such as papers, the rules, procedures, and agreements should cover the following:

  • Assignment of responsibilities for notification of transmission, dispatch, and receipt.
  • Ensuring correct addressing and transportation of the message.
  • Packaging eliminates the risk of damage to the contents that may arise when the content is in transit. For instance, packaging should be good enough to not be affected by heat or moisture.
  • A list of reliable couriers agreed and authorised by the management.
  • Description of courier identification standards.
  • Use of tamper-resistant controls such as bags if the level of sensitivity and criticality of information demands it.
  • Procedures to verify IDs of couriers.
  • Approved list of third parties providing transportation or courier services depending on the level of classification.
  • Keeping log records of the time of delivery, list of authorised recipients, protections applied, and receipt at the destination.

Supplementary Guidance on Verbal Transfer

Control 5.14 states that when personnel exchange information within the organisation or when they transmit data to external parties, they should be informed of the following risks:

  • They should avoid having confidential conversations over insecure public channels or in public spaces.
  • They should not leave voice messages that contain confidential information considering the risk of replay by unauthorised persons and the risk of re-routing of the message to third parties.
  • Each individual, whether employees or other relevant third parties, should be screened before being allowed in to listen to conversations.
  • Rooms, where confidential conversations take place, should be equipped with appropriate controls such as sound-proofing.
  • They should give a disclaimer before having any sensitive conversation.



ISMS.online supports over 100 standards and regulations, giving you a single platform for all your compliance needs.

ISMS.online supports over 100 standards and regulations, giving you a single platform for all your compliance needs.




Changes and Differences From ISO 27002:2013

27002:2022/5.14 replaces 27002:2013/(13.2.1, 13.2.2. 13.2.3).

While the two controls are similar to some extent, two key differences make the 2022 version’s requirements more onerou.

Specific Requirements for Electric, Physical and Verbal Transfers

In the 2013 version, section 13.2.3 addressed the specific requirements for the transfer of information via electronic messaging.

However, it did not separately address the transfer of information via verbal or physical manner.

In contrast, the 2022 version clearly identifies three types of information transfer and then sets out the content requirements for each of them separately.

2022 Version Sets Stricter Requirements for Electronic Transfer

While section 13.2.3 contained specific requirements for the content of agreements for electronic messaging, the 2022 Version imposes stricter obligations on organisations.

The 2022 Version requires organisations to describe and implement new controls in the rules, procedures, and agreements for electronic transfers.

For instance, organisations should advise their employees not to use SMS services when they include sensitive information.

More Detailed Requirements for Physical Transfers

The 2022 version sets more stringent requirements on the physical storage media transfer. For instance, its requirements are more comprehensive in respect of authentication of couriers and the types of damages that should be prevented.

Structural Changes

In the 2013 version, there was an explicit reference to specific requirements for agreements for information transfers. However, the ‘Rules’ and ‘Procedures’ were not addressed specifically.

In contrast, the 2022 version sets out the specific requirements for each of these three mechanisms.

New ISO 27002 Controls

New Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
5.7 NEW Threat intelligence
5.23 NEW Information security for use of cloud services
5.30 NEW ICT readiness for business continuity
7.4 NEW Physical security monitoring
8.9 NEW Configuration management
8.10 NEW Information deletion
8.11 NEW Data masking
8.12 NEW Data leakage prevention
8.16 NEW Monitoring activities
8.23 NEW Web filtering
8.28 NEW Secure coding
Organisational Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
5.1 05.1.1, 05.1.2 Policies for information security
5.2 06.1.1 Information security roles and responsibilities
5.3 06.1.2 Segregation of duties
5.4 07.2.1 Management responsibilities
5.5 06.1.3 Contact with authorities
5.6 06.1.4 Contact with special interest groups
5.7 NEW Threat intelligence
5.8 06.1.5, 14.1.1 Information security in project management
5.9 08.1.1, 08.1.2 Inventory of information and other associated assets
5.10 08.1.3, 08.2.3 Acceptable use of information and other associated assets
5.11 08.1.4 Return of assets
5.12 08.2.1 Classification of information
5.13 08.2.2 Labelling of information
5.14 13.2.1, 13.2.2, 13.2.3 Information transfer
5.15 09.1.1, 09.1.2 Access control
5.16 09.2.1 Identity management
5.17 09.2.4, 09.3.1, 09.4.3 Authentication information
5.18 09.2.2, 09.2.5, 09.2.6 Access rights
5.19 15.1.1 Information security in supplier relationships
5.20 15.1.2 Addressing information security within supplier agreements
5.21 15.1.3 Managing information security in the ICT supply chain
5.22 15.2.1, 15.2.2 Monitoring, review and change management of supplier services
5.23 NEW Information security for use of cloud services
5.24 16.1.1 Information security incident management planning and preparation
5.25 16.1.4 Assessment and decision on information security events
5.26 16.1.5 Response to information security incidents
5.27 16.1.6 Learning from information security incidents
5.28 16.1.7 Collection of evidence
5.29 17.1.1, 17.1.2, 17.1.3 Information security during disruption
5.30 5.30 ICT readiness for business continuity
5.31 18.1.1, 18.1.5 Legal, statutory, regulatory and contractual requirements
5.32 18.1.2 Intellectual property rights
5.33 18.1.3 Protection of records
5.34 18.1.4 Privacy and protection of PII
5.35 18.2.1 Independent review of information security
5.36 18.2.2, 18.2.3 Compliance with policies, rules and standards for information security
5.37 12.1.1 Documented operating procedures
People Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
6.1 07.1.1 Screening
6.2 07.1.2 Terms and conditions of employment
6.3 07.2.2 Information security awareness, education and training
6.4 07.2.3 Disciplinary process
6.5 07.3.1 Responsibilities after termination or change of employment
6.6 13.2.4 Confidentiality or non-disclosure agreements
6.7 06.2.2 Remote working
6.8 16.1.2, 16.1.3 Information security event reporting
Physical Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
7.1 11.1.1 Physical security perimeters
7.2 11.1.2, 11.1.6 Physical entry
7.3 11.1.3 Securing offices, rooms and facilities
7.4 NEW Physical security monitoring
7.5 11.1.4 Protecting against physical and environmental threats
7.6 11.1.5 Working in secure areas
7.7 11.2.9 Clear desk and clear screen
7.8 11.2.1 Equipment siting and protection
7.9 11.2.6 Security of assets off-premises
7.10 08.3.1, 08.3.2, 08.3.3, 11.2.5 Storage media
7.11 11.2.2 Supporting utilities
7.12 11.2.3 Cabling security
7.13 11.2.4 Equipment maintenance
7.14 11.2.7 Secure disposal or re-use of equipment
Technological Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
8.1 06.2.1, 11.2.8 User endpoint devices
8.2 09.2.3 Privileged access rights
8.3 09.4.1 Information access restriction
8.4 09.4.5 Access to source code
8.5 09.4.2 Secure authentication
8.6 12.1.3 Capacity management
8.7 12.2.1 Protection against malware
8.8 12.6.1, 18.2.3 Management of technical vulnerabilities
8.9 NEW Configuration management
8.10 NEW Information deletion
8.11 NEW Data masking
8.12 NEW Data leakage prevention
8.13 12.3.1 Information backup
8.14 17.2.1 Redundancy of information processing facilities
8.15 12.4.1, 12.4.2, 12.4.3 Logging
8.16 NEW Monitoring activities
8.17 12.4.4 Clock synchronization
8.18 09.4.4 Use of privileged utility programs
8.19 12.5.1, 12.6.2 Installation of software on operational systems
8.20 13.1.1 Networks security
8.21 13.1.2 Security of network services
8.22 13.1.3 Segregation of networks
8.23 NEW Web filtering
8.24 10.1.1, 10.1.2 Use of cryptography
8.25 14.2.1 Secure development life cycle
8.26 14.1.2, 14.1.3 Application security requirements
8.27 14.2.5 Secure system architecture and engineering principles
8.28 NEW Secure coding
8.29 14.2.8, 14.2.9 Security testing in development and acceptance
8.30 14.2.7 Outsourced development
8.31 12.1.4, 14.2.6 Separation of development, test and production environments
8.32 12.1.2, 14.2.2, 14.2.3, 14.2.4 Change management
8.33 14.3.1 Test information
8.34 12.7.1 Protection of information systems during audit testing

How ISMS.online Helps

ISO 27002 implementation is simpler with our step-by-step checklist that guides you through the whole process, from defining the scope of your ISMS through risk identification and control implementation.

Get in touch today to book a demo.


Sam Peters

Sam is Chief Product Officer at ISMS.online and leads the development on all product features and functionality. Sam is an expert in many areas of compliance and works with clients on any bespoke or large-scale projects.

Take a virtual tour

Start your free 2-minute interactive demo now and see
ISMS.online in action!

platform dashboard full on mint

We’re a Leader in our Field

4/5 Stars
Users Love Us
Leader - Winter 2026
Regional Leader - Winter 2026 UK
Regional Leader - Winter 2026 EU
Regional Leader- Winter 2026 Mid-market EU
Regional Leader - Winter 2026 EMEA
Regional Leader - Winter 2026 Mid-market EMEA

"ISMS.Online, Outstanding tool for Regulatory Compliance"

— Jim M.

"Makes external audits a breeze and links all aspects of your ISMS together seamlessly"

— Karen C.

"Innovative solution to managing ISO and other accreditations"

— Ben H.