A.5 Organizational controls

A.5.13 Labelling of information

Not mandatory by default – decided in your SoA

What it means in plain language

Label information according to its classification so the level is visible to everyone handling it.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

A classification decision is easily lost when information leaves the repository in which its owner assigned it. Labels carry that decision into documents, messages, exports and other workflows so recipients can recognise the required handling. They only work when people understand their meaning and when technical systems preserve them; a prominent confidentiality footer does not by itself prevent unauthorised sharing.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Documents display sensitivity labels, but exported files or printed copies lose them and recipients receive no equivalent handling instructions.
  • Automated labelling rules classify content incorrectly, while users have no practical way to challenge a result or obtain an approved exception.
  • The same label has different meanings in different departments or supplier platforms, creating inconsistent handling at organisational boundaries and during transfers.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define labelling requirements for the information formats your organisation actually uses, including files, email, physical records and datasets. Link each label to the classification policy and explain exceptions where an explicit mark is impractical or would expose sensitive information.
  • Configure templates or sensitivity tools to apply labels consistently at creation and during common exports. Test ordinary user workflows such as conversion, attachment, printing and mobile editing. Keep the results so platform limitations and compensating instructions remain visible.
  • Train handlers to interpret labels and select the right action rather than treating the label as decoration. Establish a route for correcting misclassification, with approval for downgrades where needed. Record material exceptions and ensure the underlying access settings remain appropriate.
  • Agree how labels are understood when information is shared with partners. Sample transfers and downstream copies to check that the sensitivity remains recognisable and the recipient can apply the required protection. Review rules after tooling or classification changes, and retire inconsistent legacy templates.

What an auditor will ask to see

  • Labelling procedures and examples covering the main information formats, with a clear relationship between the label displayed and the required handling rules.
  • Configuration and test results demonstrating label persistence through export, email, printing or sharing, including known limitations and instructions for affected users.
  • Approved relabelling or downgrade records, training material and sampled partner transfers showing that people and systems interpret sensitivity consistently across the information lifecycle.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.13. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.12 — Classification of information and A.8.12 — Data leakage prevention. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.