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.
HomeArticlesPenetration Testing and NIS2
Security Testing Audit / 2026-10-09

Penetration Testing and NIS2

Penetration testing can help a covered organisation evaluate the effectiveness of selected technical security measures. Article 21(2)(f) supports effectiveness assessment, but it does not impose one identical penetration-testing frequency on every entity.

Where penetration testing fits

A penetration test simulates selected attacker techniques within an agreed scope to examine whether vulnerabilities can be exploited and how protective controls respond. It can provide evidence about specific systems and attack paths, but cannot measure every organisational measure required by NIS2.

Use the risk assessment to choose systems and objectives. Internet-facing applications, privileged administration routes and infrastructure supporting critical services may warrant attention. A test of one website is not proof of the effectiveness of an entire cybersecurity programme.

Create an explicit and safe authorisation

Before testing, identify system owners, approved targets, prohibited activities, time windows, emergency contacts and conditions for stopping. Confirm permission for hosted or supplier-managed systems and understand any restrictions imposed by the service provider.

Operational resilience matters during tests. Rate limiting, account lockouts, unstable legacy systems and production-data exposure can make an otherwise standard technique unsafe. Arrange backups and recovery procedures appropriate to the environment and avoid collecting unnecessary personal data.

Choose methods that address the threat model

A web application engagement may examine authentication, authorisation and business logic, while a network assessment may inspect segmentation, exposed services and privilege escalation opportunities. An authenticated configuration review or vulnerability scan can complement penetration testing, but these methods answer different questions.

Record the environment, test assumptions and coverage. If detection or incident response is also being evaluated, coordinate the exercise so observers know what can be measured. Do not describe an unannounced exercise as essential for every organisation.

Make the report actionable

A useful report identifies the affected asset, observed weakness, plausible impact, reproduction evidence and environmental limitations. Priorities should reflect business criticality and exposure, not only a generic severity score.

Avoid reproducing exploit credentials or sensitive data more widely than necessary. Keep the detailed technical report restricted and provide management with an appropriate summary of material exposures, affected services, decisions and remediation progress.

Retest and place results in the wider assurance programme

After corrective changes, verify that the demonstrated path is closed and related controls still function. A retest is particularly useful where a fix depends on configuration changes, segmentation or authentication controls.

Penetration testing should sit alongside restoration exercises, access reviews, incident simulations, supplier reviews and other assessments. Check applicable national requirements and any sector-specific implementing rules, particularly for digital and ICT entities covered by Regulation (EU) 2024/2690.

Points of clarification

Is this exact testing method compulsory for every NIS2 entity?

No universal method or timetable follows from Article 21(2)(f) alone. Assess the risk and confirm national or sector-specific requirements.

Can an assessment report alone demonstrate compliance?

A report supports assurance only within its documented scope. Operational records, remediation and other legal obligations still need attention.

What should the organisation retain?

Retain the scope, authorisation, methods, evidence references, findings, responsible owners and verified corrective actions under appropriate security controls.

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.