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 Vulnerability Assessments Under NIS2
Secure Acquisition Development Vulnerabilities / 2026-10-10

Penetration Testing and Vulnerability Assessments Under NIS2

Penetration testing and vulnerability assessments are distinct techniques for checking the security of systems that support covered services. They can support NIS2 Article 21(2)(e) on vulnerability handling and Article 21(2)(f) on evaluating the effectiveness of measures. The Directive does not impose a single penetration-test interval or methodology on every covered entity.

Choose assurance techniques according to risk

Map systems to covered services and consider how an attacker might reach sensitive data or critical operations. Vulnerability assessments can identify known flaws and configuration weaknesses at scale, while a scoped penetration test can explore how weaknesses combine into realistic attack paths.

Neither technique proves that every possible weakness has been found. The testing programme should account for exposed interfaces, privileged tools, supplier dependencies and changes since earlier assessments.

Define scope and permission before testing

Document the systems, network ranges, applications, identities and times covered. Clarify authorised techniques, test data, reporting contacts, escalation conditions and restrictions intended to protect live services.

Industrial control systems and fragile legacy equipment may be harmed by intrusive probing. Use appropriate specialist methods or controlled environments rather than treating unrestricted scanning as a prerequisite for compliance.

Assess findings in operational context

Record evidence of weaknesses and determine exploitability, affected functions, exposure and consequences for services. A published severity score is informative but does not replace an assessment of the actual deployed environment.

Separately identify potential chains involving identity, configuration and network trust. A set of individually modest weaknesses may form a more consequential path when combined.

Assign remediation and confirm outcomes

Give material findings an accountable owner, agreed treatment and target date. Choose patches, configuration changes, access restrictions or other proportionate measures, considering maintenance and service continuity risks.

Retest important fixes where practicable. Document unresolved findings and approvals of residual risk instead of presenting completion of the test as completion of remediation.

Use results to evaluate security controls

Compare repeated findings, time to resolve material exposures and the coverage of important systems. Feed results into procurement, development practices, configuration standards and staff responsibilities.

A successful test of one application says little about an untested shared identity provider. Evidence should state the tested boundaries and limitations.

Respect different legal requirements

Article 21 provides general proportionate duties, while Implementing Regulation (EU) 2024/2690 sets more detailed technical and methodological measures for defined categories of digital and ICT providers. National law or sector requirements can add specificity.

Avoid asserting that NIS2 universally requires an annual penetration test. Retain reports and remediation evidence according to the entity's needs and applicable requirements.

Questions arising

Does NIS2 require an annual penetration test for every entity?

Article 21 does not establish one universal annual penetration-test requirement for all covered entities. Check national law and any entity-specific rules.

Can a vulnerability scan replace a penetration test?

Not necessarily. Scanning and penetration testing answer different questions and should be chosen according to risk.

Related entries

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.