🇪🇺 EU
DIRECT ANSWER — DOES NIS2 REQUIRE PENETRATION TESTING IN EU?
NIS2 Article 21(2)(e) requires risk-based vulnerability handling and (f) requires regular testing of security measure effectiveness. Penetration testing evidences both by identifying exploitable vulnerabilities and verifying controls operate as intended. Essential and important entities across the EU need documented, severity-rated test reports mapped to Article 21 measures within their risk assessment.
Article 21 of the NIS2 Directive sets out the minimum set of technical, operational, and organisational measures that essential and important entities must implement to manage cybersecurity risks. The measures cover governance, risk management, incident handling, business continuity, supply chain security, secure development, network security, access control, encryption, and the regular testing and verification of effectiveness. Member states transpose these requirements into national law, and national competent authorities supervise compliance.
Article 21(2)(e) specifically requires entities to handle vulnerabilities in a risk-based manner, including vulnerability disclosure and remediation. Article 21(2)(f) requires the regular testing and verification of the effectiveness of security measures. These two provisions are the most directly connected to penetration testing, because a penetration test produces the kind of documented, reproducible evidence that demonstrates both vulnerability handling and effectiveness verification are actually occurring.
Article 21(2)(e) is about vulnerability handling: identifying vulnerabilities, assessing their risk, disclosing them where required, and remediating them. A penetration test identifies exploitable vulnerabilities in a structured way, with each finding documented by severity, proof of concept, and remediation guidance. That output feeds directly into the vulnerability handling process the article requires, providing the evidence that vulnerabilities are being found and addressed.
Article 21(2)(f) is about effectiveness verification: confirming that the security measures an entity has implemented are actually working. A penetration test tests controls against real attack techniques and reports which held and which failed. That is precisely the kind of evidence (f) expects, not a claim that controls are effective, but a demonstration of whether they are. When the test report maps each finding and each control to the relevant Article 21 measure, regulators and auditors can trace the evidence directly to the obligation.
The deliverable is structured to evidence Article 21(2)(e) and (f) directly. It includes a scoping document defining the target surface, rules of engagement, and test windows, aligned to the entity's risk assessment. The executive summary describes the scope and overall risk posture in business terms, mapping findings to the relevant Article 21 measures so that regulators and internal risk functions can trace each item to the directive's requirements.
The technical report documents every confirmed finding with its CVSS v3.1 severity, a proof of concept, the root cause, and prioritised remediation guidance. Critical and high findings are retested after remediation to confirm each fix resolves the original issue without introducing new weaknesses. An attestation letter documents the verification outcome. The report is structured so that engineering teams can act on findings directly, and so that auditors can trace evidence to the specific Article 21 measures that require it.
Article 21 applies to all essential and important entities across the EU, regardless of the member state in which they are established. National transpositions, such as the Dutch Cyberbeveiligingswet, the Finnish Kyberturvallisuuslaki, and the Estonian Cybersecurity Act amendment, implement the same baseline obligations, though enforcement specifics and sector classifications differ by country. An entity operating across multiple member states may need to evidence Article 21 compliance to more than one national competent authority.
A penetration test report scoped to the entity's risk assessment and mapped to Article 21 measures can serve as evidence across jurisdictions, provided the scope and methodology are consistent. Where national regulators expect specific formatting or mapping, the report can be adapted without re-running the test. The key requirement is that the evidence is documented, severity-rated, reproducible, and current relative to the regulatory review window.
FAQ
Article 21 does not name penetration testing as a standalone obligation. It requires essential and important entities to implement risk-based measures including vulnerability handling under (e) and the regular testing of effectiveness under (f). Penetration testing is the most direct way to evidence both measures. Regulators expect documented test reports, not just a policy statement.
Article 21(2)(e) means identifying vulnerabilities, assessing their risk, disclosing them where required, and remediating them. Article 21(2)(f) means confirming that the security measures an entity has implemented are actually working. A penetration test produces documented evidence for both: it finds exploitable vulnerabilities and tests whether controls hold against real attack techniques.
Article 21 does not prescribe a fixed frequency. It requires risk-based measures and ongoing effectiveness review. Testing frequency should reflect your risk profile, the rate of change to your systems, and your entity classification. Annual testing is a common baseline, but higher-risk or rapidly changing environments may warrant more frequent testing aligned to release cycles.
The report should define scope, rate findings by CVSS v3.1 severity, map each finding to the relevant Article 21 measure, and include remediation status with retest evidence. An executive summary should describe the overall risk posture in business terms. Reports should be current relative to the regulatory review window and scoped to the systems in your risk assessment.
A single test can serve as evidence across jurisdictions if the scope and methodology are consistent and the report maps findings to Article 21 measures. Where national regulators expect specific formatting or mapping, the report can be adapted without re-running the test. The key requirement is that the evidence is documented, severity-rated, reproducible, and current.
Book a scoping call and we will define targets, rules of engagement, and a fixed price for your NIS2-aligned penetration test.
Request a scoping call