Skip to main content
Informationssicherheit / NIS2

Information classification

Information classification assigns information to defined protection levels based on its protection requirements and establishes binding labelling and handling rules so that every piece of information is protected in line with its value.

Information classification is a core building block of an information security management system (ISMS) and describes the systematic assignment of information to predefined protection levels. The basis is the protection requirement, which is derived from the classic security objectives of confidentiality, integrity and availability. Typical level schemes range, for example, from "public" through "internal" and "confidential" to "strictly confidential"; what matters is not the number of levels but that each level is clearly defined and reflects the potential damage that would result from a breach of the security objectives.

Classification is inseparable from labelling and handling rules. Labelling makes the assigned level visible to everyone involved, for instance through footers or headers in documents, metadata in files, or notices in emails. The handling rules specify, for each protection level, how information may be stored, transmitted, copied, retained and destroyed, including requirements for encryption, access control and transport channels. This ensures that the protection requirement, once established, is enforced consistently across the entire lifecycle of the information.

Information classification is firmly anchored in standards: ISO/IEC 27001 requires corresponding measures for classifying and labelling information in Annex A, the BSI IT-Grundschutz addresses it in the module on protection requirements, and frameworks such as the NIS2 Directive and TISAX indirectly call for appropriate measures to protect information according to its value. A well-maintained classification is also a prerequisite for effective asset management, risk-based selection of controls, and demonstrating the effectiveness of measures to auditors and supervisory authorities.

Legal Basis

ISO/IEC 27001 (Annex A, incl. A.5.12/A.5.13); BSI IT-Grundschutz; indirectly Art. 21 NIS2 Directive (Directive (EU) 2022/2555)

Practical Example

A mid-sized plant engineering company introduces a four-level classification scheme as part of its ISO/IEC 27001 certification. The information security officer defines labelling and handling rules for each level: engineering drawings are classified as "confidential", labelled accordingly in the document footer, sent only in encrypted form, and made accessible only to a defined group of people following the need-to-know principle. Employees receive brief training, and the classification is built into every new document template as a mandatory field, so that the protection requirement is set as soon as a document is created.

FAQ

In practice, three to four levels have proven effective, for example "public", "internal", "confidential" and "strictly confidential". More important than the number is that each level is clearly defined and backed by concrete labelling and handling rules. Too many levels are often not applied correctly in day-to-day work.
The protection needs assessment determines how high the protection requirement of a piece of information or asset is in terms of confidentiality, integrity and availability. Classification translates this result into a standardised protection level with associated labelling and handling rules. Classification therefore builds on the protection needs assessment.
Yes, ISO/IEC 27001 expects measures for classifying and labelling information in Annex A. If these measures are considered not applicable, this must be justified in the Statement of Applicability. In practice, a functioning classification is almost always required.

How preeco supports you

Learn how our software supports you with this topic.

Learn more