Skip to content
atlas

Data classification

Also known as: information classification

Sorting data by how sensitive it is - for example public, internal or confidential.

Draft - this entry has not been reviewed yet.

Formal

The practice of labelling information by how much harm its loss or leak would cause, so that each level gets matching rules for handling and protection.

In plain English

Like sorting post into postcards, letters and registered mail - each is handled with a different level of care.

In practice

In a Danish municipality, council meeting agendas are marked “public”, the staff handbook “internal” and case files about citizens' health “confidential”, which means they may only be sent by secure email.

Why it matters

Protecting everything to the highest level is too costly, and protecting everything to the lowest is dangerous; classification tells you where to put the effort.

How to put it into practice

The usual steps, in order. Adapt them to your organisation.

  1. Have management approve a scheme with three or four levels, such as public, internal, confidential and strictly confidential, each defined by the harm a leak or change would cause.
  2. For each level, write handling rules for access, encryption at rest and in transit, external sharing, printing, storage locations, retention and disposal.
  3. Map legal categories to a minimum level, for example GDPR special categories, criminal-offence data and CPR numbers as at least confidential.
  4. Make information owners responsible for classifying their data, starting with the most critical systems and data stores in the asset inventory.
  5. Set a sensible default label for unlabelled data and build the labels into your tools, for example Microsoft Purview sensitivity labels that drive encryption and DLP.
  6. Train staff with concrete examples of each level and how to send, store and share it.
  7. Use automatic classification, for example CPR-number patterns, to find sensitive data in existing file shares and mailboxes, and check the hits by hand.
  8. Review the scheme and a sample of labels every year, and lower the level when information loses sensitivity, such as a report after publication.

Common pitfalls

  • Using too many levels or marking everything confidential, so labels carry no signal and staff work around them.
  • Defining labels with no handling rules or technical enforcement behind them.
  • Leaving unlabelled data with no default protection at all.
  • Treating classification as a personal data exercise only, so non-personal secrets like tender prices or source code go unprotected.

Good guides

Technical deep dive

ISO/IEC 27002:2022 splits the topic across three controls: 5.12 (classification of information according to confidentiality, integrity, availability and relevant interested-party requirements), 5.13 (labelling, according to the classification scheme) and 5.14 (information transfer rules). The scheme itself is a small ordered set of levels, typically three to five, each defined by the harm that unauthorised disclosure or modification would cause, and each mapped to handling rules: who may access, whether encryption is mandatory at rest and in transit, whether external sharing, printing or removable media is allowed, retention and secure disposal. Classification is performed by the information owner, and the level should be reviewed as information ages, since a press release is confidential until it is published.

Public-sector and community schemes show the range. The Danish security circular for classified information uses TIL TJENESTEBRUG, FORTROLIGT, HEMMELIGT and YDERST HEMMELIGT, aligned with NATO and EU classified information (RESTREINT UE/EU RESTRICTED up to TRÈS SECRET UE/EU TOP SECRET). The Traffic Light Protocol, TLP 2.0 from FIRST (2022), is not a classification but a sharing marking for threat intelligence: TLP:RED, TLP:AMBER, TLP:AMBER+STRICT, TLP:GREEN and TLP:CLEAR. Most companies use simpler levels such as public, internal, confidential and strictly confidential.

Legal categories are an overlay, not a replacement. GDPR special categories (Art. 9) and criminal-offence data (Art. 10), and in Denmark CPR numbers, which the Data Protection Act (databeskyttelsesloven) § 11 regulates separately, usually force at least a confidential level, but a document can be highly confidential without containing personal data, for example a tender price or source code. Mapping each legal category to a minimum level keeps the two systems consistent.

Labels are only useful if machines can read them. Sensitivity labels stored in document metadata, such as Microsoft Purview labels, drive encryption, watermarking, DLP policies at the mail gateway and in endpoints, and CASB rules for cloud uploads. Automatic classifiers based on regular expressions (for example CPR-number patterns), fingerprinting or trained models help with the large volume of existing data, but produce false positives and cannot judge context. The typical failure modes are over-classification, where everything becomes confidential so the label carries no signal and staff route around it, and under-classification by default, where unlabelled data inherits no protection. Classification also underpins retention and deletion, discovery for data-subject access requests, and scoping of backups and encryption, which is why it pairs so directly with encryption and personal-data handling.

What to learn first

Everything this builds on, foundations first.

  1. Confidentiality
  2. →Data classification

Relationships

Don't confuse with
Classification
Mandated by
Security policy

Sources & further reading

Standards & official texts

  • ISO/IEC 27002:2022 - Control 5.12, Classification of information · ISO/IEC

Course material

  • Cyber Security Fast Track - Ordliste

Where this data comes from

This entry was drafted by an AI from the sources above and has not yet been checked by a person. Treat it as a starting point, and check anything important against the sources.

See the review queueSuggest a correction on GitHubThis term as JSON

Check yourself

Loading…

Atlas is in beta.