NIS2 Checklist: Checking the Measures under Section 30 BSIG
Under Section 30 BSIG (the BSI Act), particularly important and important entities must implement and document appropriate, proportionate and effective technical and organisational measures, in at least ten areas set out in law: from risk analysis through business continuity and the supply chain to multi-factor authentication. This checklist translates the ten areas into specific check points and lists typical evidence. This lets you see quickly where your company stands.
You can clarify whether your company is affected at all with our guide Checking NIS2 applicability. You will find a complete overview of all obligations on the page NIS2 consulting.
How to use the checklist
Rate each check point with a simple traffic light: implemented and documented, partly implemented or open. What matters is not only whether a measure exists, but whether you can provide evidence of it. Operators of critical facilities must provide evidence of implementation every three years (Section 39 BSIG). From December 2028, the BSI (Federal Office for Information Security) can request evidence from other particularly important entities (Section 61 (3) BSIG); for important entities, it carries out checks if facts indicate shortcomings (Section 62 BSIG). Without documentation, a measure is considered not implemented if in doubt.
The checklist does not replace a gap analysis. It provides initial guidance and helps you set priorities.
The principles of Section 30 BSIG
Before looking at individual measures, four principles apply to all of them:
- Appropriate, proportionate, effective: The decisive factors include risk exposure, size, implementation costs and the likelihood and severity of possible incidents.
- Documentation: Compliance must be documented (Section 30 (1) sentence 3 BSIG).
- State of the art and standards: The measures should comply with the state of the art and take relevant European and international standards into account, such as ISO/IEC 27001.
- All-hazards approach: This covers not only cyber attacks, but also physical events, technical failures and human error.
For certain digital providers, such as cloud services, data centres and managed service providers, the technical requirements of Implementing Regulation (EU) 2024/2690 take precedence.
Checklist: the ten minimum measures
1. Policies on risk analysis and IT security
- Information security policy adopted by management
- Assets (information, systems, applications, service providers) recorded and protection requirements determined
- Documented risk analysis procedure, carried out regularly (at least once a year is common)
- Risk treatment with owners and deadlines, residual risks accepted by management
Typical evidence: policy, asset register, risk analysis, risk treatment plan
2. Incident handling
- Process for detecting, assessing and handling security incidents, with clear roles
- Escalation paths and availability, including outside business hours
- Criteria for when an incident is significant and therefore reportable
- Follow-up with lessons learned
Typical evidence: incident response process, incident logs, exercise reports
3. Business continuity
- Backup concept, for example based on the 3-2-1 principle, with at least one offline copy
- Restoration tested regularly
- Emergency and recovery plans for critical processes
- Crisis organisation and emergency communication defined
Typical evidence: backup concept, logs of restoration tests, emergency manual, business impact analysis. The article Building BCM shows how to set up business continuity management in a structured way.
4. Supply chain security
- Overview of suppliers and service providers with access to systems or data
- Assessment of suppliers by criticality
- Security requirements and reporting obligations in contracts
- Regular review, for example via certificates, questionnaires or audits
Typical evidence: supplier register, assessments, contract clauses. More detail in the article NIS2 and the supply chain.
5. Security in acquisition, development and maintenance
- Security requirements in procurement policies
- Secure development, if software is developed in-house
- Vulnerability and patch management with defined deadlines
- Process for handling reported vulnerabilities
Typical evidence: procurement policy, patch reports, vulnerability overview, penetration test results
6. Assessing effectiveness
- Information security metrics defined, such as open vulnerabilities or time to remediation
- Internal audits or independent reviews
- Regular reports to management
- Actions from reviews followed up
Typical evidence: audit reports, metrics reports, management review
7. Training and awareness
- Mandatory training for all employees, repeated regularly
- Awareness measures, such as phishing simulations
- Rules of conduct for handling information and IT
- Participation documented
Typical evidence: training plan, attendance records, policies. Training for management is a separate obligation (see below).
8. Cryptography
- Requirements for encrypting stored and transmitted data
- Current, recognised methods in use
- Key management defined
Typical evidence: cryptography concept, overview of methods in use
9. Human resources security, access control, asset management
- Authorisation concept based on the principle of least privilege
- Regular review of authorisations
- Defined processes for employees joining, changing roles and leaving
- Privileged access specially protected and logged
Typical evidence: authorisation concept, recertification logs, onboarding and offboarding checklists
10. Multi-factor authentication and secured communication
- MFA for remote access, administration and critical systems
- Secured voice, video and text communication within the company
- Secured emergency communication in case the normal channels fail
Typical evidence: MFA coverage, communication policy, emergency communication plan
Cross-cutting obligations: registration, reporting, management
In addition to the ten measures, the BSIG requires further obligations that must not be missing from any NIS2 review:
- Registration with the BSI via Mein Unternehmenskonto (MUK, the German federal company account) and the BSI portal (Section 33 BSIG)
- Reporting process for significant security incidents: 24 hours, 72 hours, final report after one month (Section 32 BSIG)
- Management implements and monitors the measures, decisions are recorded (Section 38 (1) BSIG)
- All members of management trained regularly, participation documented (Section 38 (3) BSIG)
You will find details on management's duties and training in the article NIS2 and management, and on the reporting process in the article NIS2 reporting obligations.
Evaluation and next steps
If you have many open points, that is no reason to panic, but it is a reason to act: the obligations have applied since 6 December 2025 with no transition period. Proceed in this order:
- Immediately Registration, reporting process and informing management, because this is where failures lead to fines most quickly.
- In the short term Risk analysis, backup and restoration, MFA and patch management, because they reduce the greatest risk most quickly.
- In the medium term A management system that brings all areas together and runs them on a permanent basis.
For the third step we usually recommend an ISMS based on ISO 27001, onto which the NIS2 requirements are mapped. The article NIS2 and ISO 27001 shows how the mapping works. The guide Introducing an ISMS describes the path to a management system.
How SDG supports you
- Applicability assessment together with lawyers from our team
- Gap analysis against Section 30 BSIG and ISO 27001 with a prioritised action plan
- Building an ISMS based on ISO 27001 as an all-inclusive package or classic consulting
- External information security officer who steers the measures on an ongoing basis: external information security officer
- Penetration tests of your web applications, APIs and cloud environments, and ongoing vulnerability analysis via our security portal
- Training for employees and management: training
You will find all services on the page NIS2 consulting.
Frequently asked questions about the NIS2 checklist
Which measures does NIS2 require in Germany?
Section 30 (2) BSIG lists ten minimum areas: risk analysis and IT security policies, incident handling, business continuity, supply chain security, security in acquisition, development and maintenance, assessing effectiveness, training, cryptography, human resources security and access control, and multi-factor authentication and secured communication.
Do I have to implement all ten measures?
Yes, all ten areas are minimum requirements. How far implementation has to go in each area, however, depends on the principle of proportionality, i.e. on risk exposure, size, costs and possible impact.
Does implementation have to be documented?
Yes. Section 30 (1) BSIG expressly requires compliance with the measures to be documented. Without documentation, implementation cannot be demonstrated to the BSI.
Is the checklist sufficient as evidence for the BSI?
No. The checklist is intended for self-assessment. What counts as evidence are the documented measures themselves, such as risk analysis, policies, test logs and reports, ideally brought together in an ISMS.
Is ISO 27001 mandatory to comply with NIS2?
No. The BSIG does not prescribe a standard, but it does require relevant standards to be taken into account. An ISMS based on ISO 27001 covers a large part of the requirements and makes documentation easier, but does not replace registration, the reporting process and management's duties.
How often should I check the implementation status?
The law does not specify a fixed interval. It makes sense to review at least once a year and after major changes, such as new systems, service providers or security incidents.
Sources: Section 30 BSIG, BSI: information for NIS2-regulated companies, BSI: training for management
Note: This article provides general information and does not replace legal advice in individual cases.