NIS2 and ISO 27001 gap assessments: what we find, and what to fix first
NIS2, implemented in the Netherlands through the Cyberbeveiligingswet, raises the bar for a large group of organisations. In recent assignments, including the NIS2 programme and ISO 27001 recertification at KenterGroendus and NIS2 compliance at Ctac, the same findings come back.
What we typically find
Scope is unclear. Which entities, services and sites fall under NIS2, and are OT environments in or out?
The overview of assets and suppliers is incomplete. Especially OT systems and cloud or managed service suppliers are missing.
Incident reporting is not ready for the deadlines. NIS2 asks for an early warning within 24 hours of a significant incident, a notification within 72 hours and a final report within a month.
The board is not yet in the loop. Under NIS2 the management body approves and oversees the risk management measures and follows training. That is new for many boards.
Policy exists, evidence does not. Documents are in place, but proof that controls work is hard to show.
What to fix first
- Settle the scope and get it confirmed by the board.
- Organise board approval of the measures, and board training.
- Set up and rehearse the incident reporting process, with the 24 and 72 hour steps.
- Put security requirements in supplier contracts, starting with the critical ones.
- Use one control framework: an ISO 27001 ISMS gives NIS2 the structure and the evidence it needs.