A.5 Organizational controls

A.5.12 Classification of information

Not mandatory by default – decided in your SoA

What it means in plain language

Classify information by how sensitive it is (e.g. Public, Internal, Confidential, Strictly Confidential) so people know how to protect 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

Information cannot be protected proportionately if everyone makes a different assumption about its sensitivity. Classification gives owners and handlers a shared basis for decisions about access, storage, transfer and disposal. The scheme must reflect confidentiality, integrity and availability needs as well as obligations; a simple label that addresses secrecy alone may overlook records whose accuracy or timely availability is critical to the business.

Common auditor findings to check for

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

  • The policy defines classification levels but gives no usable examples, so employees assign identical information to different levels across departments.
  • Data owners have not classified major repositories, and default settings allow sensitive records to inherit broader access than their risk warrants.
  • A classification remains unchanged after publication, contract expiry or aggregation, even though the resulting information now has a different protection need.

How you can implement it

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

  • Create a small classification scheme with clear criteria and examples drawn from actual business information. Explain how contractual restrictions, personal information and operational dependence affect the decision. Assign an owner who can resolve uncertain cases rather than leaving users to guess.
  • Connect each level to practical handling rules for approved storage, access, transfer and retention. Test the rules against a real workflow so staff can comply without inventing workarounds. Record where a technical platform cannot enforce a required protection and how the gap is managed.
  • Ask information owners to classify key datasets and repositories, documenting the reasoning for high-impact cases. Include new information at creation or onboarding and examine combinations of records whose aggregated sensitivity differs from that of an individual item.
  • Review classification after meaningful changes such as new customers, publication or altered legal duties. Coordinate reclassification with labels, permissions and downstream copies, and explain the change to affected handlers. Maintain decisions so reviewers can understand why protections increased or decreased.

What an auditor will ask to see

  • An approved classification scheme with understandable criteria, business examples and defined ownership for resolving uncertainty or authorising a change in classification.
  • A sample of classified repositories and records showing that the assigned level matches sensitivity, obligations and the corresponding access and handling protections.
  • Reclassification decisions and associated changes to labels, access or transfer arrangements, demonstrating that information remains protected as its purpose and exposure evolve.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.5.13 — Labelling of information and A.5.14 — Information transfer. 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.