An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesTesting the Effectiveness of NIS2 Cybersecurity Measures
Security Testing Audit / 2026-10-09

Testing the Effectiveness of NIS2 Cybersecurity Measures

Article 21(2)(f) of NIS2 requires policies and procedures to assess the effectiveness of cybersecurity risk-management measures. A defensible approach connects each material control to a risk, tests whether it operates as intended, documents findings and follows corrective work to completion. The appropriate methods and frequency depend on the entity, its risks and the applicable legal requirements.

What the NIS2 requirement actually covers

Article 21(2)(f) addresses the assessment of cybersecurity risk-management measures. It does not prescribe a single audit methodology or require every organisation to perform the same tests. Article 21(1) also frames measures around proportionality, including exposure, size, incident likelihood and potential severity.

The first task is to identify the measures that protect the network and information systems used for the organisation's services. Each measure should have a named owner, a purpose and a link to a recorded risk or obligation. Without that context, a successful technical scan can be mistaken for proof that the wider programme is effective.

Build an assessment plan from real risks

Start with systems supporting critical services, major supplier dependencies and prior incidents. Record the intended outcome of each control, the evidence that could demonstrate it and the consequence if it fails. For example, a backup policy is not tested merely by confirming that backup jobs ran. A restoration exercise is needed to establish whether usable data can be recovered within the organisation's documented recovery objective.

A practical plan can combine document reviews, configuration inspections, interviews, access recertification, restore exercises, incident simulations and carefully authorised technical testing. Choose methods for the assurance question rather than applying every technique to every system.

Separate control design from control operation

Design effectiveness asks whether a measure could address the identified risk if implemented as planned. Operating effectiveness asks whether it actually functions over the period examined. An access review procedure may be well designed while removal of departed employees' accounts is regularly delayed. Both findings matter, but the corrective actions differ.

Sample evidence from normal operations where possible. Consider exceptional conditions such as out-of-hours incidents, failed automated jobs and supplier outages. A control that only works during a planned demonstration may not deliver the intended protection.

Measure outcomes without mistaking numbers for assurance

Metrics can reveal trends, such as the proportion of critical patches completed within a defined internal target or the time required to remove high-risk access. They do not by themselves demonstrate that the target was appropriate or the underlying exposure was reduced. Explain each metric's scope, collection method, limitations and decision threshold.

Pair quantitative results with qualitative findings. A short table of failed restore tests, root causes, ownership and repeat-test dates can provide more decision value than a large dashboard of green indicators.

Record findings and verify corrective actions

Maintain an assessment record containing scope, date, method, assessor, tested population, evidence reference, outcome and any limitations. Findings should identify the affected service, risk significance, owner and agreed action. Keep supporting records securely and restrict access where test material exposes vulnerabilities.

Closure should require evidence that the action works. A ticket marked complete after a configuration change is weaker evidence than a repeat test showing the underlying weakness is resolved. Escalate overdue or repeatedly failing controls to management according to the organisation's governance arrangements.

Account for national and sector-specific rules

NIS2 is a Directive implemented in Member State law. Organisations must check applicable national rules and competent-authority guidance before treating a proposed assessment schedule as a legal requirement. Commission Implementing Regulation (EU) 2024/2690 provides more detailed requirements for certain digital infrastructure, ICT service management and digital provider entities, so those organisations should assess whether it applies to them.

ENISA's technical implementation guidance gives practical advice and examples of evidence for the entities covered by that implementing regulation. It is useful context, but its detailed coverage should not be described as an identical mandatory checklist for every NIS2 sector.

Points of clarification

Does NIS2 require penetration testing for every covered entity?

Article 21(2)(f) requires assessment policies and procedures but does not impose one universal penetration-testing schedule on every entity. Check applicable national and sector-specific requirements and select methods suited to the risks.

Is an annual audit enough to demonstrate effectiveness?

Not necessarily. An audit may provide valuable assurance, but changes to systems, incidents and critical control failures may require more frequent or different forms of assessment.

What evidence should management receive?

A concise record of assessment coverage, material failures, residual risk, agreed corrective actions, owners and verified closure helps management oversee the programme.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.