ComplianceOctober 2, 2026·5 min read

NIS2 Article 21 for Software Teams: What a Scanner Covers and What It Does Not

Article 21 of the NIS2 Directive (Directive (EU) 2022/2555) lists ten cybersecurity risk-management measures that essential and important entities must have in place. Member states had until 17 October 2024 to transpose the directive, so the detail you answer to is your national law. This post goes through the ten measures from the point of view of a team that ships software, and says plainly which ones scanning and vulnerability handling help with and which ones they do not touch.

Who this applies to

NIS2 applies to medium and large organisations in the sectors listed in its two annexes, plus some providers regardless of size. For software companies the usual routes in are being a cloud, data centre or managed service provider, or being a supplier to a customer who is in scope. In the second case the directive does not bind you directly, but measure (d) on supply chain security means your customer has to ask how you build and maintain what you sell them. The questionnaire you receive is Article 21 arriving by another road.

Two points are worth knowing before the list. Article 21(1) asks for measures that are appropriate and proportionate to the risk, so a 60-person company is not expected to look like a bank. And Article 20 makes the management body responsible for approving the measures and overseeing them, which is why this cannot be handed wholesale to the engineering team. For some digital providers, Commission Implementing Regulation (EU) 2024/2690 sets out the technical requirements in more detail. Check whether your category is listed there.

The ten measures in plain terms

(a) Policies on risk analysis and information system security. A written, approved statement of how you identify risks and what you do about them.

(b) Incident handling. How you detect, classify, respond to and learn from incidents. Article 23 adds the reporting clock for significant incidents: an early warning within 24 hours, a notification within 72 hours and a final report within one month.

(c) Business continuity. Backups, disaster recovery and crisis management, including proof that a restore works.

(d) Supply chain security. The security of your direct suppliers and service providers and, for a software team, of the third-party code you ship.

(e) Security in the acquisition, development and maintenance of systems, including vulnerability handling and disclosure.

(f) Policies and procedures to assess whether your measures are effective.

(g) Basic cyber hygiene and cybersecurity training.

(h) Policies and procedures on the use of cryptography and, where appropriate, encryption.

(i) Human resources security, access control policies and asset management.

(j) Multi-factor or continuous authentication, and secured voice, video, text and emergency communications, where appropriate.

Where scanning and vulnerability handling do real work

Measure (e) is the one a software team lives in. Static analysis, dependency analysis, secrets detection and dynamic testing are how you find weaknesses before and after release. Finding them is half of it. The directive names vulnerability handling, so an auditor will want to see what happened next: who triaged the finding, how long the fix took, and how you confirmed it. A scanner that produces a list and no record of decisions gives you very little here.

Measure (d) is partly covered. Dependency scanning and a software bill of materials tell you which third-party components you ship and which have known vulnerabilities. They say nothing about your hosting provider, your payroll vendor or the contractor with production access. Those need supplier reviews and contract terms.

Measure (h) is partly covered. Scanners can check TLS versions and certificates, flag weak algorithms in code and build an inventory of the cryptography in use. The policy that says which algorithms are approved and how keys are managed is still a document someone has to write.

Measure (f) is where scan history earns its keep. Trends in open findings, time to remediate and re-test results are evidence that your measures work, or an early signal that they do not.

Measure (i) gets a little help. A list of scanned targets and discovered hosts is a start on asset management for your internet-facing estate, and dynamic testing can find broken access control in an application. It does not manage who has access to what inside your company.

Measure (j) gets less. A scan can show that a login flow lacks a second factor. It cannot show that your staff use one.

What no scanner covers

Measures (a), (b), (c) and (g), and most of (i), are organisational. No tool run against your code or your website can produce a risk policy approved by management, an incident process that people have rehearsed, a restore test, training records, or joiner and leaver procedures. The same goes for the Article 20 duties of the management body and the Article 23 reporting process. For those you need named people, contact details for your national CSIRT or competent authority, and a decision made in advance about who may declare an incident significant.

This matters when you buy tooling. A product that claims to make you NIS2 compliant from scan results alone is overstating what scan results are. The honest shape of the work is a short set of policies, a handful of rehearsed processes, and technical evidence that the processes are running.

A sensible order of work

1. Establish whether you are in scope directly or as a supplier. If directly, find your national transposition law and your competent authority.

2. Write down who decides and who reports. An incident process that names people is worth more than a long one that does not.

3. Put scanning on a schedule and keep the triage record. The record is the evidence for (e) and (f).

4. Generate an SBOM for each product and list your direct suppliers for (d).

5. Record your cryptography choices for (h), then check reality against them.

6. Deal with training, HR security and continuity with the people who own them. They are not engineering tasks, though engineering will be asked for input.

How Spoorder fits

On Pro and above, Spoorder maps scan findings and evidence to the NIS2 measures and shows where there is evidence and where there are gaps. A measure reads "not assessed" until there is evidence for it, and the mapping does not certify anything. The governance, training, HR and incident-process measures above remain yours to run.

Ready to scan your application?

Free health check: HTTPS, TLS and security headers for one URL, in about a minute. Free account, no credit card.

Scan your app free →
← Back to blog