Services Training Communities About Insights Contact
← Back to RambiCo
RambiCo

A cyber security roadmap the board can steer on

As interim CISO at Ctac and KenterGroendus, one of the first deliverables was a security strategy with a roadmap. The trap is familiar: a long list of technical projects that the board approves once and never looks at again. A roadmap only works when directors can use it to make choices.

How I build one

Start with the business. Which processes, customers and obligations matter most? What risk is the board willing to accept? Those answers set the priorities, not the latest tool.

Measure where you stand. A maturity baseline against a recognised framework such as ISO 27001, with the NIS2 duties alongside, shows the gaps in plain terms.

Group the work into a few themes. Five to seven themes across people, process and technology, each with an owner. Governance and awareness belong on the roadmap as much as monitoring and identity.

Plan in horizons. Quick wins in the first months build trust. Larger changes follow in year one and beyond, in an order the organisation can absorb.

Report on progress and risk, not activity. A handful of indicators per quarter tells the board whether risk is going down, and where a decision is needed.

A good roadmap fits on one page in the boardroom, with the detail underneath for the teams that carry it out.

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

  1. Settle the scope and get it confirmed by the board.
  2. Organise board approval of the measures, and board training.
  3. Set up and rehearse the incident reporting process, with the 24 and 72 hour steps.
  4. Put security requirements in supplier contracts, starting with the critical ones.
  5. Use one control framework: an ISO 27001 ISMS gives NIS2 the structure and the evidence it needs.

A final EE-ISAC plenary as board member

At EE-ISAC’s second plenary meeting of 2018, held on 6 and 7 June in Glasgow, Johan Rambi attended his last meeting as a board member of the organization he helped launch. The moment closed a chapter that began with the DENSEK project in 2013 and the formal launch of EE-ISAC in December 2015.