A.5.13ISO 27001Last reviewed 19 February 2026

ISO 27001 A.5.13: Labelling of information

Classification is only useful if people can actually see it. A document classified as "Confidential" that carries no visible marking will inevitably get treated as if it were internal or public. Labelling makes classification actionable.

Work through the ISO 27001 assessment, record supporting evidence and review the gaps in your answers.

Start my free ISO 27001 assessmentNo account · No credit card · Save when useful

Requirement summary

An appropriate set of procedures for information labelling shall be developed and implemented in accordance with the information classification scheme adopted by the organization.

Check the source wording and scope in ISO/IEC 27001:2022. The guidance below explains how to approach a review.

In Plain Language

This applies to both physical and digital information. Paper documents need classification markings in headers or footers. Digital files need metadata, watermarks, or visible labels. Emails may need classification tags in the subject line. Storage media should be labelled with the highest classification of information they contain.

Be practical about it. Not every single document needs an individual label. You can define that all information on a particular system inherits a certain classification, or that public website content does not need explicit markings. The key is defining clear rules for when labelling is mandatory versus when context is sufficient.

How to Implement

Develop labelling procedures for every information format your organisation uses. Cover paper documents (header and footer markings, cover pages), electronic documents (metadata, watermarks, visual labels), emails (subject line tags, classification selectors), presentations (slide headers and footers), storage media (physical labels on USB drives, hard drives, tapes), and information systems (banner pages, login screen classifications).

Deploy tools to make labelling easy. Microsoft Information Protection (MIP) can add persistent labels and metadata to Office documents and emails. Email classification add-ins can require users to select a classification before sending. Document management systems can enforce classification tagging on upload.

Define clear rules for when labelling is required versus when it can be implied. Documents on a classified file share might inherit the share's classification. Public content on your website probably does not need individual labels. Spell out these exceptions explicitly.

Train people on how to label correctly. Provide templates with pre-configured classification headers and footers. Give guidance on what to do when they receive unlabelled information - the default should be to treat it as the higher classification until confirmed.

Audit labelling compliance regularly. Sample documents, emails, and storage media to check labels are being applied correctly. Address failures through awareness reinforcement first, and escalate through your disciplinary process if needed.

Evidence to review

Documented labeling procedures for all information formats and media types
Technical tools deployed to support information labeling such as MIP or email classifiers
Samples of labeled documents, emails, and media demonstrating correct labeling
Training records showing personnel have been trained on labeling procedures
Audit records of labeling compliance checks

Common Mistakes

No labeling procedures exist or they only cover one format such as paper documents
Digital documents and emails are not labeled with classification markings
Personnel do not consistently apply labels due to lack of training or tools
Labeling tools are available but not mandatory or enforced
Removable media containing classified information is not labeled

Related Controls Across Frameworks

Framework	Control ID	Relationship
SOC 2	SOC 2 CC6.1: Logical and Physical Access - Security Software, Infrastructure, and Architectures	Partial overlap
GDPR	GDPR Art.32: Security of Processing	Partial overlap

Frequently Asked Questions

Do we need to label every single document?

No, and trying to would probably make the whole scheme collapse under its own weight. Define when labelling is mandatory and when context is enough. Confidential and restricted documents should always be explicitly labelled. For internal-use material, you might allow context-based classification where everything in a particular system or location inherits a level. Public information generally does not need labels. Just make sure the rules are clear and documented.

What tools can help automate information labeling?

Microsoft Information Protection (MIP) is the most common choice for Office documents and emails - it handles visual markings, metadata, and protection in one package. Boldon James, Titus, and Digital Guardian offer alternatives. For email specifically, classification add-ins can force users to pick a label before hitting send. For file servers, automated classification tools can scan content and apply labels. The right choice depends on your technology stack and budget.

Track ISO 27001 compliance in one place

Work through the ISO 27001 assessment, record supporting evidence and review the gaps in your answers.

Start Free Assessment

Start without an account · Sign up only to save

Start my free ISO 27001 assessment