17 November 2026 • NIS2
In brief: The NIS2 duty of care is the obligation for essential and important entities to manage the cybersecurity risks to the systems they depend on. Article 21 of the NIS2 Directive asks for appropriate and proportionate technical, operational and organisational measures and lists ten areas you have to cover at a minimum: from risk analysis and incident handling to supply chain security, cyber hygiene and training, and multi-factor authentication. How far you go depends on your risks and your size. Article 20 adds a separate duty for the board: approve the measures, oversee their implementation and follow training. A supervisor will not ask whether you have a policy, but whether you can show that it works.
What the NIS2 duty of care requires
The duty of care sits in Article 21(1) of the NIS2 Directive. Essential and important entities must take appropriate and proportionate measures to manage the risks to the security of their network and information systems, and to prevent or minimise the impact of incidents on the people who use their services.
Three words in that article do most of the work.
- Appropriate: the level of security has to match the risk, taking into account the state of the art, the cost of implementation and, where relevant, European and international standards.
- Proportionate: you weigh how exposed you are, how large the organisation is, how likely incidents are and how severe they would be, including their societal and economic impact.
- All-hazards: the measures protect systems and their physical environment against every kind of incident. A fire in the server room counts as much as ransomware.
This is a real change from the first NIS Directive, which only applied to a much smaller group of operators and left the content of the measures largely open. Our article on the difference between NIS1 and NIS2 explains what else changed. Whether your organisation falls under the law at all, and as an essential or an important entity, is covered in our NIS2 guide. This article assumes you are in scope and asks the next question: what do you actually have to do?
The ten minimum measures: a duty of care checklist
Article 21(2) lists ten areas that the measures must cover at a minimum. The table below sets out what each one means in practice and what evidence you can show when a supervisor asks. The wording in the first column follows the directive.
| Measure (Art. 21(2)) | What it means in practice | Evidence you can show |
|---|---|---|
| (a) Policies on risk analysis and information system security | Know which systems and data matter most, which threats apply and which risks you accept. Write down your security policy and who is responsible for what. | Approved security policy, risk analysis with a date and an owner, risk register |
| (b) Incident handling | Agree in advance how you detect, assess and contain an incident, who decides and who you call for outside help. | Incident response plan, contact list, log of past incidents and how they were handled |
| (c) Business continuity, backup management, disaster recovery and crisis management | Assume systems will fail. Make backups that an attacker cannot reach, test the restore and practise a crisis with the people who would lead it. | Continuity and recovery plans, restore test results, report of a crisis exercise |
| (d) Supply chain security | Map your direct suppliers and service providers, assess the risk each one brings and lay down security requirements in contracts. | Supplier list with risk classification, security clauses in contracts, supplier assessments |
| (e) Security in acquisition, development and maintenance, including vulnerability handling and disclosure | Patch on time, harden configurations, build security into purchases and development, and give outsiders a way to report vulnerabilities. | Patch and vulnerability management records, hardening baselines, a published reporting address |
| (f) Policies and procedures to assess the effectiveness of measures | Check periodically, for example once a year, whether the measures work in practice. Decide who does it and how. | Annual review or audit report, test results, decisions taken on the findings |
| (g) Basic cyber hygiene practices and cybersecurity training | Everyone knows the risks that are relevant to their work and applies the basics. People with security roles get regular, deeper training. | Training plan, participation and results per department, baseline and follow-up measurements |
| (h) Policies and procedures on cryptography and, where appropriate, encryption | Decide where encryption is used, which types, who implements it and who manages the keys. | Cryptography policy with a review date, key management procedure |
| (i) Human resources security, access control policies and asset management | Keep an up-to-date list of assets, give people only the access their role needs, revoke it when they leave and screen staff in sensitive roles where necessary. | Asset inventory, periodic access reviews, joiner, mover and leaver procedure |
| (j) Multi-factor or continuous authentication, secured voice, video and text communication and secured emergency communication, where appropriate | Use MFA, and preferably passkeys, at least for accounts that can be reached from the internet, administrator accounts and accounts on critical systems. Arrange a way to communicate if email and chat are down. | MFA coverage overview, list of exceptions with a reason, emergency communication plan |
The list is a minimum, not a ceiling. If your risk analysis shows that something else matters more, such as physical access to a site, the duty of care covers that too. And the reverse also holds: proportionate means a hospital and a 60-person logistics company will not reach the same depth on every row.
The board’s duty under Article 20
NIS2 does not let the board delegate cybersecurity to the IT department and leave it there. Article 20 gives the management body three duties of its own.
Approve the measures
The management body approves the risk-management measures the organisation takes under Article 21. That is more than a signature under a policy document. Approving means the board has seen the risk analysis, understands which risks are accepted and has chosen the measures and the budget that go with them. Put it on the agenda, minute the decision and repeat it when the risks change.
Oversee the implementation
After approval, the board has to follow whether the measures are carried out and whether they work. In practice this means a fixed moment on the agenda, a short report with a few indicators that do not change every quarter, and the reviews from measure (f). A board that only hears about security after an incident has not overseen anything.
Follow training
Article 20(2) requires members of the management body to follow training, so that they gain enough knowledge and skills to identify risks and assess cybersecurity risk-management practices and their impact on the services the entity provides. The same article encourages organisations to offer similar training to their employees on a regular basis. National laws can add details, such as the content of the training, a deadline or proof of participation.
Liability and sanctions
Article 20(1) states that management bodies can be held liable for infringements of Article 21 by the entity. How that works depends on national law. For essential entities, NIS2 also allows authorities as a last resort to temporarily bar a person at CEO or legal representative level from managerial functions (Article 32(5)). The organisation itself faces maximum fines of at least 10 million euros or 2% of worldwide annual turnover for essential entities, and at least 7 million euros or 1.4% for important entities (Article 34). Our article on NIS2 and board liability goes deeper into what this means for individual directors.
The duty of care asks for cyber hygiene and training for everyone, not just the board. See how Guardey trains employees in 3-minute weekly challenges and reports participation per employee.

Cyber hygiene and training: where employees come in
Most of the ten measures are about systems, policies and suppliers. Measure (g) is about people: basic cyber hygiene practices and cybersecurity training. It is also the measure that touches every employee, from reception to the board.
Cyber hygiene is the set of habits that prevent most incidents: recognising a phishing email or a fake invoice, reporting it instead of deleting it, locking a screen, using MFA without approving every prompt, and knowing what not to share on the phone. Training is how those habits are built and kept up.
NIS2 does not prescribe a format. What it does ask for, through measure (f), is that you can show your measures are effective. For training that means more than a list of who clicked through a module once a year. Useful evidence includes:
- a starting point, for example a security awareness baseline measurement;
- regular, short training instead of one long session, with participation per department;
- a follow-up measurement that shows whether behaviour changed;
- reporting the board can read in five minutes.
Phishing simulations are a common way to measure that change. To be clear: no law makes them mandatory, and NIS2 does not mention them. They are one practical way to test whether training sticks, and to give employees a safe moment to practise. Guardey offers phishing simulations alongside short weekly training challenges and reporting per employee.
Where to start
For most organisations the duty of care is not a blank page. Parts of it already exist, but scattered and not written down. This order works in practice.
- Confirm your position. Check whether you are in scope, and as an essential or an important entity. The NIS2 guide walks you through it.
- Do the risk analysis first. Every other measure follows from it. Without it you cannot explain why a measure is proportionate.
- Take the result to the board. Let the board approve the risk analysis and the plan, minute it, and schedule the NIS2 training for executives.
- Close the gaps in order of risk. Use the ten rows of the table as a gap analysis. Suppliers often turn out to be the biggest unknown, so see our guide to supplier risk management.
- Measure the human side. Start with a baseline, train regularly and measure again, so you have evidence for measures (f) and (g).
- Review and record. Evaluate once a year whether the measures work, adjust them and keep the report. That review is also the input for the next board discussion.
Reporting is a separate duty
The duty of care is about preventing and limiting incidents. Reporting them is a different obligation, in Article 23. For a significant incident you send an early warning within 24 hours, a notification within 72 hours and a final report within one month. In the Netherlands this goes through the central reporting point on MijnNCSC. Measure (b) is what makes those deadlines achievable: without a plan, 24 hours is gone before anyone knows who should report.
Frequently asked questions about the NIS2 duty of care
What is the NIS2 duty of care?
The duty of care is the obligation in Article 21 of NIS2 for essential and important entities to take appropriate and proportionate technical, operational and organisational measures to manage the risks to their network and information systems, and to prevent or limit the impact of incidents.
Which measures does the duty of care require?
At a minimum: risk analysis and security policies, incident handling, business continuity and crisis management, supply chain security, secure acquisition and maintenance including vulnerability handling, assessing the effectiveness of measures, cyber hygiene and training, cryptography, HR security with access control and asset management, and multi-factor authentication and secured communication where appropriate.
Do board members have to follow NIS2 training?
Yes. Article 20(2) requires members of the management body to follow training so they can identify risks and assess risk-management measures. National laws can add details, such as a deadline or a certificate as proof of participation. The board also has to approve the measures and oversee their implementation.
Are phishing simulations mandatory under NIS2?
No. NIS2 requires cyber hygiene and cybersecurity training, but it does not prescribe phishing simulations or any other specific format. Simulations are a practical way to measure whether training changes behaviour, which helps you show that your measures are effective.
Is the duty of care the same as the reporting obligation?
No. The duty of care (Article 21) is about managing risks and preventing incidents. The reporting obligation (Article 23) applies once a significant incident has happened: an early warning within 24 hours, a notification within 72 hours and a final report within one month.
In a personal demo we show the weekly challenges, the NIS2 training for executives and the reports on participation and progress per employee.