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.
HomeArticlesRole-Based Cybersecurity Training Under NIS2
Cyber Hygiene Training Human Security / 2026-10-10

Role-Based Cybersecurity Training Under NIS2

Role-based cybersecurity training prepares people for the security decisions attached to their duties. Under NIS2 Article 21(2)(g), training should support proportionate cybersecurity risk-management measures, with specialist learning for people who manage systems, suppliers, incidents or sensitive data.

Identify the decisions each role makes

A system administrator, purchasing manager and customer-support employee encounter different threats. Training needs should follow access privileges, service criticality, information handled and decisions that could change cybersecurity exposure. Generic awareness remains useful, but it cannot teach all specialised procedures.

Article 21(2)(g) covers basic cyber hygiene and cybersecurity training. Organisations should also consider Article 20 on management-body training and Article 21(2)(i) on human resources security and access controls. Member State implementing law and sector rules may add detail.

Map training to real operational tasks

Incident responders may need to classify reports, preserve evidence and follow escalation timelines. Procurement teams may need to challenge supplier security claims and escalate unacceptable exceptions. Developers may require instruction on secure dependency handling, code review and disclosure processes.

Define learning objectives that describe decisions or actions a participant must perform. A lesson explaining phishing risk is different from an exercise in safely verifying a supplier's request to change payment details.

Give privileged and critical roles practical exercises

People who administer identity platforms, production networks or critical cloud services need more than a slide presentation. Controlled labs, tabletop scenarios and supervised procedures can assess whether they can protect credentials, approve changes and restore services under pressure.

Coordinate exercises with service owners to prevent disruption. For fragile operational technology or safety-sensitive systems, use suitable simulations or test environments and record limitations.

Track competence and adjust after changes

Maintain a role-to-training matrix, delivery records and evidence of assessment. New hires should receive instruction before risky access is granted, while employees changing roles may need additional material before receiving new permissions.

An incident, failed test, material technology change or revised responsibility should trigger a review of competence. Do not equate course attendance with proof that people can perform the required security action.

Make governance and follow-up explicit

Assign responsibility for approving training content, identifying participants and resolving competence gaps. Management reporting should concentrate on roles with material uncovered risk, not only completion percentages.

Keep records proportionate, respect employee privacy and check national NIS2 requirements. Clear ownership and verification of corrective actions provide stronger evidence than an unchanged annual course calendar.

Points of clarification

Does NIS2 mandate one course for every employee?

NIS2 does not prescribe a universal course. Training should reflect relevant roles and risks and be checked against applicable national and sector-specific requirements.

Does employee training replace technical controls?

No. Training supports cybersecurity risk management, while organisations must also select and maintain proportionate technical and organisational safeguards.

What evidence should be kept?

Relevant role mapping, training objectives, completion records, practical assessments, identified gaps and corrective actions can support oversight.

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.