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.
HomeArticlesTechnical and Organisational Security Controls Under NIS2
Cryptography Access Assets Physical Security / 2026-10-10

Technical and Organisational Security Controls Under NIS2

NIS2 requires covered essential and important entities to adopt appropriate and proportionate technical, operational and organisational cybersecurity risk-management measures. Article 21 includes cryptography, access control and asset management alongside other control areas. Selection and evidence should reflect the risks to the services and systems in scope.

Start with the systems and services being protected

Article 21(1) of Directive (EU) 2022/2555 requires appropriate and proportionate measures to manage risks to the security of network and information systems used in operations or service provision. Its all-hazards approach covers technical, operational and organisational exposures, including the physical environment. A control catalogue alone is therefore not an adequate risk assessment.

Identify the legal entity, its regulated services, critical systems, information assets and important dependencies. Record the risks that could compromise availability, confidentiality, integrity or authenticity. Consider supplier access, remote administration and physical sites, as well as ordinary IT assets.

Decide which controls are proportionate

Article 21(2)(h) addresses policies and procedures regarding cryptography and, where appropriate, encryption. Point (i) covers human resources security, access control policies and asset management. Controls in these areas should be linked to the sensitivity of assets and the consequences of compromise.

Proportionality does not mean choosing measures based only on budget. Consider exposure to threats, business criticality, the likelihood and severity of incidents, organisation size and the state of the art. A privileged administrative interface used to control a critical service warrants closer scrutiny than a low-risk test environment.

Set a cryptography policy that can be implemented

Identify information and systems requiring cryptographic protection, then document approved approaches for data stored on devices, in applications and across communications links. The policy should cover algorithm selection, key ownership, access to keys, certificate management and the procedure for responding to compromise.

Encryption protects some aspects of data security but does not automatically prevent unauthorised use by a person with legitimate access. Pair cryptographic safeguards with identity controls, logging and recovery plans. Record justified exceptions for systems that cannot support modern configurations.

Link identities, roles and permissions to risks

Determine who needs access to a service, for what purpose and for how long. Apply controlled provisioning, privileged-access safeguards, review of dormant accounts and removal of permissions after role changes or departures. Suppliers with administrative connections should be included in these workflows.

The relevant evidence should show that access rules operate in real systems. A written least-privilege policy is weaker evidence than a verified sample of granted rights, approval records and completed access removal.

Keep assets visible and protect their physical environment

An asset inventory should connect devices, applications, cloud resources, information stores and facilities with owners and critical services. Classification helps identify where stronger cryptography, authentication or monitoring is justified.

Physical and environmental controls should address risks such as unauthorised entry, power disruption, fire and equipment loss where they affect the security of systems. Review how facilities, remote sites and third-party data centres support service continuity.

Measure effectiveness and keep evidence of improvement

Article 21(2)(f) calls for policies and procedures assessing effectiveness. Test selected safeguards through restoration exercises, access reviews, configuration inspections, certificate checks and appropriately authorised technical assessments. Record observed failures and verify that corrective actions work.

NIS2 is implemented through Member State law. Commission Implementing Regulation (EU) 2024/2690 adds detailed requirements for specified digital and ICT provider categories, with supporting ENISA guidance. Establish which instruments apply before treating a particular configuration or document as universally mandatory.

Points of clarification

Does NIS2 prescribe the same technical controls for every entity?

No. Article 21 sets a common risk-based framework and minimum measure areas; national and applicable sector-specific requirements may supply additional detail.

Is encryption alone enough for NIS2 compliance?

No. Cryptography is one element of the wider risk-management measures, including access control, incident handling, continuity and the assessment of effectiveness.

How can an organisation demonstrate that controls work?

Maintain risk decisions, policies, system-level evidence, test findings, accountable corrective actions and repeat verification.

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.