These are the 8 trainings your employees need to comply with NIS2:
- Management body training
- Baseline cyber hygiene for all staff
- Phishing and social engineering awareness
- Incident detection and internal reporting
- Role-based training for high-risk functions
- Technical team readiness
- Supply chain and third-party security
- Data protection and secure information handling
Under NIS2, members of management bodies must follow cybersecurity training, and every in-scope organisation must include basic cyber hygiene and cybersecurity training for its staff among its risk-management measures. In practice, that means a recurring, documented and role-based programme: awareness for all employees, deeper operational training for technical teams and high-risk functions, governance training for management, and evidence that all of it works.
Most serious cybersecurity incidents are not caused by complex technical failures but by human error: a click on a phishing link, a weak password, a poorly protected device or a file shared over an insecure channel. The NIS2 Directive turns that reality into a governance requirement: resilience is organisational as well as technical. This guide explains each of the eight trainings, how often to run them, how they map to ISO 27001 and the GDPR, and what evidence you need to keep.
The 8 trainings your employees need to comply with NIS2
One of the most common compliance failures is delivering the same generic course to the whole workforce. NIS2 calls for a risk-proportionate approach, so each training below targets a specific audience and risk. Together they cover what Articles 20 and 21 expect and what an auditor or authority will ask to see.
1. Management body training
Management training is the only training NIS2 explicitly makes mandatory, and it is the first thing to put in place. Under NIS2, management cannot “delegate away” responsibility: the people who approve the cybersecurity measures must understand the risks well enough to challenge them, fund them and oversee them.
What to cover
- Governance duties: oversight, accountability, personal liability and decision-making under risk.
- Risk management: how to read a risk register, assess impact and prioritise mitigations and budget.
- Incident reporting: the NIS2 timeline of an early warning within 24 hours, an incident notification within 72 hours and a final report within one month.
- Supply chain risk: which critical suppliers the organisation depends on and what assurance it holds from them.
A format that works well is an annual workshop of two to three hours plus a tabletop exercise in which the management team takes the decisions of a realistic incident: whether to notify, what to tell customers and how to restore services. Keep the agenda, attendance and materials for each session, because management training that cannot be evidenced will be treated as not having happened. This training is also the anchor of a credible plan to meet NIS2 compliance requirements, since every other measure depends on management oversight.
2. Baseline cyber hygiene for all staff
Article 21(2)(g) names basic cyber hygiene explicitly, and it is the foundation every other training builds on. It applies to everyone with access to the organisation’s systems or data, from new joiners to senior staff.
What to cover
- Passwords and authentication: password managers, MFA and why credentials must never be shared.
- Devices: screen locking, updates, encryption and what to do if a laptop or phone is lost.
- Safe working habits: public Wi-Fi, remote working, removable media and clear screens.
- Acceptable use: what the organisation’s policies allow and where to find them.
Short modules of 15 to 30 minutes with realistic examples work better than long lectures, and they are easier to repeat at onboarding and in the annual refresh. Rather than running it as an isolated IT initiative, fold it into the existing corporate training plan, which gives it an owner, a calendar and a budget.
3. Phishing and social engineering awareness
Phishing remains one of the most common entry points for incidents, and attacks are becoming harder to spot. Awareness training must go beyond “do not click suspicious links” and reflect the techniques employees actually face.
What to cover
- Real examples of phishing emails, SMS and messaging attacks relevant to your sector.
- MFA fatigue attacks, QR-code phishing and fake login pages.
- Impersonation of executives or suppliers, including deepfake voice calls.
- “Stop and verify” habits and how to report a suspicious message in one click.
Pair the training with regular phishing simulations and measure two numbers: the click rate and the reporting rate. A falling click rate is good, but a rising reporting rate is often the better signal, because it shows employees are acting as an early warning system rather than simply avoiding mistakes.
4. Incident detection and internal reporting
NIS2’s reporting deadlines start when the entity becomes aware of a significant incident. If employees do not know how to recognise and report an incident internally, the 24-hour early warning becomes impossible to meet, however good the incident response plan is on paper.
What to cover
- What counts as a security event or incident in everyday terms.
- Exactly how and to whom to report, including outside working hours.
- What to preserve and what not to touch, such as emails, devices and logs.
- Why speed matters, with the NIS2 and GDPR deadlines explained simply.
The goal is that every employee can answer three questions with confidence: what is suspicious, how do I report it, and what must I not do? When personal data is involved, the same reporting route should trigger the GDPR breach process, and a tested data breach response template makes this training concrete.
5. Role-based training for high-risk functions
Some non-technical teams are targeted more often or handle more sensitive information, and generic awareness is not enough for them. Anchoring training to their daily tasks makes it relevant and memorable.
What to cover by function
- Finance: verifying changes to supplier bank details through a second channel and recognising invoice and payment fraud.
- HR: handling employee data, secure document sharing, offboarding checklists and avoiding informal channels for sensitive files.
- Sales: receiving external files, urgent “CEO requests”, approved tools for proposals and preventing account takeover on email and CRM.
- Customer Support: identity verification scripts, secure resets, avoiding over-disclosure and detecting suspicious customer requests.
These sessions can be short, but they should use scenarios drawn from the team’s own tools and processes. Auditors frequently interview staff from these departments, so it pays when they can explain their part of the security programme in their own words.
6. Technical team readiness
Technical teams operate most of the controls that NIS2 Article 21 lists, so their training needs to be deeper and more practical. The aim is not certification of individuals but demonstrable ability to run controls and respond to incidents.
What to cover
- Incident response: detection, escalation paths, evidence preservation and communication.
- Access control: MFA enforcement, privileged access and the account lifecycle.
- Monitoring and hardening: logging, alerting, patching and configuration baselines, including cloud IAM and secrets.
- Backup and recovery: restore testing and disaster recovery plans.
- Secure development: secure coding, dependency management and secrets handling for teams that build software.
Include “muscle memory” exercises: incident simulations for ransomware, data leaks or supplier compromise; runbook walkthroughs that practise rotating credentials and isolating workloads; and reporting drills that gather the information needed for the 24-hour early warning. Role-specific competence is also what ISO 27001 auditors check, so the same records support ISO 27001 employee training requirements.
7. Supply chain and third-party security
NIS2 Article 21(2)(d) requires supply chain security, and Implementing Regulation 2024/2690 explicitly extends awareness expectations to direct suppliers and service providers. Training here has two audiences: the contractors and outsourced teams who access your systems, and the internal staff who select and manage suppliers.
What to cover
- The same baseline onboarding module for contractors with system access as for employees.
- Security awareness requirements written into contracts with providers that access systems or data.
- For procurement and supplier owners: how to assess a supplier’s security, what evidence to request and when to escalate.
Asking critical suppliers for evidence of their own training programme during due diligence closes the loop. These checks fit naturally into a vendor compliance management process, so the evidence is reviewed periodically rather than only at onboarding.
8. Data protection and secure information handling
NIS2 and the GDPR overlap whenever incidents involve personal data, and most organisations run one programme for both. The GDPR does not define a single syllabus, but it requires accountability (Article 5(2)), that people acting under the organisation’s authority process personal data only on instructions (Article 32(4)), and it makes staff awareness and training one of the Data Protection Officer’s tasks (Article 39(1)(b)).
What to cover
- Recognising personal and confidential data, and the basics of information classification.
- Secure sharing, approved tools and least-privilege habits.
- AI tools and shadow IT: which tools are approved and what must never be pasted into public AI services or personal accounts.
- How to route data subject requests, and what counts as a personal data breach.
Privacy training is one of the first things reviewed in a GDPR audit, so the same evidence structure applies: plan, attendance, materials and results.
“With NIS2, security is no longer just an IT matter: every employee contributes to operational resilience.”
What NIS2 requires on training (Articles 20 and 21)
NIS2 places responsibility at the top, but its training expectations reach the whole organisation. The obligations come from two articles of Directive (EU) 2022/2555, and it helps to read them separately.
Mandatory training and accountability for management bodies
Under Article 20(1), the management bodies of essential and important entities must approve the cybersecurity risk-management measures, oversee their implementation and can be held liable for infringements. Article 20(2) goes further: members of management bodies are required to follow training so they have enough knowledge and skills to identify risks and assess risk-management practices and their impact on the services the entity provides.
This is not a symbolic requirement. For essential entities, Article 32 allows authorities, as a last resort, to temporarily prohibit a person with managerial responsibilities from exercising those functions. Fines for infringing Article 21 can reach €10 million or 2% of worldwide annual turnover for essential entities, and €7 million or 1.4% for important entities, whichever is higher.
Cyber hygiene and training for all staff as a risk-management measure
For the wider workforce, Article 20(2) states that Member States shall encourage entities to offer similar training to their employees on a regular basis. The firmer obligation sits in Article 21(2)(g), which lists “basic cyber hygiene practices and cybersecurity training” among the minimum measures every in-scope entity must implement, in a way that is appropriate and proportionate to its risks, size and sector.
The result is that employee training is not optional in practice. It is one of the measures an authority will check, and the burden is on the organisation to show that its audience, content and frequency fit its risk profile.
Digital providers and national rules
For some sectors, the expectations are more detailed. Section 8 of the Annex to Implementing Regulation (EU) 2024/2690 sets out awareness and training requirements for DNS providers, TLD registries, cloud and data centre providers, content delivery networks, managed (security) service providers, online marketplaces, search engines, social networks and trust service providers. It expects a repeated awareness programme that covers management and new joiners, effectiveness testing at planned intervals, and specific training for roles that require security skills. Even outside these sectors, it is a useful benchmark for a mature programme.
Because NIS2 is a directive, the exact rules also depend on each Member State’s implementing law. Spain’s draft Cybersecurity Coordination and Governance Act was approved by the Council of Ministers in January 2025 but was still going through Parliament in 2026, so following NIS2 transposition in Spain matters before you fix your programme’s cadence. At EU level, targeted amendments to NIS2 proposed in January 2026 focus on scope, size thresholds and incident reporting; they do not remove the core training and governance duties.
How PrivaLex can help employees comply with NIS2
PrivaLex Partners helps organisations build NIS2 training programmes that also cover GDPR and ISO 27001, and that hold up when an authority or auditor asks for evidence. We work with internal teams rather than replacing them: we bring the regulatory interpretation, the content and the documentation, and your people keep ownership of a programme they can run themselves.
Assess your training gaps
We start by establishing what the law requires of you and what you already have. That avoids building a programme that is too heavy for an important entity or too light for an essential one. We check whether you are an essential or important entity, which national law applies and whether Implementing Regulation 2024/2690 covers your sector.
We then review existing courses, onboarding materials, LMS records, phishing simulations and past management sessions, and talk briefly to HR, IT, security and management to see how incidents are reported in practice. The output is a gap report with a prioritised roadmap, so you know which of the eight trainings to fix first and what can wait.
Design a role-based programme
We turn the gap report into a programme built around your roles, tools and risks rather than a generic course catalogue. That includes a competence matrix showing which roles need which trainings, at what depth and how often, and modules for each audience: all staff, high-risk functions, technical teams, management and contractors.
Exercises are based on your own suppliers, SaaS tools and incident history, so employees recognise what they will actually face. The programme is mapped once to NIS2, ISO 27001 (clauses 7.2 and 7.3 and Annex A control 6.3) and the GDPR, so each session counts towards all three.
Deliver live, online or blended training
Delivery adapts to each audience. Management workshops cover governance duties, liability and reporting timelines, and include a tabletop exercise based on a realistic incident. Technical sessions focus on incident response drills, runbook walkthroughs and practice for the 24-hour early warning.
Staff modules are short sessions of 15 to 30 minutes, live or online, with practical examples for each department. Training can be delivered on-site in Spain or remotely, in English or Spanish.
Document an audit-ready evidence pack
Every activity produces the records an auditor or authority will ask for, organised so they are easy to find and update: an annual training plan and competence matrix, attendance and completion templates that connect to your LMS exports, and assessment templates for quizzes, phishing simulations and tabletop exercises.
We also prepare a management review template to record what leadership reviewed and decided, and a requirements map linking each record to NIS2 Articles 20 and 21(2)(g), ISO 27001 and the GDPR.
Maintain updates, KPIs and management reporting
A programme that is not updated loses value quickly, and authorities look for proof that it evolves with your risks. We run quarterly micro-training on current threats and update content after incidents, near-misses, new systems or changes in national law, including the final Spanish NIS2 transposition.
A KPI dashboard covers completion, phishing click and reporting rates, and time-to-report, and an annual report documents management’s oversight of the programme.
Funding training in Spain
If you operate in Spain, part of the cost can often be covered with FUNDAE training credits, the state system that lets companies recover training costs through reductions in their social security contributions. We help you check eligibility and prepare the documentation, so compliance training does not have to come entirely out of the security budget.
The result is a programme a small internal team can sustain: clear scope and cadence, an evidence pack that is easy to update, short modules focused on behaviour change, and a reporting layer that lets management demonstrate its oversight.
How often should NIS2 training take place?
NIS2 does not set a fixed frequency, and national laws may add their own expectations. The right cadence depends on roles, threats, operational changes and training results. A practical risk-based model that many organisations adapt looks like this:
- Onboarding: baseline training within the first two weeks, before access to sensitive systems where possible.
- Annual refresh: a baseline update for the whole company, plus the annual management workshop.
- Quarterly micro-training: short sessions tied to current threats such as phishing, MFA fatigue, supplier scams or deepfake voice fraud.
- Post-incident learning: a short update after relevant incidents or near-misses.
- Role change: specific training when someone moves into a role with privileged access or security responsibilities.
A single annual awareness session is rarely enough where responsibilities, threats or systems change frequently. Combining onboarding, an annual baseline and targeted micro-training keeps knowledge current without overloading teams, and the results of each round should shape the content of the next.
How the 8 trainings map to ISO 27001 and the GDPR
Even if your starting point is NIS2, most organisations need training that also supports ISO 27001 audits and GDPR accountability. NIS2 focuses on cyber resilience and governance, ISO 27001 on competence and information security awareness, and the GDPR on responsible handling of personal data. A combined training checklist lets one programme cover all three without duplicating sessions.
ISO 27001
ISO 27001 requires that people doing work under the organisation’s control are competent (clause 7.2) and aware of the information security policy, their contribution to the ISMS and the consequences of non-compliance (clause 7.3). Annex A control 6.3 adds ongoing awareness, education and training. Trainings 2, 3, 4 and 6 above cover most of what an ISO 27001 auditor expects, provided they are backed by a competence matrix and records.
If you are also working towards ISO 27001 certification, building the competence matrix early saves time before the Stage 1 audit, because the same evidence serves both frameworks.
GDPR
Training 8 carries most of the GDPR weight, supported by training 4 for breach reporting and training 5 for teams that handle personal data daily, such as HR and Support. Together they help demonstrate accountability and reduce the human errors behind many personal data breaches.
Where a Data Protection Officer is appointed, involve them in the content and keep a record of their review, since awareness-raising and staff training are part of the DPO’s tasks under the GDPR.
What auditors expect and how to prove your staff are trained
NIS2 is not a certification like ISO 27001, but supervision is similar in one key respect: you must be able to provide evidence. Essential entities can face proactive supervision, including on-site inspections and audits, while important entities are mainly supervised after the fact, for example following an incident. Either way, it pays to prepare for a NIS2 audit before it is announced.
What auditors look for
Auditors and authorities typically look for a training plan with scope, audiences, frequency and owners; proof it was delivered through attendance records and completion logs; proof it works through evaluations, simulations or metrics; proof it is maintained through onboarding and refreshers; and proof of management involvement through training records and evidence that leadership reviews the programme.
They also sample reality. They interview employees from different departments about where they would report phishing or an incident, ask for records from a specific month rather than “your best deck”, ask how training changes when new risks appear, and ask a manager to explain how the board oversees cyber risk.
Build an evidence pack
Knowing how to prove staff are trained is what turns a defined programme into one an auditor accepts. A solid evidence pack includes the annual plan and schedule, attendance lists or LMS exports, dated training materials, assessment results from quizzes, simulations and tabletop exercises, onboarding evidence for new joiners and third parties, and management training records with review minutes.
To keep it manageable, store evidence in a consistent structure, such as separate folders for the plan, materials, records by year, assessments by year, onboarding and management sessions. Add a record of exceptions and catch-up sessions for people who miss training, and a small set of KPIs: completion rate, phishing click rate, reporting rate and time-to-report.
“In compliance, what is not documented is treated as if it did not exist.”
“We trained people” without attendance, materials or evaluation results will not stand up to review. Building demonstrable compliance means every session produces a log, dated materials and an assessment result, and that completion figures are read alongside behaviour metrics rather than instead of them.
Conclusion
NIS2 makes training a legal and governance matter. Management bodies must be trained and remain accountable, and cyber hygiene and cybersecurity training are part of the risk-management measures every in-scope entity must implement. The eight trainings in this guide turn those obligations into a programme: governance training for management, baseline hygiene, phishing awareness and incident reporting for everyone, targeted sessions for high-risk functions and technical teams, and coverage of suppliers and personal data.
The programmes that hold up in front of an authority share three traits: they are role-based, they are recurring and they are backed by evidence that shows they change behaviour. That evidence also serves ISO 27001 and GDPR audits, so one well-designed programme covers several obligations at once.
The practical priorities are to confirm which national rules apply to you, train management first, put baseline hygiene and incident-reporting training in place for all staff, and organise the evidence before anyone asks for it. A 10-point NIS2 self-assessment is a quick way to see where training sits among your other gaps, and if your programme is missing or you cannot prove it, schedule a strategic session with PrivaLex to define the minimum training and an evidence pack you can defend.
Frequently Asked Questions (FAQs)
Article 20 expressly requires training for members of management bodies. For the wider workforce, cybersecurity training and basic cyber hygiene form part of the Article 21 risk-management measures. The appropriate audience, content and frequency should be determined according to the organisation’s risks, sector and applicable national implementation rules.
It means management bodies are expected to oversee cybersecurity measures and to have sufficient training to understand risks and responsibilities. It is part of demonstrating governance, not just operational security.
Auditors typically expect evidence that staff are competent for their role and aware of security policies and procedures, plus recurring awareness activities.
In practice: a training plan, attendance/completions and some form of evaluation.
The GDPR does not define a single mandatory course, but it does require that personal data is processed correctly and that organisations can demonstrate compliance. Training is one of the most practical ways to reduce human error and demonstrate accountability.
Keep at least a training plan, attendance or completion records, materials and evaluation results, plus onboarding evidence for new joiners. This is what auditors and authorities rely on.
Yes, and it is usually the best approach.
A single role-based programme can cover overlapping requirements (awareness, competence, documentation) while keeping workload and evidence management under control.
