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.
HomeArticlesPassword Security Under NIS2: Policy, Authentication and Account Protection
Cyber Hygiene Training Human Security / 2026-10-09

Password Security Under NIS2: Policy, Authentication and Account Protection

NIS2 does not prescribe one identical password length or rotation schedule for all organisations. Password practices form part of proportionate cybersecurity risk management and should be paired with strong authentication, account protection and controlled recovery procedures.

Connect password policy to identity risk

Weak, reused and exposed credentials can enable access to corporate accounts. Determine which systems still depend on passwords, which identities have elevated privileges and how authentication failures might disrupt important services.

Article 21(2)(j) refers to the use of multifactor authentication or continuous authentication solutions where appropriate, alongside secure communications. Article 21(2)(g) covers cyber hygiene and training. These provisions should be read together with national implementing rules rather than treated as a fixed EU password recipe.

Prefer strong and unique credentials

Require passwords or passphrases that are difficult to guess and discourage reuse across systems. Screen new passwords against known compromised values where technically feasible, and provide an approved password manager for generating and storing unique credentials.

Avoid practices that routinely push workers toward predictable substitutions or written lists. Changes following suspected compromise are essential, while arbitrary frequent rotation without evidence of risk can create unnecessary burden and unsafe workarounds.

Protect account recovery and privileged identities

Account recovery can bypass otherwise strong authentication. Verify identity through a trusted procedure, restrict who can reset high-risk accounts and record unusual requests. Remove default passwords and protect administrative, service and emergency-access credentials using appropriate controls.

Use safeguards against automated guessing, monitor suspicious sign-ins and review dormant accounts. Noninteractive identities require their own lifecycle, ownership and secure secret storage rather than relying on employee training.

Combine passwords with stronger authentication

Passwords alone may be phished. Select suitable multifactor or phishing-resistant authentication methods for exposed and privileged systems, taking account of accessibility, service continuity and recovery arrangements.

Training should explain fraudulent approval prompts, unfamiliar sign-in requests and safe handling of recovery codes. Employees should know when to stop an authentication attempt and how to report it.

Test the policy in operation

Evidence may include authentication settings, screening results, password-manager adoption where relevant, access reviews and records of compromised credential response. Examine whether the policy is enforced on systems in scope rather than relying solely on signed acknowledgements.

Review exceptions for legacy systems and document compensating controls. Check current national or sector-specific requirements before claiming a particular numeric password threshold is required by NIS2.

Points of clarification

Does NIS2 specify the same training schedule for every organisation?

No universal schedule is set for every entity by Article 21 alone. Assess applicable national rules and the organisation's risks.

Can training replace technical protection?

No. Training complements technical and organisational controls and cannot by itself establish that the related security measure is effective.

What evidence is useful?

Keep relevant policy, training, technical implementation, assessment and corrective-action records, with appropriate access controls.

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.