NIS2UmsuCG · in force since 6 Dec 2025
If the BSIG as amended by the NIS2UmsuCG applies to you, you must register with the BSI and prove risk management under Art. 21 NIS2. We deliver the technical part: a pentest with a report that follows the requirements catalogue.
What counts is sector, headcount and financial figures. Headcount OR the financial figures are enough; for the financial figures, turnover AND balance sheet total must both be exceeded.
Qualified trust service providers, TLD registries and certain telecom providers are covered regardless of size.
A significant security incident triggers a three-stage reporting process with the BSI.
A brief notice on whether the incident is suspected to result from unlawful acts or has cross-border effects.
Assessment of severity and impact, plus initial indicators of compromise.
Description of the incident, root cause analysis and the countermeasures taken.
Art. 21(2) NIS2, transposed nationally as section 30(2) BSIG, names ten areas of measures. Letter f requires a procedure for assessing how effective your measures are. That is exactly what an independent test is.
Example findings. Every finding gets its place in the catalogue (a to j), together with severity and a remediation measure.
NIS2 does not prescribe a testing method, but it does require demonstrable technical measures. The pentest is the recognised instrument for that. Without regular tests, if something happens, the burden is on you to show that you did enough.
NIS2 sets no testing interval. A full test at regular intervals makes sense, plus one after significant IT changes such as new systems, restructuring or incidents.
In a free 30-minute initial consultation we clarify the scope. After that you receive a fixed-price offer.