ISO 27002:2022, Control 5.13 – Labelling of Information

ISO 27002:2022 Revised Controls

Book a demo

close,up,of,african,child,browsing,internet,on,laptop.,hands

Labelling of Information is a procedure that enables organisations to put their information classification scheme into practice by attaching classification labels to relevant information assets.

Control 5.13 addresses how organisations should develop, implement and manage a robust information labelling procedure based on the classification scheme adopted through Control 5.12.

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 Table

Control TypeInformation Security PropertiesCybersecurity ConceptsOperational CapabilitiesSecurity Domains
#Preventive#Confidentiality
#Integrity
#Availability
#Protect#Information Protection#Defence
#Protection
Trusted by companies everywhere
  • Simple and easy to use
  • Designed for ISO 27001 success
  • Saves you time and money
Book your demo
img

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.

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.

Get a Headstart
on ISO 27002

The only compliance
solution you need
Book your demo

Updated for ISO 27001 2022
  • 81% of the work done for you
  • Assured Results Method for certification success
  • Save time, money and hassle
Book your demo
img

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.

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.

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.

Are you ready for
the new ISO 27002

We’ll give you an 81% headstart
from the moment you log in
Book your demo

New Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
5.7NewThreat intelligence
5.23NewInformation security for use of cloud services
5.30NewICT readiness for business continuity
7.4NewPhysical security monitoring
8.9NewConfiguration management
8.10NewInformation deletion
8.11NewData masking
8.12NewData leakage prevention
8.16NewMonitoring activities
8.23NewWeb filtering
8.28NewSecure coding

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

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
6.107.1.1Screening
6.207.1.2Terms and conditions of employment
6.307.2.2Information security awareness, education and training
6.407.2.3Disciplinary process
6.507.3.1Responsibilities after termination or change of employment
6.613.2.4Confidentiality or non-disclosure agreements
6.706.2.2Remote working
6.816.1.2, 16.1.3Information security event reporting

Physical Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
7.111.1.1Physical security perimeters
7.211.1.2, 11.1.6Physical entry
7.311.1.3Securing offices, rooms and facilities
7.4NewPhysical security monitoring
7.511.1.4Protecting against physical and environmental threats
7.611.1.5Working in secure areas
7.711.2.9Clear desk and clear screen
7.811.2.1Equipment siting and protection
7.911.2.6Security of assets off-premises
7.1008.3.1, 08.3.2, 08.3.3, 11.2.5Storage media
7.1111.2.2Supporting utilities
7.1211.2.3Cabling security
7.1311.2.4Equipment maintenance
7.1411.2.7Secure disposal or re-use of equipment

Technological Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
8.106.2.1, 11.2.8User endpoint devices
8.209.2.3Privileged access rights
8.309.4.1Information access restriction
8.409.4.5Access to source code
8.509.4.2Secure authentication
8.612.1.3Capacity management
8.712.2.1Protection against malware
8.812.6.1, 18.2.3Management of technical vulnerabilities
8.9NewConfiguration management
8.10NewInformation deletion
8.11NewData masking
8.12NewData leakage prevention
8.1312.3.1Information backup
8.1417.2.1Redundancy of information processing facilities
8.1512.4.1, 12.4.2, 12.4.3Logging
8.16NewMonitoring activities
8.1712.4.4Clock synchronization
8.1809.4.4Use of privileged utility programs
8.1912.5.1, 12.6.2Installation of software on operational systems
8.2013.1.1Networks security
8.2113.1.2Security of network services
8.2213.1.3Segregation of networks
8.23NewWeb filtering
8.2410.1.1, 10.1.2Use of cryptography
8.2514.2.1Secure development life cycle
8.2614.1.2, 14.1.3Application security requirements
8.2714.2.5Secure system architecture and engineering principles
8.28NewSecure coding
8.2914.2.8, 14.2.9Security testing in development and acceptance
8.3014.2.7Outsourced development
8.3112.1.4, 14.2.6Separation of development, test and production environments
8.3212.1.2, 14.2.2, 14.2.3, 14.2.4Change management
8.3314.3.1Test information
8.3412.7.1Protection of information systems during audit testing
Get a Headstart on ISO 27001
  • All updated with the 2022 control set
  • Make 81% progress from the minute you log in
  • Simple and easy to use
Book your demo
img

Explore ISMS.online's platform with a self-guided tour - Start Now