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.
HomeArticlesLeast Privilege and NIS2: Limiting Access to Essential Systems
Cryptography Access Assets Physical Security / 2026-10-10

Least Privilege and NIS2: Limiting Access to Essential Systems

Least privilege limits access to the systems, information and actions needed for authorised work. Under NIS2, this supports the access control policies included in Article 21(2)(i) and helps reduce damage from account compromise or human error.

Connect permissions to service risk

Identify critical systems and the functions staff, contractors and automated services need to perform. Access decisions should be based on specific duties, not job titles alone. For example, a technician who monitors equipment may not need permission to change its production configuration.

Article 21(2)(i) lists access control policies alongside human resources security and asset management. Its risk-based approach does not prescribe one identical entitlement model for all entities. Relevant national law and sector-specific rules should be considered.

Define roles and approve exceptions

Create role profiles with justified permissions, accountable owners and approvals. Separate normal user identities from privileged administration wherever practical. Emergency rights should have clear authorisation and be reviewed after use.

Time-limited permissions help prevent temporary project access from becoming permanent. When legacy software cannot support granular privileges, record the exposure and implement appropriate compensating protections.

Control access throughout the employment lifecycle

Coordinate identity management with joining, transfers, contractor renewals and departures. A worker promoted to a new function may need old permissions removed as well as new rights approved.

Check local accounts, remote access, cloud tenancy roles and supplier-administered identities. Central identity records may not capture every independently managed credential.

Test actual entitlement boundaries

Review samples of active permissions against approved roles and attempt carefully authorised tests of sensitive operations. Verify that rejected requests are logged appropriately and that unauthorised actions do not succeed.

An access review marked complete is weak evidence if the reviewer did not inspect actual entitlements. Record tested systems, uncovered exceptions, responsible owners and verified corrections.

Measure and report residual access risk

Track high-risk standing permissions, unused accounts, delayed access removal and exceptions lacking owners. Interpret figures in the context of the critical service affected rather than using a universal numeric target.

Escalate repeated failures and retest after remediation. Keep risk decisions and operational records secure because detailed entitlement maps can reveal sensitive system information.

Points of clarification

Does NIS2 prescribe a single technology for every entity?

No. Article 21 requires appropriate and proportionate measures, with national and relevant sector-specific rules also considered.

Is a written policy sufficient evidence?

No. Operational configuration, sampled testing, monitoring and verified remediation support effectiveness assessment.

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.