Penetration Testing Requirements in Germany: NIS2 (BSIG), KRITIS, DORA and BSI (2026)
Published by Zero Hunt, an autonomous AI red team on an on-premise appliance running private AI: automated penetration testing for networks and infrastructure, black-box or gray-box, with a human approving every step that matters.
Short definition
Germany's NIS2 law, in force since 6 December 2025, never uses the word “Penetrationstest”: it requires about 29,500 entities to assess whether their security measures work. Yearly penetration tests appear one level down, in the BSI criteria for critical infrastructure audits and in the C5 cloud catalogue, and DORA adds yearly testing and three-yearly TLPT for finance.
Why this matters now
Germany transposed NIS2 late and without a transition period: the new BSI Act (BSIG) applied in full from 6 December 2025, the registration deadline has passed, and managers are personally responsible for the measures. At the same time the KRITIS evidence cycle moved from two to three years, BaFin's BAIT circular ends on 31 December 2026 as DORA takes over, and the BSI published a new C5 catalogue in April 2026. Buyers and auditors now ask which of these texts actually demands a test, and how often.
Key points
- ▸NIS2 in Germany (BSIG, in force 6 December 2025): § 30 requires vulnerability handling and “concepts and procedures to assess the effectiveness” of measures. It names no penetration test and no frequency.
- ▸Operators of critical facilities prove their measures to the BSI every three years (§ 39 BSIG). The BSI's audit criteria catalogue expects penetration tests at least once a year (requirement 95, RB-18).
- ▸Finance: DORA requires yearly tests of ICT systems supporting critical or important functions and TLPT at least every three years for identified entities; BaFin is the TLPT authority and the Bundesbank accompanies each test. BAIT is fully repealed at the end of 2026.
- ▸BSI IT-Grundschutz treats penetration tests as SOLLTE (should) for systems with higher protection needs. C5:2026 requires cloud providers to test at least yearly and after material changes. TISAX names them as an example at high protection needs.
- ▸Penalties under the BSIG reach EUR 10 million or 2 % of worldwide turnover for particularly important entities, and EUR 1 million for missing KRITIS evidence.
NIS2 in Germany: the new BSIG since 6 December 2025
Germany transposed NIS2 with the NIS-2-Umsetzungs- und Cybersicherheitsstärkungsgesetz of 2 December 2025 (BGBl. 2025 I Nr. 301). It entered into force on 6 December 2025 with no general transition period. The duties sit in a new BSI Act (BSIG) that replaces the 2009 law.
- Who is covered (§ 28). “Besonders wichtige Einrichtungen” (particularly important entities): operators of critical facilities, and Annex 1 entities with at least 250 employees or more than EUR 50 million turnover and EUR 43 million balance sheet. “Wichtige Einrichtungen” (important entities): Annex 1 and 2 entities with at least 50 employees or more than EUR 10 million turnover and balance sheet. The BSI counts about 29,500 entities, up from about 4,500.
- Registration (§ 33). Within three months of falling in scope. The BSI states that the statutory deadline has passed; on 30 September 2026, 20,141 entities had registered.
- Incident reporting (§ 32). Early warning within 24 hours, notification within 72 hours, final report within one month.
- Management (§ 38). Managers must implement and oversee the measures, are liable to the entity, and must attend regular training.
- Fines (§ 65). Up to EUR 10 million or 2 % of worldwide turnover for particularly important entities, up to EUR 7 million or 1.4 % for important entities.
Financial entities under DORA, and telecoms and energy operators, follow their own regimes for the risk measures (§ 28(5) and (6)).
What § 30 BSIG says about testing
The BSIG does not contain the word “Penetrationstest”. § 30 requires “geeignete, verhältnismäßige und wirksame” (suitable, proportionate and effective) technical and organisational measures, which should follow the state of the art, and compliance must be documented. Of the ten minimum areas in § 30(2), two concern testing:
- Nr. 5. Security in the acquisition, development and maintenance of IT systems, “einschließlich Management und Offenlegung von Schwachstellen” (including the management and disclosure of vulnerabilities).
- Nr. 6. “Konzepte und Verfahren zur Bewertung der Wirksamkeit von Risikomanagementmaßnahmen” (concepts and procedures to assess the effectiveness of risk-management measures).
So the law asks for a result, proof that the measures work, and leaves the method to the entity. A penetration test is the usual way to produce that proof, and a vulnerability scan alone shows which weaknesses exist, not whether the measures stop an attacker. For cloud, data-centre, managed-service and similar digital providers, the Commission's implementing regulation under NIS2 Art. 21(5) takes precedence (§ 30(3)). For the EU-level picture see NIS2 penetration testing and vulnerability assessment requirements.
Where German rules name a penetration test
| Text | Who it applies to | What it says | How often | |
|---|---|---|---|---|
| BSIG § 30 (NIS2) | About 29,500 important and particularly important entities | Assess the effectiveness of measures; handle vulnerabilities. No penetration test named | Not set | |
| BSI KRITIS criteria, no. 95 | Operators of critical facilities | Penetration tests by qualified internal staff or external providers, documented method | At least yearly | |
| DORA Art. 24-25 | Financial entities, except microenterprises | Appropriate tests of ICT supporting critical or important functions; penetration testing is one listed method | At least yearly | |
| DORA Art. 26 (TLPT) | Entities identified by BaFin or the ECB | Threat-led penetration testing on live production systems | At least every 3 years | |
| BSI C5:2026, OPS-22 | Cloud providers seeking a C5 attestation | Penetration tests by qualified internal staff or external testers | At least yearly and after material changes | |
| IT-Grundschutz | Organisations applying it, federal administration | Penetration tests SOLLTE (should) at higher protection needs | Not set | |
| TISAX (VDA ISA 5.2.6) | Automotive suppliers | Penetration tests named as an example for critical systems at high protection needs | Risk-based |
Text
- BSIG § 30 (NIS2)
- About 29,500 important and particularly important entities
- BSI KRITIS criteria, no. 95
- Operators of critical facilities
- DORA Art. 24-25
- Financial entities, except microenterprises
- DORA Art. 26 (TLPT)
- Entities identified by BaFin or the ECB
- BSI C5:2026, OPS-22
- Cloud providers seeking a C5 attestation
- IT-Grundschutz
- Organisations applying it, federal administration
- TISAX (VDA ISA 5.2.6)
- Automotive suppliers
Who it applies to
- BSIG § 30 (NIS2)
- Assess the effectiveness of measures; handle vulnerabilities. No penetration test named
- BSI KRITIS criteria, no. 95
- Penetration tests by qualified internal staff or external providers, documented method
- DORA Art. 24-25
- Appropriate tests of ICT supporting critical or important functions; penetration testing is one listed method
- DORA Art. 26 (TLPT)
- Threat-led penetration testing on live production systems
- BSI C5:2026, OPS-22
- Penetration tests by qualified internal staff or external testers
- IT-Grundschutz
- Penetration tests SOLLTE (should) at higher protection needs
- TISAX (VDA ISA 5.2.6)
- Penetration tests named as an example for critical systems at high protection needs
What it says
- BSIG § 30 (NIS2)
- Not set
- BSI KRITIS criteria, no. 95
- At least yearly
- DORA Art. 24-25
- At least yearly
- DORA Art. 26 (TLPT)
- At least every 3 years
- BSI C5:2026, OPS-22
- At least yearly and after material changes
- IT-Grundschutz
- Not set
- TISAX (VDA ISA 5.2.6)
- Risk-based
How often
- BSIG § 30 (NIS2)
- BSI KRITIS criteria, no. 95
- DORA Art. 24-25
- DORA Art. 26 (TLPT)
- BSI C5:2026, OPS-22
- IT-Grundschutz
- TISAX (VDA ISA 5.2.6)
Summarized from the texts as read on 17 November 2026. The KRITIS criteria catalogue and IT-Grundschutz are BSI documents, not statute. Check the official text and your auditor's reading before you rely on a frequency.
Critical facilities: evidence every three years, penetration tests every year
Operators of critical facilities (“Betreiber kritischer Anlagen”) carry an extra duty under § 39 BSIG: they prove their measures to the BSI through security audits, reviews or certifications every three years. Under the old § 8a(3) the cycle was two years. The results, including the deficiencies found, go to the BSI, which can demand a remediation plan. Missing or late evidence can cost up to EUR 1 million.
The binding procedure document (GAiN, version 2.2 of 9 July 2026) lists audit methods in general terms and names no penetration test. The explicit requirement is in the BSI's criteria catalogue for these audits, the “Konkretisierung der Anforderungen” (version 1.2, 10 September 2024), requirement 95, RB-18: the operator has penetration tests carried out at least once a year, by qualified internal staff or external providers, following a documented test method, and findings of medium to very high criticality are tracked and fixed. This catalogue is an audit yardstick, not statute, and it still carries the old section number in its title.
Two more points for these operators:
- Attack detection. Systems for attack detection are mandatory (§ 31(2)) and part of the three-yearly evidence.
- BSI orders. The BSI may order audits or tests by independent bodies at particularly important entities (§ 61(1)).
The KRITIS-Dachgesetz of 11 March 2026 (in force 17 March 2026) covers physical resilience. It contains no IT test duty and leaves IT security to the BSIG. On 17 November 2026 we could not confirm that the ordinance defining critical facilities under that law was in force; until it is, the previous definition continues to apply (§ 66 BSIG).
Finance: DORA, BaFin and the Bundesbank
For banks, insurers, investment firms and other financial entities, DORA has applied since 17 January 2025 and replaces the national circulars. BaFin repealed KAIT, VAIT and ZAIT at the end of 16 January 2025; BAIT remains only for institutions not yet under DORA and is fully repealed at the end of 31 December 2026.
- Yearly testing (Art. 24). Financial entities other than microenterprises ensure, at least yearly, that appropriate tests are conducted on all ICT systems and applications supporting critical or important functions. Tests are run by independent parties, internal or external.
- Test types (Art. 25). The list of appropriate tests includes vulnerability assessments and scans, network security assessments, scenario-based tests and penetration testing. Penetration testing is one listed method.
- TLPT (Art. 26). Identified entities carry out threat-led penetration testing at least every three years, on live production systems. The detailed rules are in Delegated Regulation (EU) 2025/1190.
In Germany, BaFin is the TLPT authority for the entities it supervises: it identifies them, orders the test and validates the scope. The ECB covers significant institutions. The Deutsche Bundesbank's TIBER team accompanies each test and confirms it was conducted properly. More in DORA penetration testing requirements beyond TLPT and TLPT.
BSI guidance: IT-Grundschutz and the pentest guides
The BSI's own material is what German auditors and tenders refer to.
- IT-Grundschutz-Kompendium (Edition 2023). Penetration tests appear as SOLLTE (should) requirements, mostly for higher protection needs. OPS.1.1.6.A14: for applications and IT systems with higher protection needs, penetration tests should be used as a test method. APP.3.1.A22 and APP.3.2.A16 cover web applications and web servers, NET.3.1.A23 and NET.3.2.A24 routers, switches and firewalls. None is a basic MUSS requirement.
- Praxis-Leitfaden für IS-Penetrationstests (version 1.2, 2016). Defines black-box and white-box tests and states that the BSI recommends white-box testing as a rule. It sets three test depths, from technical security audit to invasive vulnerability scan. We found no BSI document that defines grey box.
- Durchführungskonzept für Penetrationstests. The older study, marked by the BSI as still current, classifies tests by six criteria, including information base, aggressiveness, scope and starting point (from outside or from inside).
- Certified providers. The BSI certifies companies as IT security service providers for IS penetration tests; its list has 22 entries. Certification of individual testers has ended and was replaced by a recognition of external certificates.
If a contract or tender asks for a test “nach BSI” (per BSI), it usually means these documents: agree the classification, the test depth and the starting point in writing.
Cloud, automotive, public portals and health apps
A few German rules name penetration tests directly:
- Cloud: BSI C5:2026. Criterion OPS-22 requires the cloud provider to run penetration tests at least yearly and after material changes to the service, by qualified internal staff or external testers, with each relevant component covered at least once in three years under multi-year plans. C5:2026 applies to attestations starting on or after 1 June 2027; C5:2020 can be used until then.
- Automotive: TISAX. In the VDA ISA catalogue (6.0.3, and ISA2027 for assessments ordered from 1 January 2027), control 5.2.6 asks for regular system and service audits and, at high protection needs, names “human penetration tests” as an example for critical systems. Control 5.3.1 names penetration testing as an example for custom software at very high protection needs.
- Public administration portals. Under the ITSiV-PV, internet-facing components and those with high protection needs undergo a penetration test and a web check to BSI specifications before they connect to the Portalverbund, repeated after three years at the latest or after major changes.
- Digital health applications (DiGA). The manufacturer must have run a penetration test of the listed version, including all backend components, following the BSI's concept.
For energy (§ 5c EnWG) and telecoms (§ 165 TKG) the statutes mirror NIS2 and name no penetration test; the detail is in the Bundesnetzagentur's security catalogues, which are under revision.
Compliance checklist
- Establish your category: important, particularly important, operator of a critical facility, DORA entity, or a sector regime (energy, telecoms).
- Check that the BSI registration is complete and current; changes are due within two weeks.
- Write down how you assess the effectiveness of your measures (§ 30(2) Nr. 6): method, scope, frequency, who decides.
- For critical facilities: plan penetration tests at least yearly and keep the method documented for the three-yearly evidence.
- For DORA entities: map critical or important functions to ICT systems and test them at least yearly; check whether BaFin has identified you for TLPT.
- Classify each test in BSI terms: information base, aggressiveness, scope, starting point.
- Sign a written authorisation naming period, targets and depth, including third-party systems.
- Track findings of medium criticality and above to closure and retest the fix.
- Keep the evidence where your auditor can verify it: who tested what, when, with which result.
- Brief management: they must oversee the measures and attend training (§ 38).
Where Zero Hunt fits
Zero Hunt is an autonomous AI red team on an on-premise appliance: it runs black-box and gray-box penetration tests of networks and infrastructure from inside your data centre, on its own models, with a human in the loop for sensitive actions. No external AI service is called and no finding leaves the appliance.
- Effectiveness, on a schedule. Campaigns repeat after changes and on a calendar, which gives § 30(2) Nr. 6 a documented procedure and gives critical-facility operators material between the yearly tests and the three-yearly evidence.
- Retest after a fix. The same campaign runs again and shows whether the path is closed.
- Evidence. Every attack attempt is a signed entry in a hash chain per campaign, verifiable offline.
- Mapping. Findings are mapped to 34 frameworks, including NIS2, DORA, TIBER-EU and ISO 27001.
What it is not: the engine has no mapping for BSI IT-Grundschutz, C5, TISAX or the BSI's KRITIS criteria catalogue, so tying a report to those stays in your documentation. Zero Hunt is not a BSI-certified IT security service provider, does not perform the § 39 audit and does not replace a TLPT, which needs threat intelligence and testers under the BaFin and Bundesbank process. See the on-premise AI red team and the on-premise pentest platform buyer's guide.
Questions
Does NIS2 require penetration tests in Germany? Not by name. The BSIG requires vulnerability handling and procedures to assess whether the measures are effective (§ 30(2) Nr. 5 and 6), and leaves the method open. Penetration tests are the common way to show effectiveness; the law sets no frequency.
How often must a KRITIS operator run penetration tests? The BSI's criteria catalogue for the audits expects them at least once a year (requirement 95). The evidence itself goes to the BSI every three years under § 39 BSIG.
Is BAIT still in force? Only for institutions that are not yet under DORA. It is fully repealed at the end of 31 December 2026. KAIT, VAIT and ZAIT ended on 16 January 2025.
Who runs TLPT in Germany? BaFin identifies the entities and orders the test; the ECB does so for significant institutions. The Bundesbank's TIBER team accompanies every test. The entity commissions the threat intelligence and the testers.
Does the BSI recommend black-box or white-box tests? Its practical guide recommends white-box tests as a rule, because they find more in the same time. Black-box tests show what an outsider can reach.
Must the penetration tester be BSI-certified? The BSIG does not require it. The BSI guide says providers should preferably be certified, and public bodies connecting to the Portalverbund must use the BSI, state authorities or BSI-certified providers.
Can an automated or autonomous platform cover these duties? It can cover regular, documented testing and retesting of networks and infrastructure. It does not replace the auditor's § 39 evidence, a TLPT, or the manual tests of business logic that a human tester performs.
Sources
- BSI-Gesetz (BSIG), full text
- § 30 BSIG, risk-management measures
- § 39 BSIG, evidence duties of operators of critical facilities
- BSI: NIS2 implementation law in force (5 December 2025)
- BSI: NIS2 in figures
- BSI: Konkretisierung der Anforderungen, v1.2 (KRITIS criteria)
- BSI: GAiN v2.2, evidence procedure
- KRITIS-Dachgesetz
- Regulation (EU) 2022/2554 (DORA)
- Delegated Regulation (EU) 2025/1190 (TLPT)
- BaFin: DORA and the repeal of the IT circulars
- BaFin: TLPT
- BSI IT-Grundschutz-Kompendium, Edition 2023
- BSI: Praxis-Leitfaden für IS-Penetrationstests
- BSI: Studie Durchführungskonzept für Penetrationstests
- BSI: certified IT security service providers for penetration tests
- BSI C5:2026
- ENX: VDA ISA (TISAX)
- ITSiV-PV § 2
- DiGAV, Anlage 1
- § 202a StGB
Goes deeper
- NIS2 penetration testing and VA requirements →
- DORA penetration testing requirements beyond TLPT →
- TLPT: threat-led penetration testing under DORA Art. 26 →
- Penetration testing requirements by regulation →
- On-premise pentest platform buyer's guide →
- Pentera, NodeZero and Cymulate alternatives →
- Partner program: distributors and resellers →
Want this against your environment?
Book a 30-minute scoping call — we will map this directly to your current compliance scope and threat profile.