🇪🇪 ESTONIA
DIRECT ANSWER — DOES NIS2 REQUIRE PENETRATION TESTING IN ESTONIA?
Yes. Estonia transposes NIS2 through an amendment to its Cybersecurity Act, in force from 1 January 2026. Essential and important entities must implement Article 21 risk-based measures including vulnerability handling and effectiveness testing. Penetration testing evidences Article 21(2)(e) and (f). The Estonian Information System Authority (RIA) expects documented test evidence.
Estonia transposes the NIS2 Directive through an amendment to its Cybersecurity Act (Küberkindlustuse seadus), which enters into force on 1 January 2026. The Estonian Information System Authority (RIA) acts as the national competent authority, responsible for supervision, guidance, and the receipt of incident notifications. The amendment expands the scope of the original Estonian Cybersecurity Act to cover the 18 critical and important sectors defined in NIS2, introduces mandatory 24-hour early warning and 72-hour incident notification, and makes senior management personally accountable for cybersecurity governance.
Estonia's digital infrastructure is among the most advanced in Europe, with extensive public-sector dependency on digital services. The amended Cybersecurity Act reflects that context, placing particular emphasis on the resilience of digital infrastructure and the supply chains that support it. Non-compliance can carry administrative fines consistent with the NIS2 Directive's maximum thresholds, and RIA has the authority to issue binding instructions to in-scope entities where measures are found inadequate.
Under the amended Cybersecurity Act, essential entities in Estonia include operators in energy, transport, banking, financial market infrastructure, health, drinking water, digital infrastructure, public administration, and space. Important entities cover postal and courier services, waste management, the manufacture of critical equipment, digital service providers, and research organisations. Size thresholds determine classification, though certain entities such as DNS providers, public administration bodies, and market infrastructure operators are in scope regardless of size.
Estonian organisations, particularly those in the digital infrastructure and public administration sectors, should confirm their classification with RIA. Estonia's concentration of digitally delivered public services means that entities providing underlying infrastructure may fall within scope even where their individual size would not otherwise trigger the thresholds. RIA maintains guidance on sector classification and the obligations that apply once an entity is confirmed as essential or important.
Article 21(2)(e) requires entities to handle vulnerabilities in a risk-based manner, including disclosure and remediation. Article 21(2)(f) requires the regular testing and verification of the effectiveness of security measures. Penetration testing evidences both: it identifies exploitable vulnerabilities that must be handled under (e), and it demonstrates whether controls are operating as intended under (f).
RIA expects in-scope entities to maintain documented evidence that Article 21 measures are operating. A penetration test report scoped to the entity's risk assessment, with severity ratings, proof of concept, and remediation status, provides that evidence in a form that RIA reviewers and internal risk functions can trace to the relevant Article 21 measure. For entities operating in Estonia's highly digitised environment, where a single vulnerability can affect multiple dependent services, the value of documented, reproducible test evidence is particularly high.
The deliverable includes a scoping document defining targets, rules of engagement, and test windows. The executive summary maps findings to the relevant Article 21 measures so that RIA reviewers and the entity's risk function can trace each item to the directive's requirements. The technical report documents every confirmed finding with its CVSS v3.1 severity, proof of concept, 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 and regulators can trace evidence to the Article 21 measures that require it. For entities operating across the Baltic region, the report can be aligned to obligations under multiple national transpositions where relevant.
FAQ
The amended Cybersecurity Act does not name penetration testing as a standalone obligation. It requires essential and important entities to implement Article 21 risk-based measures, including vulnerability handling and the regular testing of effectiveness. Penetration testing is the most direct way to evidence those two measures. RIA expects documented test reports, not just a policy statement.
Essential entities under the amended Cybersecurity Act include operators in energy, transport, banking, financial market infrastructure, health, drinking water, digital infrastructure, public administration, and space. Size thresholds apply, though some entities such as DNS providers, public administration bodies, and certain market infrastructure operators are in scope regardless of size. RIA provides guidance on classification.
The amended Cybersecurity Act 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.
Yes. Critical and high findings are retested after remediation to confirm each fix resolves the original issue without introducing new weaknesses. Verified fixes are documented and an attestation letter is issued. The retest is included in the engagement price, and the engagement is not closed until it is complete.
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