NexGenio
Home Academy Insights Contact

Your board is now personally liable. Nobody gave them a way to see the risk.

4 September 2026

NIS2 Article 20(2) is unambiguous. Management bodies are personally liable for overseeing cybersecurity risk management. The directive does not assign this duty to the CISO, the IT department, or a compliance team. It assigns it to the board.

So the board asks to see the risk.

The CISO prepares a 47-slide deck. It covers threat vectors, vulnerability scan results, patching cadence, SIEM alert volumes, and a colour-coded heat map. The presentation is thorough, technically sound, and entirely opaque to anyone whose expertise sits outside information security. The board listens, asks a few clarifying questions, and approves the report. The item moves to the next agenda slot.

Oversight just became a signature on a page.

This pattern repeats in organisations across every sector now falling under NIS2 scope. The board carries personal liability for a domain it was never equipped to evaluate. Directors are expected to oversee risk they cannot interpret, challenge assumptions they lack the framework to test, and make informed decisions using material designed for a different audience entirely. The gap is structural. It sits between the technical reality of cybersecurity posture and the decision language a board uses to govern.

That gap is where liability accumulates.

When a regulator investigates after an incident, the question will be straightforward: did the management body exercise effective oversight? Approving a slide deck the board could not meaningfully interrogate does not meet that threshold. Personal liability under Article 20(2) demands demonstrable competence and genuine engagement with the risk landscape. A NIS2 Lead Implementer programme builds exactly this competence, equipping leaders to bridge the distance between technical controls and governance accountability.

The missing piece in most organisations is a translation layer. Technical teams understand the risk in granular detail. The board understands strategic consequence, financial exposure, and operational continuity. These two languages describe the same reality from different positions. Without architecture that connects them, the board governs blind, and the CISO presents into a vacuum.

NexGenio builds the governance architecture that closes this gap. Risk is restructured into board-level decision language: strategic exposure mapped to business objectives, quantified impact scenarios tied to financial thresholds, and clear escalation criteria the board can act on with confidence. Every reporting cycle gives directors the means to evaluate, challenge, and direct. Oversight becomes a functioning control, grounded in material the board is equipped to use.

The result is a leadership team that meets its Article 20(2) obligations with substance. Directors see cybersecurity risk in terms they can govern. CISOs present to an audience that engages with the content. And the organisation replaces ceremonial approval with informed decision-making at the highest level.

Personal liability demands personal understanding. NexGenio delivers the structure that makes both possible.

Related
Continue reading
17 September 2026

DORA gates 22 of its 41 articles on criticality. It never says how to measure it.

Twenty-two of the forty-one substantive articles of the DORA technical standard change depending on whether a function is critical or important. The regulation specifies no method for deciding that, and the same is true of the risk tolerance level two further articles are built on.

Read article →
16 September 2026

The Cyberbeveiligingswet is live. We are opening the Netherlands.

The Dutch NIS2 implementation entered into force on 15 August 2026. More than 8,000 organisations are now in scope, each with a register entry to maintain and a management body that signs for it. NexGenio is now serving the Dutch market.

Read article →
16 September 2026

Your patch policy says 30 days. The turbine says no.

The IT security playbook assumes systems can be patched, rebooted, and restored. Industrial control systems run physical processes where none of those assumptions hold. ISA/IEC 62443 is the standards series built for that difference.

Read article →