An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesInformation Classification Under NIS2
Cryptography Access Assets Physical Security / 2026-10-10

Information Classification Under NIS2

Information classification helps organisations determine which data and records need stronger access, handling, protection and recovery measures. NIS2 does not prescribe one universal classification scheme, but Article 21 requires risk-based cybersecurity measures, including asset management and access control policies.

Start with the information supporting critical services

Identify the records, configuration information, credentials and operational data necessary to deliver the organisation's services. Consider confidentiality, integrity and availability separately. A public maintenance schedule may be low in confidentiality but operationally critical if unauthorised changes could disrupt a service.

Article 21(2)(i) includes asset management and access control policies, while Article 21(2)(h) addresses cryptography and encryption where appropriate. Classification provides an operational basis for choosing safeguards under those provisions.

Define categories that lead to decisions

Use a small set of understandable categories with written criteria, examples and clear owners. An overly complicated scheme that workers cannot apply consistently will not reliably influence system configuration or information handling.

Describe what each classification means for storage, sharing, access approval, encryption, retention and disposal. Ensure classifications are reviewed when data is combined or transferred into a new system.

Account for integrity and availability

Confidentiality is only one dimension of information security. System configurations, monitoring records and recovery documentation may require high integrity even where disclosure would cause limited harm. Operational data needed to restore services may require reliable availability.

Link classification to asset ownership and business continuity arrangements so safeguards address these different consequences rather than treating all high-value information alike.

Apply labels throughout information flows

Record where important information is created, copied, processed and exchanged with suppliers. Include exports, cloud backups, messaging tools and development environments where sensitive records might persist after a project ends.

Provide approved tools and workable guidance. If staff must manually label every transient file without automation or clear purpose, the process may create inconsistent results and encourage workarounds.

Verify outcomes and review exceptions

Sample information repositories and access permissions against approved classification decisions. Review whether encryption, recovery and retention controls match the assigned sensitivity and whether suppliers handle information as agreed.

Document missing classifications, exceptions, remediation and rechecks. Applicable national and sector-specific rules may introduce additional obligations, so distinguish those from the organisation's own policy thresholds.

Points of clarification

Does NIS2 prescribe one identical procedure for every organisation?

No. Appropriate measures depend on the services, risks, Member State law and any applicable sector-specific requirements.

Are written policies enough to demonstrate controls are effective?

No. Evidence should include implementation, relevant assessment results, identified weaknesses and verified corrective actions.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.