← zabolotny.de
DEENRUUA

Home / Notes

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.

Serge Zabolotny ·

The key facts

TopicAccording to the source
In force6 December 2025 (promulgated 5 December 2025, BGBl. I No. 301)
Particularly important entitiesfrom 250 employees, or turnover above €50 million and balance sheet above €43 million
Important entitiesfrom 50 employees, or turnover and balance sheet each above €10 million
Extra conditionmembership of a sector listed in Annex 1 or 2
BSI registrationwithin three months; for entities already covered by 6 March 2026
Reports for significant incidentsearly warning 24 hours, notification 72 hours, final report no later than one month after
Finesup 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

Sources and limits

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.

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

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