Demonstrate the effectiveness of the protective measures
Since the beginning of December 2025, NIS-2 has been legally binding in Germany, and the crucial question is no longer whether companies have security measures in place, but whether they are effective and whether this can be proven.
This post updates our article on NIS-2 Directive on the current legal situation. It shows what the amended BSI law requires, which of the ten minimum measures are mandatory. DEFENDERBOX Technically supported and why the efficacy test is the most important lever.
What has changed
The EU directive has become German law: The obligations are now directly set out in the BSI Act (BSIG), and affected companies must implement them.
The main duties include:
- Registration with the BSI: The deadline has now expired. Anyone who has not registered yet should do so immediately.
- Report of significant security incidents: They must report to the BSI within fixed deadlines, starting with a first report within 24 hours. This requires a well-established process.
- Responsibility of the management: She must approve and monitor the measures, undergo training, and may be personally liable in the event of violations of her duties.
- Ten minimum measures in risk management: They are regulated in § 30, paragraph 2 of the BSIG.
The law requires „appropriate, proportionate and effective“ technical and organizational measures. In addition, compliance must be documented. The word „effective“ is the key to the rest of this contribution.
The ten minimum measures and the contribution of the DEFENDERBOX
Four of the ten minimum measures are supported by the DEFENDERBOX directly and technically (Nos. 1, 5, 6 and 9), four others in addition (Nos. 2, 4, 8 and 10); in two cases the contribution remains indirect (Nos. 3 and 7).
|
No. |
Minimum measure pursuant to § 30, paragraph 2, BSIG |
Contribution by DEFENDERBOX |
|---|---|---|
|
1 |
Risk analysis and IT security |
Strong: Vulnerability analyses, automated pentests, attack paths, AD audits, and darknet research provide technical evidence |
|
2 |
Handling security incidents |
In addition: Recognizes technical risks and critical vulnerabilities; incident response and reporting processes remain organizational tasks |
|
3 |
Operational maintenance, backup, recovery, crisis management |
Indirectly: does not replace a backup or BCM system, but detects vulnerabilities that could endanger operation |
|
4 |
Security of the supply chain |
In addition: Systems from service providers can be examined within the agreed scope of testing; evaluation, contracts, and control remain organizational matters. |
|
5 |
Acquisition, development and maintenance of IT including vulnerability management |
Strong: The core function of the DEFENDERBOX: Scans and pentests reveal vulnerabilities and actually exploitable attack paths |
|
6 |
Assessment of the effectiveness of the risk management measures |
Strong: Repeatable pentests and scans objectively verify whether technical security measures are effective |
|
7 |
Training and awareness raising |
Indirectly: The results are well suited as material for awareness, a training platform does not replace the DEFENDERBOX. |
|
8 |
Cryptographic methods |
In addition: detects weak encryption, insecure protocols, and misconfigurations; the company itself sets the cryptography policy |
|
9 |
Personnel security, access control, management of ICT systems |
Strong in the technical field: AD/IAM audits, credential attacks, and attack path analyses reveal weaknesses in identities and permissions |
|
10 |
Multi-factor authentication and secure communication |
In addition: shows weaknesses in authentication and access protection; the DEFENDERBOX does not provide MFA and communication systems |
Risk analysis & vulnerability management (No. 1 and 5)
The DEFENDERBOX provides the technical evidence for the risk analysis and carries out the entire cycle of vulnerability management.
No. 1 – Risk analysis. A company must know where its actual cyber risks lie. The DEFENDERBOX goes beyond a purely organizational analysis here: it examines the technical infrastructure using vulnerability analysis as well as internal and external penetration tests. NodeZero simulates real attacks and shows which security gaps can actually be exploited and which attack paths an attacker can use to get in.
No. 5 – Vulnerability management. The legislator explicitly requires security measures when acquiring, developing and maintaining IT systems, including the management of vulnerabilities. The DEFENDERBOX examines the following aspects:
- external and internal vulnerabilities,
- external and internal pentests,
- Active-Directory configurations,
- Exposed access data and information in the Darknet.
The tests can be repeated repeatedly. This creates the classic cycle: find → evaluate → fix → retest. The DEFENDERBOX thus supports the legal requirement that the deployment of patches and change management remain the responsibility of the company.
Effectiveness testing – the most important lever (No. 6)
No. 6 explicitly calls for „concepts and procedures for evaluating the effectiveness of risk management measures,“ and it is precisely here that the DEFENDERBOX makes its strongest contribution.
Having a firewall, EDR, MFA, or network segmentation is not enough. A company must also be able to assess whether these measures actually work. This is a paradigm shift: away from describing what is present, towards asking what an attacker can still achieve with it.
|
So far: describe the measures |
Better: Evaluate effectiveness |
|---|---|
|
Firewall present |
Can an attacker still penetrate? |
|
MFA activated |
Can he obtain access data? |
|
Network segmented |
Can he move laterally in the net? |
|
SMB configured |
Can he compromise further systems? |
|
AD hardened |
Can he access privileged accounts? |
The left column describes implemented measures; whether they are sufficient in an emergency is not stated. The right column can be answered with the DEFENDERBOX, up to the question of how vulnerable the IT is as a whole. Based on this, the right measures can be specifically defined and implemented.
The statement „We have implemented security measures“ thus becomes more reliable: „We have examined whether our security measures actually work against realistic attack scenarios.“ Repeatable penetration tests and vulnerability analyses are the instrument for this, and their reports document the results.
What the DEFENDERBOX does not do
The DEFENDERBOX does not make a company NIS-2 compliant alone, and it is not a „NIS-2 compliance solution“.
That is why the ten requirements are too extensive: they contain numerous specifications regarding governance, processes, training, business continuity and organization, which cannot be replaced by a testing tool. The DEFENDERBOX instead supports companies in the technical implementation and, above all, in the verifiable effectiveness testing of central risk management measures.
This is precisely what distinguishes a solution with repeatable pentests from products that provide a single protective measure: it examines how several measures, when combined, can withstand realistic attacks. It is this assessment that NIS-2 requires.
Conclusion
NIS-2 not only demands measures, but the evidence that they work; and for that, regular, verifiable technical inspections are needed.
The DEFENDERBOX makes these tests practical for small and medium-sized businesses: it shows where an attacker could actually infiltrate, prioritizes the recommended actions, and documents whether countermeasures have been effective. Anyone who wants to know what their own network looks like can start with the free security initial analysis.
Companies from the financial sector find the appropriate classification for their duties in our contribution to DORA (available online on December 3, 2026).
Are you prepared for cyber attacks?
Stay vigilant – your IT is with us!
Image generated by AI