NIS2 checklist 2026 with measures, reporting deadlines and management duties

The registration in the BSI portal is done and the confirmation email has arrived. The next morning, the managing director of a logistics company with 300 employees asks what is still missing. The honest answer from IT, “most of it”, does not help him. He needs a list he can tick off, with a piece of evidence behind every tick.
This checklist follows the German BSI Act as amended by the NIS2 Implementation Act, which has applied since 6 December 2025. For each item it sets out what the law requires, what evidence holds up and where companies usually fall short. For the legal background, see our guide on NIS2 in Germany. We also send you the full list as a printable PDF by email.
Key takeaways
- The checklist starts with scope. Every legal entity is checked on its own, not the group.
- Registration with the BSI is due within three months. For companies in scope on 6 December 2025, the deadline was 6 March 2026.
- Section 30 BSIG lists ten areas of measures. They have to be appropriate, proportionate and effective, and you have to document them.
- Significant incidents are reported in stages, within 24 hours, 72 hours and one month.
- Management has to implement the measures, oversee their implementation and attend training. That is Section 38 BSIG.
- A tick only counts with evidence. If you hold ISO 27001 or TISAX®, much of that evidence can be reused.
Step 1: Check scope for each legal entity
The law asks two questions of every entity. Does it provide a service listed in Annex 1 or Annex 2 of the BSI Act, and is it large enough? Under Section 28 BSIG, medium-sized companies with 50 or more employees, or more than 10 million euros in turnover and balance sheet, are important entities. Large companies in an Annex 1 sector are particularly important entities. Group figures count unless the entity runs its IT independently.
You can tick this item once there is a short written rationale for each entity: its activity and the matching annex entry, its size figures, the result, the date and who signed it off. Our guide on checking NIS2 applicability per entity goes through the details.
Common gap: the check was done once for the whole group and never repeated. An acquisition, a new service or a new set of annual accounts can change the answer.
Step 2: Register with the BSI
Section 33 BSIG requires registration no later than three months after an entity first falls, or falls again, into scope. If you have not registered yet, do it now.
Registration has two stages. First the entity needs an ELSTER organisation certificate through Mein Unternehmenskonto, the federal business account, which requires a German tax number. Then it registers in the BSI portal. You provide, among other things, the name and legal form, contact details including public IP address ranges, the sector under Annex 1 or 2, and the member states in which you provide services. Changes have to be reported within two weeks of you becoming aware of them.
Evidence: the portal confirmation for every entity in scope, and a named person who keeps the data current. Common gap: the certificate sits with the finance team and nobody in IT can log in to the portal. That matters, because incident reports go through the same portal.
Step 3: The ten measures under Section 30 BSIG
Section 30(1) BSIG requires technical and organisational measures that are appropriate, proportionate and effective. Proportionality takes into account your exposure to risk, the size of the entity, the cost of implementation, and the likelihood and severity of incidents. You have to document compliance. Section 30(2) lists ten areas as a minimum and calls for an all-hazards approach, so power cuts, fire and human error count as well as attacks.
Some digital providers fall primarily under Implementing Regulation (EU) 2024/2690 instead, including cloud computing providers, data centre service providers, managed service providers, managed security service providers and online marketplaces (Section 30(3) BSIG). If your entity is one of them, check the list below against the regulation's more detailed annex.
1. Risk analysis and information security policies
Required: policies for risk analysis and for the security of your IT. Common gap: the risk analysis looks at servers and applications but not at the services the company actually provides to its customers.
2. Incident handling
Required: a process to detect, assess, contain and resolve incidents. Common gap: the process exists but has no criteria for “significant” and no step for the 24-hour report.
3. Business continuity
Required: backup management, disaster recovery and crisis management. Common gap: backups run every night, but nobody has ever tested a full restore. Often the backups are tied to the same directory service as the production systems.
4. Supply chain security
Required: security in the supply chain, including the security aspects of relationships with direct suppliers or service providers. Common gap: there is a supplier list, but no rating by criticality and no security clauses in the contracts.
5. Acquisition, development and maintenance
Required: security when buying, developing and maintaining systems, including vulnerability handling and disclosure. Common gap: patches get installed, but without deadlines by severity. And there is no way for outsiders to report a vulnerability they have found.
6. Assessing effectiveness
Required: policies and procedures to assess whether the measures work. Common gap: the measures are written down and nothing is measured. One internal audit a year and a few metrics, such as the patch backlog, are a start.
7. Cyber hygiene and training
Required: basic training and awareness measures on IT security. Article 21(2)(g) of the NIS2 Directive also names basic cyber hygiene practices. Common gap: a single session during onboarding and nothing after that. Or management is exempt from the mandatory training.
8. Cryptography
Required: policies and processes for the use of cryptographic methods. Common gap: encryption is in use, but no document says which algorithms are allowed or who manages the keys. The BSI's Technical Guideline TR-02102 is a useful reference.
9. HR security, access control and asset management
Required: human resources security, access control and management of ICT systems, products and processes. Common gap: access is granted but never reviewed. Leavers' accounts stay active, and SaaS tools signed up for by departments are missing from the inventory.
10. MFA and secured communication
Required: multi-factor or continuous authentication, secured voice, video and text communication and, where appropriate, secured emergency communication. Common gap: MFA covers employees but not admin accounts, service accounts or a supplier's remote maintenance access. And nobody knows how the crisis team will talk if email and chat are down.
The evidence auditors want to see
A tick on its own will not convince the BSI or an auditor. What holds up are documents with a date, an owner and traces from day-to-day operations. An ISO 27001 ISMS already produces much of this; it just needs mapping to the right NIS2 measure.
A TISAX® label helps too, because the information security module of VDA ISA builds on ISO/IEC 27001. Watch the scope, though. TISAX® is assessed per site, while NIS2 applies to the whole legal entity. What is usually missing is the NIS2-specific layer: registration, reporting deadlines, management duties and a mapping that shows which control covers which measure. Our guide on multi-framework control mapping walks through that step.
Reporting: 24 hours, 72 hours, one month
An incident is significant if it has caused or can cause severe operational disruption or financial loss, or if it affects others through considerable material or immaterial damage. Reports go through the BSI portal to the joint reporting office of the BSI and the BBK. The clock starts when you become aware of the incident.
The early warning states whether you suspect an unlawful or malicious act and whether cross-border effects are possible. The 72-hour notification adds an initial assessment of severity and impact; the final report covers root cause and remediation.
On the checklist, that means:
- Significance is defined in writing, with examples from your own operations.
- One person decides whether to report, and a deputy can be reached at weekends too.
- At least two people can log in to the BSI portal and know where the credentials are kept.
- Templates for each stage are ready, so nobody is drafting wording at three in the morning.
- The process has been rehearsed, with timestamps in the record.
Under Section 35 BSIG, the BSI can also instruct you to inform the recipients of your services about a significant incident. Agree in advance who does that, and how.
Management duties under Section 38 BSIG
Management has to implement the measures under Section 30 and oversee their implementation (subsection 1). If it culpably breaches that duty and the entity suffers a loss, it is liable under the company law that applies to its legal form (subsection 2). Its members have to attend training regularly, so they can identify and assess risks and risk management practices (subsection 3). The law sets no fixed interval. The BSI covers content and scope in a guidance paper from April 2026 and a curriculum for management training from October 2026.
Article 20 of the NIS2 Directive says the management body approves the measures. The German Section 38 does not use that word. A documented management decision still makes sense, because without one it is hard to show that management knows the measures and oversees them.
- A management decision on the measures, dated and minuted.
- Regular reporting on the status of each measure. Twice a year is a good minimum.
- Training records for every member of management, not only the one responsible for IT.
Evidencing the supply chain through contracts
Measure 4 is evidenced mainly through contracts. Start by deciding which suppliers are critical: who has access to your systems or data, and whose outage would stop your operations? Then check their contracts for security requirements, incident notification duties, audit rights, rules on subcontractors and exit. Our guide to NIS2 clauses in supplier contracts sets out the clauses in detail.
At GetTeddy, contract analysis supports this review. It maps contract clauses to the requirements of Article 21(2)(d) NIS2, Article 28 GDPR and Article 30 DORA. Uncertain assessments go to an approver in your team.
The checklist as a PDF
The NIS2 checklist PDF contains every item from this article, with columns for status, evidence and legal basis, a section on reporting deadlines and one on management duties. It reflects the law as of November 2026.
A completed list shows one day. Three months later there is a new admin account without MFA, and a supplier contract has been renewed without its security annex. That is why the GetTeddy Gap Audit checks your documents against the framework, and a dedicated compliance engineer stays with you through to the audit.
Frequently asked questions
Does the BSI publish an official NIS2 checklist?
Yes. The BSI provides a NIS-2 checklist on its website, along with material on individual measures and on reporting. Use them as the primary source; our list adds evidence and the ISO 27001 mapping.
Is ISO 27001 certification enough for NIS2?
Not on its own. It covers a large part of the technical and organisational measures if its scope includes the entity in question. Registration, reporting deadlines and management duties come on top.
Is there a NIS2 certificate?
No. The BSI can require particularly important entities to have audits, inspections or certifications carried out by independent bodies (Section 61 BSIG). Operators of critical facilities have to provide evidence every three years (Section 39 BSIG). The law does not provide for a certificate that confirms NIS2 compliance as such.
When do I need a lawyer?
When your classification is disputed, for example over the IT independence of a group subsidiary, or when the BSI writes to you. A checklist is not legal advice.
Where to start
Begin with the items that carry a deadline: scope, registration and the reporting process. An incident will not wait for the gap analysis to finish. Then work through the ten measures, starting from the controls you already have.
Our NIS2 page shows how GetTeddy runs the checklist as an ongoing programme, and our how it works page explains who does which part of the work.



