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.
HomeArticlesBasic Cyber Hygiene Under NIS2: Everyday Security Practices
Cyber Hygiene Training Human Security / 2026-10-09

Basic Cyber Hygiene Under NIS2: Everyday Security Practices

Basic cyber hygiene under NIS2 concerns routine measures that reduce preventable cybersecurity exposure, such as secure authentication, maintained systems, safe device use and prompt reporting of suspicious activity. Article 21(2)(g) identifies basic cyber hygiene practices alongside cybersecurity training.

What basic cyber hygiene means in practice

The NIS2 Directive includes basic cyber hygiene practices as a minimum measure category, without presenting a single device-level checklist suitable for every entity. Organisations need to translate the requirement into actions relevant to their systems, workforce and services.

For example, a business operating remote-access systems might prioritise strong authentication, managed endpoints, session protections and guidance for staff connecting from outside its premises. An industrial operator may need additional safeguards where ordinary patching or active scanning could disrupt production.

Reduce avoidable account and device exposure

Ensure staff use approved authentication methods and report lost credentials or devices without delay. Apply updates through a managed process, remove unsupported applications where feasible and restrict administrative rights to authorised activities.

Human behaviour cannot compensate for missing technical safeguards. Organisations should combine guidance with identity controls, centralised device management and monitoring suited to the risk. Record cases where legacy technology limits implementation and document alternative controls.

Make reporting easy and useful

Employees should know where to send suspected phishing messages, unusual login prompts and lost-device reports. A reporting route that is hard to find or punishes early mistakes can delay detection.

Give responders a clear method for triage and escalation. After incidents, examine whether staff received understandable instructions and whether technical alerts reached the correct team. Revise the reporting process when evidence shows gaps.

Extend hygiene to suppliers and remote work

A supplier with privileged remote access can create exposure even if internal employees follow the rules. Set expectations for approved devices, account ownership, logging and offboarding in proportion to the service's importance.

Remote and hybrid work also require appropriate rules for handling confidential records, using public networks and storing information. Provide workable approved alternatives so that staff do not need informal workarounds to complete routine tasks.

Demonstrate that practices are operating

Evidence may include device management coverage, access review records, policy acknowledgements, training results, incident simulations and corrective actions. No single attendance percentage proves that cyber hygiene is effective.

Check the applicable Member State implementing law before labelling internal practices as statutory minimums. Review practices when risks, systems or working arrangements materially change.

Points of clarification

Does NIS2 require exactly the same training course for all employees?

No. Training should reflect roles, risks, services and applicable national requirements. Specialised personnel and management bodies may need distinct content.

Is attendance enough to show training works?

No. Attendance is useful evidence of delivery, but scenario exercises, reporting outcomes and assessment of behaviour can reveal whether the programme is effective.

Do organisations need to check national NIS2 legislation?

Yes. NIS2 is a Directive implemented through Member State legislation; the applicable national law and competent-authority guidance should be reviewed.

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.