🇫🇮 FINLAND

NIS2 Penetration Testing in Finland

DIRECT ANSWER — DOES NIS2 REQUIRE PENETRATION TESTING IN FINLAND?

Yes. Finland transposes NIS2 through the Kyberturvallisuuslaki (Cybersecurity Act), supervised by Traficom. 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). Traficom expects documented test reports with severity ratings mapped to the entity's risk assessment.

The Finnish Kyberturvallisuuslaki and NIS2

Finland transposes the NIS2 Directive through the Kyberturvallisuuslaki (Cybersecurity Act), with the Finnish Transport and Communications Agency (Traficom) acting as the national competent authority. Traficom is responsible for supervision, enforcement, and the receipt of incident notifications. The law expands the scope of the original Finnish 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 failures.

Finnish entities should confirm their classification with Traficom. The agency provides guidance on which sectors and entity types fall within scope, and on the obligations that apply once an entity is classified as essential or important. Non-compliance can carry administrative fines consistent with the NIS2 Directive's maximum thresholds, and Traficom has the authority to issue binding instructions and order corrective measures where an entity's measures are found inadequate.

Which entities are in scope in Finland

Under the Kyberturvallisuuslaki, essential entities in Finland 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.

Finnish organisations operating across Nordic or Baltic markets should note that classification depends on where the entity is established. A company headquartered in Finland but operating in the Netherlands or Estonia may have obligations under multiple national transpositions. Traficom coordinates with counterpart regulators in other member states, but the primary supervisory relationship sits with the authority in the entity's country of establishment.

How penetration testing evidences Article 21(2)(e) and (f)

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. A penetration test scoped to the entity's risk assessment provides evidence for both: it identifies exploitable vulnerabilities that must be handled under (e), and it demonstrates whether controls are operating as intended under (f).

Traficom expects essential and important entities to maintain documented evidence that Article 21 measures are operating, not merely described in policy. A penetration test report with scope, severity ratings, proof of concept, and remediation status provides that evidence in a form that Traficom reviewers and internal risk functions can trace directly to the relevant Article 21 measure. Testing that is aligned to the entity's risk assessment and repeated at a risk-appropriate cadence strengthens the compliance position over time.

What the deliverable contains

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 Traficom 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. Testing frequency and scope are aligned to the entity's risk assessment rather than applied as a fixed interval.

FAQ

Frequently asked questions

Does the Kyberturvallisuuslaki explicitly require penetration testing?

The Kyberturvallisuuslaki 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. Traficom expects documented test reports, not just a policy statement.

Which Finnish entities are classified as essential?

Essential entities under the Kyberturvallisuuslaki 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. Traficom provides guidance on classification.

How often should we test under NIS2 in Finland?

The Kyberturvallisuuslaki 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.

What should the report include for Traficom review?

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.

Is a retest included in the engagement?

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.

Request a fixed-scope engagement

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