Purpose of Control 5.13

5.13 is a preventive control that protects information assets against security risks by helping organisations achieve two distinct purposes:

  • Making it easier to demonstrate the level of classification each information asset is given when the information is communicated internally and externally and when it is accessed and used by employees and third parties.
  • Streamlining the process of automating information management and processing.

Attributes of Control 5.13

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

Ownership of Control 5.13

Considering that adding metadata to digital assets is the primary way of labelling information assets, metadata stewards shall be accountable for proper implementation of labelling procedure.

Alongside the metadata stewards, asset owners with access and modification authorisations shall be accountable for proper labelling of all data assets and shall make necessary modifications to labelling if needed.




Get an 81% headstart

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.

Book a demo



General Guidance on How to Comply

Control 5.13 identifies four specific steps that organisations should implement to carry out labelling of information in compliance with 5.13.

Develop and implement an Information Labelling Procedure

Organisations should develop an organisation-wide Information Labelling Procedure that adheres to the information classification scheme created in accordance with Control 5.12.

Furthermore, 5.13 requires that this Procedure be extended to all information assets, regardless of whether it is in digital or paper format and that the labels must be easy to recognise.

While there is no limit to what this Procedure document can contain, the Control 5.13 states that the Procedures should at least include the following:

  • Description of the methods to attach labels to information assets depending on the storage medium and how the data is accessed.
  • Where the labels are to be attached for each type of information asset.
  • Which information assets will not be labelled, if any. For instance, an organisation may omit labelling public data to streamline the information labelling process.
  • Description of measures for cases where it is not possible to label certain types of information due to technical, legal or contractual limitations.
  • The rules on how the labelling of information transmitted to internal or external parties should be handled.
  • For digital assets, the Procedure must explain how the metadata should be inserted.
  • Names of labels to be used for all assets.

Provide Adequate Training to Staff on How to Adhere to the Labelling Procedure

The Procedure for labelling of Information can be effective only to the extent that Personnel and other relevant stakeholders are well-informed about how to correctly label information and how to deal with labelled information assets.

Therefore, organisations should provide staff and other relevant parties with training on the Procedure.

Use Metadata for Labelling of Digital Information Assets

5.13 requires the use of metadata for labelling of digital information assets.

Furthermore, it notes that the metadata should be deployed in a way that makes it easy and efficient to identify and search for information and also in a way that streamlines the decision-making process between systems related to labelled information.

Take Extra Measures to Label Sensitive Data That May Outflow of the System

Considering the risks involved in outward transfer of sensitive data from systems, 5.13 recommends organisations to label these information assets with those most appropriate to the level of criticality and sensitivity of the information concerned.

Supplementary Guidance on Control 5.13

The 5.13 highlights that Identification and accurate labelling of classified information is vital to security of data sharing operations.

In addition to the four specific steps described above, 5.13 also recommends that organisations insert additional metadata points such as the name of the process that created the information asset and the time of such creation.

Furthermore, the 5.13 refers to the common labelling techniques that organisations can implement:

  • Physical Labels
  • Headers and footers
  • Metadata
  • Watermarking
  • Rubber-stamps

Lastly, the 5.13 emphasises that labelling information assets as ‘confidential’ and ‘classified’ can have unintended consequences because it may make it easier for malicious actors to search through and find sensitive information assets.




Manage all your compliance in one place

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

Book a demo



Changes and Differences From ISO 27002:2013

27002:2022/5.13 replaces 27002:2013/8.2.2 (Labelling of Information).

While the two controls are similar to some extent, there are two key differences which makes the 2022 version more comprehensive.

New Requirements on the Use of Metadata

Whereas the 2013 version referred to metadata as a labelling technique, it did not impose any specific obligations for compliance when using metadata.

In contrast, the 2022 version brings strict requirements on how to use metadata technique. To illustrate, the 2022 version requires that:

  • Metadata is added to information in a way that makes it easy to identify, manage and discover information in an efficient way.
  • Metadata for the name of the organisational process that created a specific asset and its time should be inserted.

Content of the Information Labelling Procedure Must Be More Detailed

Contrary to the 2022 version, the 2013 version did not specify the minimum content that should be included in a Information Labelling Procedure.

New ISO 27002 Controls

New Controls


Organisational Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
5.105.1.1, 05.1.2Policies for information security
5.206.1.1Information security roles and responsibilities
5.306.1.2Segregation of duties
5.407.2.1Management responsibilities
5.506.1.3Contact with authorities
5.606.1.4Contact with special interest groups
5.7NewThreat intelligence
5.806.1.5, 14.1.1Information security in project management
5.908.1.1, 08.1.2Inventory of information and other associated assets
5.1008.1.3, 08.2.3Acceptable use of information and other associated assets
5.1108.1.4Return of assets
5.12 08.2.1Classification of information
5.1308.2.2Labelling of information
5.1413.2.1, 13.2.2, 13.2.3Information transfer
5.1509.1.1, 09.1.2Access control
5.1609.2.1Identity management
5.17 09.2.4, 09.3.1, 09.4.3Authentication information
5.1809.2.2, 09.2.5, 09.2.6Access rights
5.1915.1.1Information security in supplier relationships
5.2015.1.2Addressing information security within supplier agreements
5.2115.1.3Managing information security in the ICT supply chain
5.2215.2.1, 15.2.2Monitoring, review and change management of supplier services
5.23NewInformation security for use of cloud services
5.2416.1.1Information security incident management planning and preparation
5.2516.1.4Assessment and decision on information security events
5.2616.1.5Response to information security incidents
5.2716.1.6Learning from information security incidents
5.2816.1.7Collection of evidence
5.2917.1.1, 17.1.2, 17.1.3Information security during disruption
5.30NewICT readiness for business continuity
5.3118.1.1, 18.1.5Legal, statutory, regulatory and contractual requirements
5.3218.1.2Intellectual property rights
5.3318.1.3Protection of records
5.3418.1.4Privacy and protection of PII
5.3518.2.1Independent review of information security
5.3618.2.2, 18.2.3Compliance with policies, rules and standards for information security
5.3712.1.1Documented operating procedures


People Controls


Physical Controls


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.

Our platform is intuitive and easy-to-use. It’s not just for highly technical people; it’s for everyone in your organisation. We encourage you to involve staff at all levels of your business in the process of building your ISMS, because that helps you to build a truly sustainable system.

Get in touch today to book a demo.


Jump to topic

Max Edwards

Max works as part of the ISMS.online marketing team and ensures that our website is updated with useful content and information about all things ISO 27001, 27002 and compliance.

ISMS Platform Tour

Interested in an ISMS.online platform tour?

Start your free 2-minute interactive demo now and experience the magic of ISMS.online in action!

Try it for free

We’re a Leader in our Field

Users Love Us
Leader Winter 2025
Leader Winter 2025 United Kingdom
Best ROI Winter 2025
Fastest Implementation Winter 2025
Most Implementable Winter 2025

"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.

DORA is here! Supercharge your digital resilience today with our powerful new solution!