Managed IT
NIS2 readiness without the panic
The compliance officer got an email. Nobody knew exactly what NIS2 was, including the IT vendor at the time.
A Dutch supplier to the health sector came to us saying they "had to do something with NIS2". The compliance officer didn't know how much work it was. The director didn't know if it was this month or this year.
By the numbers
weeks to compliance baseline
open findings at the baseline scan
open finding after implementation
The situation
NIS2 catches far more Dutch SMBs than expected in 2024: mid-sized suppliers to essential sectors (health, energy, transport, finance) and a long tail of service providers in the chain. The rule asks for concrete measures, a policy, a designated responsible person, and evidence that it actually runs.
Many organisations start too late, buy an expensive compliance tool nobody operates, or pay a consultant for a report that ends up in a drawer. This client wanted none of those three.
What we did
Quickscan in two weeks. We mapped which measures were already covered by existing systems (often more than clients think), what was missing, and what counted as acceptable risk.
The gaps were manageable: MFA missing on a handful of systems, incident logging not meeting the notification duty, and no written-down responsible person. Implementation took six weeks: MFA across the board, a log pipeline producing structural evidence, and a one-page document the board signs.
No separate compliance tool purchased, existing systems were enough.
What it delivered
After the quickscan and implementation:
- Quickscan completed in 11 working days, clear view of gaps and what was acceptable. - Implementation in six weeks, within the original quote. - A one-page summary for the board, plus the underlying technical documentation an inspector can ask for. - Monthly monitoring that kept running after the quickscan, otherwise "ready" is a single point in time. - No extra software license bought.
The board had first feared this would be a big project. It became one with an end date.
What this wasn't
Not 200 pages of report. Not a mandatory six-figure compliance platform. Not a "you are fully NIS2 compliant" stamp, that doesn't exist and we don't issue it. What it was: a defendable file an inspection can be walked through.
Related cases
A 20-50 person SMB without an in-house IT team
One person "who also does something with IT", three different vendors, and nobody who has the overview.
ReadDocuments that get retyped three times
A quote starts in the CRM, gets retyped into Word, then into the accounting system, and arrives by email as a PDF.
Read