NIS-2 and data backup: which backup obligations now apply
The new BSI Act has applied since December 2025. What Section 30 BSIG requires for backup and recovery, who is affected and how to implement the obligations verifiably.
Since 6 December 2025, the new BSI Act (BSIG, the German Act on the Federal Office for Information Security) has required particularly important and important entities to take risk management measures that explicitly include ‘backup management and disaster recovery’. The Act does not specify how often, where to or with which tests you must back up - it requires appropriate, proportionate and effective measures that should comply with the state of the art, and compliance must be documented. Commission Implementing Regulation (EU) 2024/2690 is more specific: it applies directly to certain digital services and serves as guidance for everyone else.
In this guide, you will learn where implementation stands in October 2026, who is affected, what the backup provisions require word for word and how to derive an auditable backup concept from them.
Note: This article provides general guidance and does not replace legal advice. Whether and how your company is affected should be assessed in each individual case.
Where does NIS-2 stand in October 2026?
The German NIS-2 Implementation and Cybersecurity Strengthening Act (NIS2UmsuCG) has revised the BSIG; it entered into force on 6 December 2025. According to the BSI (Germany’s Federal Office for Information Security), there is no general transition period: the obligations have in principle applied since that day.
- Registration: Entities concerned must register with the BSI no later than three months after they are first deemed to be affected (Section 33 BSIG). For companies that were already affected when the Act entered into force, this deadline ended on 6 March 2026. Registration takes two steps: first via ‘Mein Unternehmenskonto’ (MUK, the German federal company account) with an ELSTER organisation certificate, then in the BSI portal, which has been open since 6 January 2026.
- Status of registrations: The BSI estimates that around 29,500 entities are affected. According to the BSI, around 17,700 companies had registered by 30 June 2026.
- If you have missed the deadline, you should register without delay. Failure to register, or late registration, can be punished with a fine of up to €500,000 (Section 65(5) no. 5 BSIG).
- EU level: On 20 January 2026, the European Commission proposed amendments to the NIS-2 Directive. Until these are transposed into German law, the BSIG applies in its current version.
Is your company affected by NIS-2?
The decisive factors are sector and size (Section 28 BSIG). The sectors are listed in Annexes 1 and 2 of the BSIG and include energy, transport, health, water, digital infrastructure (such as cloud and data centre services, managed service providers), waste management, chemicals, food and parts of manufacturing such as mechanical engineering, vehicle manufacturing and the manufacture of electrical and electronic products.
| Category | Size threshold (sectors in the Annexes) |
|---|---|
| Important entity | at least 50 employees or annual turnover and annual balance sheet total each exceeding €10 million (Annexes 1 and 2) |
| Particularly important entity | at least 250 employees or annual turnover exceeding €50 million and annual balance sheet total exceeding €43 million (Annex 1) |
| Regardless of size | including operators of critical facilities, qualified trust service providers, TLD registries, DNS service providers |
Figures are calculated in accordance with the European Commission’s SME Recommendation (2003/361/EC); data from partner or linked enterprises is not added if your company is independent of them in the design and operation of its IT (Section 28(4)). The BSI’s anonymous NIS-2 impact check provides an initial assessment; its result is expressly not legally binding.
Many smaller companies are indirectly affected through the supply chain. The BSI points out that the rules of the BSIG can also have an indirect effect on companies that are not covered themselves, through their business relationships. In practice, customers send security questionnaires or ask for evidence of backup and emergency preparedness. A documented backup concept is then an advantage.
What does Section 30 BSIG require for backups?
Section 30(1) BSIG requires entities to take ‘appropriate, proportionate and effective technical and organisational measures’. When assessing proportionality, factors include the exposure to risk, the size of the entity, the cost of implementation and the likelihood and severity of security incidents. Important: compliance must be documented (Section 30(1) sentence 3).
The measures ‘should comply with the state of the art’ and take relevant European and international standards into account (Section 30(2)). For backups, these points of the minimum catalogue are particularly relevant (quoted in our translation):
- No. 3: ‘business continuity, such as backup management and disaster recovery, and crisis management’
- No. 4: ‘supply chain security, including security-related aspects concerning the relationships with direct suppliers or service providers’
- No. 6: ‘policies and procedures to assess the effectiveness of risk management measures in the field of information technology security’
- No. 8: ‘policies and processes regarding the use of cryptographic procedures’
- No. 9: ‘development of policies for human resources security, access control and the management of ICT systems, products and processes’
- No. 10: ‘use of multi-factor authentication or continuous authentication solutions’ as well as secured communications
What the Act does not prescribe: a specific backup rule such as 3-2-1, immutable storage, fixed test intervals or particular products. These points only follow from the state of the art, from standards and from your own risk analysis.
What does Implementing Regulation (EU) 2024/2690 say about backups?
Implementing Regulation (EU) 2024/2690 applies directly only to DNS service providers, TLD registries, providers of cloud computing and data centre services, content delivery network providers, managed service providers, managed security service providers, online marketplaces, search engines, social networks and trust service providers. For these entities, it takes precedence under Section 30(3) BSIG. Please note: if your IT service provider is itself a managed service provider within scope, these requirements apply to it directly.
For all other companies, the Regulation is not binding, but useful guidance, because it describes what ‘backup management’ can look like in concrete terms. Point 4.2 of the Annex (‘Backup and redundancy management’) requires backup plans based on the risk assessment that cover the following:
- recovery times
- complete and accurate backup copies, ‘including configuration data and data stored in cloud computing service environments’
- storage ‘(online or offline) in a secure location or locations, which are not in the same network as the system, and are at sufficient distance’
- physical and logical access controls to the backup copies
- restoring data from backup copies
- retention periods based on business and regulatory requirements
In addition, there are regular integrity checks of the backups (point 4.2.3) and regular restore tests, whose results are documented and followed up with corrective actions where necessary (point 4.2.6). Point 4.1 calls for a business continuity plan with recovery objectives. Further sections cover cryptography including key management (point 9) as well as multi-factor authentication and administrative accounts (point 11).
What obligations does management have?
Under Section 38 BSIG, management must implement the risk management measures and monitor their implementation. If it breaches this duty, it is liable to the entity for culpably caused damage under the rules of company law. In addition, management must regularly attend training in order to be able to assess risks and risk management practices. The BSI provides training materials for this purpose.
Significant security incidents must be reported to the BSI (Section 32 BSIG): an early warning within 24 hours at the latest, an incident notification with an initial assessment within 72 hours at the latest and a final report no later than one month after that notification.
The BSI can order audits of particularly important entities and verify compliance (Section 61), and of important entities if facts indicate shortcomings (Section 62). Fines (Section 65 BSIG) can also be imposed for missing documentation:
| Infringement | Particularly important entity | Important entity |
|---|---|---|
| Measures under Section 30 not taken, not documented, report not submitted | up to €10 million; with total turnover above €500 million, up to 2% of worldwide turnover | up to €7 million; with total turnover above €500 million, up to 1.4% of worldwide turnover |
| Registration not made or not made in time | up to €500,000 | up to €500,000 |
How do you implement the backup obligations in practice?
The following overview translates the requirements into concrete measures and shows which documents you can present during an audit or in response to a customer enquiry. It is intended as guidance, not as an exhaustive catalogue.
| Requirement | Practical implementation | Evidence |
|---|---|---|
| Backup management (Section 30(2) no. 3) | Backup concept: systems, backup type, frequency, retention, responsibilities | approved concept with version status |
| Recovery objectives | Derive RPO (tolerable data loss) and RTO (tolerable downtime) for each system from a business impact analysis | system list with RPO/RTO, reconciled with backup plans |
| Separate storage | at least one copy outside your own network and site, e.g. in a cloud repository | job logs, location details from the service provider |
| Protection against tampering | immutable copy or recycle bin for deleted backups, separate credentials | documented configuration and retention periods |
| Cryptography (no. 8) | Encryption in transit and at rest, controlled key custody | cryptography concept, documented and protected key escrow |
| Access control and MFA (nos. 9, 10) | dedicated administrative accounts for the backup, MFA, least privilege | authorisation concept, record of regular access reviews |
| Check effectiveness (no. 6) | regular restore tests, automated and manual | test reports with date, duration, result, corrections |
| Supply chain (no. 4) | Assess backup service providers: DPA, data centre certification, location, incident reporting channels | register of service providers, contracts, certificates |
| Crisis management | Business continuity plan with restart sequence, also available offline | business continuity plan, exercise records |
We describe how to set up and document restore tests in our guide Testing restores. You can read why an immutable copy is so important against ransomware in Immutable backups against ransomware.
How do IT-Grundschutz CON.3 and Art. 32 GDPR fit in?
The BSI module CON.3 Backup Concept (IT-Grundschutz Compendium, 2023 edition) is a practical template for what Section 30 requires in general terms: among other things, it requires you to define the tolerable data loss for each system, to store backups in a physically separate location, to protect them against being overwritten and to test restores regularly.
The GDPR (EU General Data Protection Regulation) sets its own requirements in parallel as soon as personal data is involved: among other things, Art. 32(1) requires the ability to restore the availability of and access to data in a timely manner in the event of an incident (point (c)), and a process for regularly testing the effectiveness of the measures (point (d)). With an external backup service provider, you also conclude a data processing agreement under Art. 28 GDPR.
Frequently asked questions
Does NIS-2 also apply to companies with fewer than 50 employees?
As a rule, no, provided that annual turnover and annual balance sheet total do not each exceed €10 million. Exceptions apply, among others, to operators of critical facilities, qualified trust service providers and DNS service providers. Smaller companies can be affected indirectly through requirements from their customers.
Does NIS-2 prescribe immutable backups or the 3-2-1 rule?
Not literally. The BSIG names backup management as a minimum measure that should reflect the state of the art. For the entities it covers, Implementing Regulation 2024/2690 requires backups in secure locations outside the system’s network as well as access controls. Immutable off-site copies are a common way of safeguarding these requirements against ransomware.
How often do I need to test restores?
The Act does not specify a fixed interval. The Implementing Regulation refers to regular, documented tests. Set the interval on a risk basis and also test after major changes to systems or backups.
Does an external backup service provider make us NIS-2 compliant?
No. Responsibility remains with your management. A service provider can supply building blocks such as an encrypted off-site copy; the concept, tests, documentation and the assessment of the service provider itself remain your responsibility.
Conclusion
NIS-2 makes backup a management obligation, but does not prescribe any particular technology. What matters is a risk-based concept, a protected copy outside your own network, regular and documented restore tests and an assessed service provider. If you document this in a traceable way, you are as well prepared for BSI audits as for requests for evidence from customers.
We supply individual building blocks for this: with Veeam Cloud Connect, you transfer backup copies in encrypted form to our cloud repository in an ISO/IEC 27001 certified data centre in Germany. You can also encrypt with your own key and add immutability and the Veeam recycle bin ‘Insider Protection’ with a freely selectable retention period; we provide a data processing agreement under Art. 28 GDPR. With the Veeam Managed Service, we monitor your backup servers on site; response times are agreed individually in the maintenance contract. We are happy to answer your questions at hello@myveeam.cloud or on +49 8106 928 9493.
Sources
- BSI Act (BSIG) - Sections 28, 30, 32, 33, 38, 61, 62, 65 and Annexes 1/2, gesetze-im-internet.de (in German) (version of 23 July 2026)
- Implementing Regulation (EU) 2024/2690, EUR-Lex (17 October 2024)
- Directive (EU) 2022/2555 (NIS-2), EUR-Lex (14 December 2022)
- Regulation (EU) 2016/679 (GDPR), EUR-Lex (27 April 2016)
- BSI: NIS-2 regulated companies (in German) (5 October 2026)
- BSI: Second step towards NIS-2 registration - BSI portal now open (in German) (6 January 2026)
- BSI: NIS-2 in figures (in German) (30 June 2026)
- BSI: Questions and answers on NIS-2 (in German) (6 December 2025)
- BSI: NIS-2 impact check (in German) (5 October 2026)
- BSI: NIS-2 obligations (registration, reporting, risk management, management training) (in German) (5 October 2026)
- BSI: IT-Grundschutz module CON.3 Backup Concept (in German) (2023 edition)
- European Commission: Proposal amending the NIS-2 Directive, COM(2026) 13 (20 January 2026)