NIS2 sets out a short list of security measures, each covering a range of specific requirements and tasks. We translate the requirements into what you actually have to put in place.
Article 21 of NIS2 sets out ten security measures in a few hundred words. Article 20 adds management accountability and Article 23 the reporting deadlines. Between them, the three articles take up barely two pages.
That's deliberate. NIS2 tells you what to achieve and leaves the detail to national law, to the supervisory authorities, and to your own judgment about what's proportionate. It says you need policies on risk analysis. It doesn't say what goes in them, who signs them off, or how often you revisit them.
So there's a gap between reading the directive and knowing what to build. This article is about closing it: what each requirement means in terms of documents, owners and recurring tasks, and what a supervisor will probably ask to see.
Key takeaways
- The requirements come from three articles, not one. Article 20 covers management accountability, Article 21 the security measures, Article 23 incident reporting. Most organisations only plan for the middle one.
- Article 21 lists ten measures, phrased as outcomes. Each one translates into at least one artifact with a named owner and a review cycle.
- Proportionality is the operative word. Measures must match your exposure, size and the societal impact of an outage, which is why the same list produces very different programs and why your reasoning has to be written down.
- Supply chain security is the requirement that travels. It reaches organisations with no NIS2 obligations of their own, through their customers' contracts.
- What fails an audit is usually the evidence, not the control. Most organisations do the work, but stumble at showing the dated record of when it happened.
The requirements sit in three places
Article 20 governance.
Management bodies must approve the risk-management measures, oversee their implementation, and undergo training themselves. Supervisors can hold individuals personally liable, and at essential entities can temporarily bar them from management functions.
Article 21 security measures.
The ten technical, operational and organisational measures, built on an all-hazards approach and sized proportionately.
Article 23 incident reporting.
Early warning within 24 hours of becoming aware of a significant incident, a fuller notification within 72 hours, a final report within one month.
Organisations plan diligently for Article 21 and get caught on the other two. Article 23 becomes a challenge when there is no clear process in place for handling and reporting significant incidents even when they occur on a Sunday afternoon.
The ten measures, translated
Article 21(2) is written as outcomes. This is what each one means as something you can actually build, own and show.
What you need in place
Examples of documentation a supervisory authority may request
1. Risk analysis and information system security policies. What you need in place: a documented risk assessment method, applied, with a treatment plan and an approved security policy. A supervisory authority may ask for: current risk assessments, security policies, and documentation of approval and follow-up.
2. Incident handling. What you need in place: a written process covering detection, classification, escalation and the reporting clock, with named roles. A supervisory authority may ask for: the procedure, plus records from a real or tested incident.
3. Business continuity, backup management and crisis management. What you need in place: backup routines, restore testing, a continuity plan and a crisis plan naming decision-makers. A supervisory authority may ask for: the date of your last restore test and its result.
4. Supply chain security. What you need in place: a register of direct suppliers with criticality ratings, security requirements in contracts, and follow-up. A supervisory authority may ask for: a supplier overview, risk assessments, relevant contractual provisions, and documentation of follow-up.
5. Security in acquisition, development and maintenance, including vulnerability handling. What you need in place: a vulnerability management process with timelines by severity, and security requirements in procurement. A supervisory authority may ask for: how fast you patched the last critical vulnerability, with proof.
6. Policies to assess the effectiveness of risk-management measures. What you need in place: a defined way of testing whether controls work, and a record of the results. A supervisory authority may ask for: test results and what changed as a consequence.
7. Basic cyber hygiene and security training. What you need in place: a training programme covering all staff, with completion records, and baseline hygiene standards. A supervisory authority may ask for: who was trained, when, and the completion rate.
8. Cryptography and encryption policies. What you need in place: a written policy stating where encryption is required and which standards apply. A supervisory authority may ask for: the policy, and evidence it matches reality.
9. Human resources security, access control and asset management. What you need in place: joiner-mover-leaver routines, access reviews on a cycle, and a current asset inventory. A supervisory authority may ask for: the last access review, with date and reviewer.
10. Multi-factor authentication and secured communications. What you need in place: MFA deployed with documented scope and exceptions, plus a communications plan for when primary systems are down. A supervisory authority may ask for: documentation of implemented authentication measures, secure communication, and any risk-based exceptions.
The last line under each measure is the useful one. Nearly every organisation can describe its controls. The gap is in producing the dated artefact that proves the control operated – so treat those lines as a list of what to go and check this quarter.
How much is enough
Article 21 requires measures that are appropriate and proportionate, taking into account the state of the art, implementation costs, and the entity's exposure, size and the societal impact of an incident.
That wording is doing real work. It means there is no fixed answer, and that a small regional supplier is not expected to run a national grid operator's program. It also means the burden is on you to explain the level you chose.
In practice proportionality is defensible when three things exist: a risk assessment showing what you actually face, a documented decision about what you will and won't implement, and an approval from someone with the mandate to make that call. Without them, "proportionate" becomes indistinguishable from "we didn't get to it."
The cheapest mistake to avoid is implementing from the list rather than from the risk. Controls selected because they appear in Article 21, with no line back to an identified risk, cost money and still read badly in an audit, because the risks and the measures don't line up. Build the risk assessment first and let it justify the control set.
Supply chain security reaches further than the rest
One requirement behaves differently from the other nine. Supply chain security obliges in-scope entities to manage the security of their direct suppliers, which means the requirements propagate down the chain through contracts.
The practical consequence is that organisations with no NIS2 obligations of their own receive security questionnaires and contract clauses derived from it. They can't be fined by a regulator. They can lose the customer.
If you are in scope, this is a real workload: a register of direct suppliers, criticality assessment, security requirements written into contracts, and documented follow-up. The follow-up is the part that slips an annex signed in 2024 proves nothing in 2026 unless somebody checked. If you're on the receiving end, the efficient move is to prepare the evidence pack once rather than answering each supplier review from scratch.
The management requirements are the easiest to fail
Article 20 asks for three things from the management body: approve the measures, oversee implementation, complete training. All three are straightforward to do and easy to leave no trace of.
Approval needs to be a minuted decision with a date, not a slide someone presented. Oversight needs to be recurring and recorded a standing agenda item produces evidence; an informal check-in doesn't. Training needs an attendance record.
What management actually needs to see, and how often, is worth settling early, because the reporting line is what makes oversight demonstrable rather than asserted.
Where organisations get this wrong
Across the programs that run into trouble, the same five patterns recur.
Documentation written for the auditor. Policies that describe an idealised organisation. These fail faster than no policy at all, because the gap between the document and reality is itself a finding.
No owner at the control level. "IT" owns MFA. Nobody owns the exceptions list.
The risk assessment aged out. Written during implementation, never revisited, now describing systems and suppliers the company no longer has.
Evidence collected retroactively. Someone assembles it in the two weeks before an audit, which is expensive and produces weaker proof than capturing it as the work happens.
NIS2 run as a separate program. A parallel track beside ISO 27001 and GDPR, with its own spreadsheet describing the same controls. The overlap is large enough that running one information security management system across all of them is substantially cheaper.
Where to start
Whether youre mapping the requirements for the first time or reviewing an existing programme, the following should be in place:
- The scope decision is written down, dated and owned, and you're registered with the correct national authority
- Each of the ten Article 21 measures has a named owner and at least one artifact behind it
- The risk assessment is current and visibly connects to the controls you chose
- Someone specific can declare an incident significant, outside office hours
- The 24-hour, 72-hour and one-month steps exist as tasks with owners, not as knowledge
- Management approval is minuted and training is recorded
- Direct suppliers are assessed, contracts carry security requirements, and follow-up has happened at least once
Work through the documentation lines under the ten measures before anything else. It’s the fastest way to find out which requirements you meet in practice but can’t currently prove – which, for most organisations, is where the real gap sits.
Cerivo's NIS2 solution maps the requirements of Article 21 directly to ISO 27002 controls, allowing you to focus on closing actual gaps rather than documenting work youve already done. Each security measure is assigned an owner and a regular review cycle, while documentation is maintained continuously, giving management the information they need to oversee the work effectively.
Frequently asked questions
Does NIS2 apply to suppliers?
Not directly, unless the supplier is itself in scope. But in-scope entities must manage the security of their direct suppliers, so the requirements reach suppliers through contracts and security questionnaires. The consequence for a supplier is commercial rather than regulatory.
How detailed do NIS2 measures have to be?
They must be appropriate and proportionate to your exposure, size and the societal impact of an incident. There is no fixed level. What makes a chosen level defensible is a current risk assessment, a written decision about what you will and won't implement, and approval from someone with the mandate to make that call.
Is ISO 27001 enough to meet NIS2 requirements?
It covers much of Article 21 and is a strong starting point, but it isn't automatically sufficient. NIS2 adds obligations ISO 27001 doesn't include, among them national registration, the 24/72-hour reporting ladder, and personal management accountability.
What are the 10 minimum measures in Article 21?
Risk analysis and security policies; incident handling; business continuity, backup and crisis management; supply chain security; security in acquisition, development and maintenance including vulnerability handling; policies to assess the effectiveness of the measures; basic cyber hygiene and training; cryptography and encryption; human resources security, access control and asset management; and multi-factor authentication with secured communications.
What are the NIS2 requirements?
NIS2 requirements sit in three articles. Article 20 requires management bodies to approve and oversee cybersecurity risk-management measures and to undergo training. Article 21 sets out ten technical, operational and organizational measures. Article 23 requires incident reporting within 24 hours, 72 hours and one month.

