Regulation · IT security · SMEs
NIS2 for small IT companies and freelancers: thresholds, deadlines, duties
The German NIS2 implementation act has been in force since 6 December 2025. Whether a company is directly affected depends on sector and size – but small firms feel it as suppliers too.
The key facts
| Topic | According to the source |
|---|---|
| In force | 6 December 2025 (promulgated 5 December 2025, BGBl. I No. 301) |
| Particularly important entities | from 250 employees, or turnover above €50 million and balance sheet above €43 million |
| Important entities | from 50 employees, or turnover and balance sheet each above €10 million |
| Extra condition | membership of a sector listed in Annex 1 or 2 |
| BSI registration | within three months; for entities already covered by 6 March 2026 |
| Reports for significant incidents | early warning 24 hours, notification 72 hours, final report no later than one month after |
| Fines | up to €10 million (particularly important) or €7 million (important entities) |
Important: size alone does not decide. Only the combination of a threshold and a sector makes a company a regulated entity. When unsure, the BSI’s self-assessment helps – and, if in doubt, legal advice.
And if I am below the thresholds?
A freelancer or micro-company is usually below 50 employees and therefore not directly affected – that is my reading of the thresholds, not legal advice. NIS2 still becomes noticeable through the supply chain: affected customers have to keep an eye on risks at their service providers and will ask for evidence, for example on access control, backups and incident handling. A commentary on the draft bill (usd, 2024) explicitly lists supply-chain security, vulnerability handling, backup and business continuity, access control and multi-factor authentication among the measures; whether the final wording says the same should be checked in the law.
Practical evidence worth having anyway
- Backups with a tested restore: see backup the 3-2-1 way and the restore test.
- Access control and multi-factor login: how I do it in the homelab, see zero trust for the homelab.
- Traceable delivery: a documented CI/CD pipeline shows how changes reach production.
- A plan for security incidents: who is informed when? Closely related to the CRA reporting duty.
Sources and limits
- ADVISORI: NIS2 implementation act (consultancy blog; entry into force, thresholds, deadlines, fines)
- usd: NIS-2, the key points (commentary on the 2024 draft, used only for the list of measures)
- The Federal Law Gazette is binding; neither source is an official text.
Not legal advice. I am a developer, not a lawyer. The details come from the sources listed (as of October 2026); the legal text is what counts.
Keep reading
Homelab · Backup · Proxmox
Backup the 3-2-1 way and the restore test: a backup only counts once it has been restored
Most backup stories end at the same point: the backup ran – but nobody ever tested whether it can be restored. Here is how I back up my Proxmox host and how I test the restore without endangering anything running.
Regulation · Security · DevOps
CRA reporting duty from 11 September 2026: 24 hours, 72 hours, 14 days
Since 11 September 2026, manufacturers of products with digital elements must report actively exploited vulnerabilities – in three stages and on a fixed clock. What this means for development and DevOps teams.
DevOps · Cloudflare · Zero Trust
Zero Trust for the homelab: Cloudflare Tunnel and Access instead of open dashboards
An internal dashboard was publicly reachable via a subdomain. Here is how I locked it down with Cloudflare Tunnel, Cloudflare Access and Tailscale.
Access · Security · Backup
Reaching and protecting a home server: Tailscale, Cloudflare Tunnel, vzdump
A home server is only as good as its access and its backups. My principle: no port forwarding, every access path a conscious decision, a backup every day.
More from practice
Find more notes, case studies and projects on the homepage.
All notes Case study MeisterMeld Case study PflegeOasis Case study Kernbohr-Expert Back to the homepage
Comments
Join the discussion: comments run on GitHub Discussions (sign in with a GitHub account). Content from GitHub/giscus is only loaded after you click. Privacy