Make responsibilities concrete and achievable
A security policy should explain what personnel are expected to do while using devices, sharing files, responding to unexpected requests and reporting incidents. Instructions need to reflect daily work rather than a generic requirement to act securely.
NIS2 Article 21(2)(g) includes cyber hygiene and cybersecurity training, while Article 21(2)(i) includes human resources security and access control policies. These provisions do not transfer an entity's legal duties wholesale to individual employees.
Protect accounts and organisational information
Employees should use approved authentication methods, keep secrets out of unsecured channels and report lost devices or suspected credential exposure. Appropriate training should explain how sensitive records are labelled, stored and transmitted in the organisation.
Give staff usable approved tools and access to support. When legitimate work requires insecure workarounds, management and system owners need to address the underlying design rather than relying on reminders.
Report suspicious activity without delay
Personnel should know how to raise concerns about phishing, unusual sign-in prompts, unexpected software, misplaced information or service disruption. Clear routes for both normal hours and emergencies are necessary where services operate continuously.
A useful reporting process acknowledges the message and tells the reporter what to do next. Encouraging early reports, including uncertain ones, can help security teams investigate before an event spreads.
Understand responsibility during role changes
Access should be granted for authorised duties and adjusted when those duties change. Employees should not lend privileged accounts or continue using permissions no longer required. Contractors and temporary personnel need similarly clear expectations.
Managers, HR and system owners must coordinate onboarding, transfer and departure workflows. The design and operation of access controls remain organisational responsibilities.
Use incidents and exercises to improve guidance
Scenario practice can reveal whether instructions are understandable, especially for teams working shifts or outside traditional offices. Review reporting outcomes, repeated errors and technical evidence to identify where additional training or process changes are needed.
Avoid punitive practices that discourage reporting or intrusive measurement unrelated to risk. Record important findings, corrective action and follow-up. Review applicable Member State law when defining formal duties and evidence expectations.
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.