Skip to main content

    1 July 2026 · 8 min read · By Michael van Mameren, Lead Penetration Tester (OSCP)

    NIS2 Compliance and Penetration Testing: Requirements, Scope, and How to Prepare

    NIS2 raises the bar on cybersecurity risk management for thousands of organisations across the EU. Here is what it requires, who it covers, and where security testing fits in.

    Request a quote

    What is NIS2?

    NIS2 is the EU Network and Information Security Directive (Directive (EU) 2022/2555), the successor to the original 2016 NIS Directive. It significantly widens the range of sectors in scope, raises the baseline for cybersecurity risk management, and introduces stricter incident-reporting duties and direct accountability for company management. Each member state implements NIS2 in national law.

    In the Netherlands, NIS2 is implemented through the Cyberbeveiligingswet (Cbw). The Eerste Kamer approved the law on 7 July 2026 and it entered into force on 15 August 2026. In-scope organisations must register with the NCSC, and the duty of care and incident reporting obligations apply now, so the risk-management measures need to be in place rather than planned.

    Does NIS2 apply to my organisation?

    NIS2 splits in-scope organisations into essential and important entities, based mainly on sector and size (generally medium-sized and larger, from 50 staff or EUR 10M turnover, with some sector exceptions). You are likely in scope if you operate in one of these areas.

    • Energy, transport, banking, and financial market infrastructure
    • Health, drinking water, waste water, and digital infrastructure
    • ICT service management, public administration, and space
    • Postal and courier services, waste management, and chemicals
    • Food production and processing, and manufacturing (incl. medical devices, electronics, machinery)
    • Digital providers such as online marketplaces, search engines, and social platforms

    What does NIS2 require?

    NIS2 requires in-scope entities to take appropriate and proportionate technical, operational, and organisational measures to manage cybersecurity risk. These include risk analysis and information-system security policies, incident handling, business continuity and backup, supply-chain security, secure development and vulnerability handling, and policies to assess the effectiveness of security measures. That last point is where testing matters: you are expected to verify that your controls actually work, not just that they exist.

    NIS2 also introduces a phased incident-reporting duty (an early warning within 24 hours, a fuller notification within 72 hours, and a final report within a month), and it makes management bodies directly responsible for approving and overseeing cybersecurity measures. Non-compliance carries significant penalties: for essential entities, fines up to EUR 10 million or 2% of global annual turnover; for important entities, up to EUR 7 million or 1.4%.

    How penetration testing supports NIS2 compliance

    NIS2 does not prescribe a specific test, but its requirement to assess the effectiveness of your security measures is difficult to satisfy without independent testing. A penetration test is one of the clearest ways to produce that evidence.

    Evidence that controls work

    NIS2 expects policies to assess the effectiveness of cybersecurity risk-management measures. A penetration test provides concrete, independent evidence of whether your controls hold against a realistic attacker, not just a checklist that says they should.

    Vulnerability handling and secure development

    The directive calls for vulnerability handling and disclosure and secure development practices. Regular testing of your applications and infrastructure feeds directly into that process, surfacing exploitable issues before an attacker does.

    Supply-chain and risk analysis

    Testing your external perimeter and internal segmentation informs the risk analysis NIS2 requires, and helps you understand the blast radius of a compromised supplier or account.

    Board-ready assurance

    Because NIS2 makes management directly accountable, leadership needs credible assurance. A clear penetration-test report gives your management body the independent view of security posture the directive expects them to oversee.

    Essential vs important entities

    NIS2 sorts in-scope organisations into two categories. The security measures are largely the same; supervision and maximum fines differ.

    AspectEssential entitiesImportant entities
    Typical sectorsEnergy, transport, banking, health, drinking water, digital infrastructure, public administrationPostal services, waste management, chemicals, food, manufacturing, digital providers
    SupervisionProactive: audits and inspections can happen without an incidentReactive: mainly after an incident or an indication of non-compliance
    Maximum fineEUR 10 million or 2% of global annual turnoverEUR 7 million or 1.4% of global annual turnover
    Security measuresArticle 21 risk-management measuresArticle 21 risk-management measures
    Incident reportingRequired for significant incidentsRequired for significant incidents

    NIS2 incident reporting timelines

    For significant incidents, NIS2 sets a staged reporting process to the national CSIRT or competent authority. Tested detection is what makes these deadlines realistic.

    • Within 24 hours: an early warning, including whether the incident may be caused by unlawful or malicious acts or could have cross-border impact.
    • Within 72 hours: an incident notification with an initial assessment of severity and impact, and indicators of compromise where available.
    • On request: intermediate status updates for the authority.
    • Within one month: a final report covering the incident, its root cause, the mitigation applied, and any cross-border impact.

    A practical NIS2 testing programme

    NIS2 does not prescribe a testing schedule, so a sensible programme is risk-based. This structure works for most organisations.

    1. Map your critical services

    Start from the services that would affect customers or society if disrupted. They set the scope for testing, not the other way round.

    2. Test the external attack surface

    An external penetration test of internet-facing systems shows what an outside attacker could reach first.

    3. Test from the inside

    An internal or assumed-breach test shows how far an attacker could move after an initial foothold, which is where many real incidents escalate.

    4. Include suppliers and integrations

    NIS2 explicitly covers supply-chain security. Test the connections, APIs, and access that third parties have into your environment.

    5. Retest and keep the record

    Retest critical findings after remediation and keep reports, remediation evidence, and retest results together. That record is what you show a supervisor or auditor.

    Frequently asked questions

    Preparing for NIS2?

    We help in-scope organisations get ready, from a readiness assessment through to the security testing that proves your controls work. Talk to our team.