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.
ISO 27001 made easy
An 81% Headstart from day one
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 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, all in one place
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.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
| 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 |
| 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 |
| 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 |
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.
