What the law asks of you
Duty of care
You assess your own risks and take appropriate measures: access management, multi-factor authentication, backup and recovery, patch management, monitoring, supplier management, awareness and a tested incident process.
Reporting duty
A significant incident requires an early warning within 24 hours, a fuller report within 72 hours and a final report within a month. You only make that with a process that is in place beforehand.
Board accountability
Directors must understand the risks and be able to show that oversight exists. Outsourcing to an IT provider does not shift that responsibility.
Frequently asked questions
What counts as a significant incident?
In short: an incident with substantial consequences for your service, for example prolonged downtime or a high-impact data breach. In the incident process we record in advance who makes that judgement, so it is not up for debate during a crisis.
Does ISO 27001 make us automatically NIS2 compliant?
No, but it saves a lot of work. ISO 27001 covers a large part of the measures and provides the management process the law expects. The additional points are in the reporting duty, the supply chain and board accountability.
What does a NIS2 project cost?
That depends on where you start. We do the baseline assessment for a fixed price; after that you know which measures are needed and what they cost. Many measures are already part of the blends.
Can you file the reports for us?
We help determine whether to report and what it should say, and supply the technical evidence. Filing itself remains the organisation's responsibility.
Do you know where you stand?
The NIS2 check takes two minutes and shows which obligations apply to you and where the biggest gaps are.