Why mid-size organizations can no longer ignore NIS2 and DORA
NIS2 expanded the scope of EU cybersecurity regulation far beyond critical infrastructure operators — it now covers mid-size manufacturers, logistics providers, healthcare organizations, and digital service providers. DORA does the same for financial entities and their critical ICT third parties. Both regulations share a common thread: they no longer accept "we have a firewall" as evidence of risk management. They require a documented, auditable risk management process.
If your organization falls under either framework, 2026–2027 is the period where enforcement moves from theoretical to real. Supervisory authorities are actively requesting evidence, not just policies.
What NIS2 actually requires
NIS2 mandates a risk-based approach to cybersecurity, which in practice means:
- Risk analysis and information system security policies — a living risk register, not a one-off PDF.
- Incident handling procedures — with defined roles, escalation paths, and reporting timelines (24h early warning, 72h full report).
- Supply chain security — assessing and monitoring risks introduced by suppliers and service providers.
- Business continuity and crisis management — backup management, disaster recovery, and crisis response plans.
- Governance accountability — management bodies must approve risk management measures and can be held personally liable for non-compliance.
What DORA adds for financial entities
DORA builds on the same foundation but focuses specifically on ICT risk in financial services:
- ICT risk management framework — a documented framework covering identification, protection, detection, response, and recovery.
- Digital operational resilience testing — regular testing, including threat-led penetration testing for larger entities.
- Third-party ICT risk management — a register of all contractual arrangements with ICT providers and concentration risk analysis.
- Incident reporting — harmonized major ICT-incident reporting to regulators.
The real gap: evidence, not intent
Most mid-size organizations already do some of this informally. The gap regulators actually penalize is the inability to prove it: no versioned risk register, no control testing history, no traceable link between a risk, its controls, and remediation actions. A spreadsheet survives a self-assessment; it rarely survives an audit request for evidence spanning the last 12 months.
This is exactly where a structured risk register and a Three Lines of Defense model help — see our guide on the Three Lines of Defense model for how to split ownership between risk owners, oversight, and internal audit so NIS2/DORA accountability requirements are actually met.
How a modern ERM platform makes this manageable
Instead of rebuilding your risk register for every audit, a platform like Reesk lets you:
- Maintain a single, versioned risk register with full audit trail — exactly what NIS2/DORA evidence requests look for.
- Link ICT and supplier risks directly to controls and run structured testing cycles.
- Track remediation actions with owners and deadlines, so overdue items are visible before an auditor finds them.
- Generate board-ready reports that demonstrate governance accountability in minutes, not weeks.
If you are still managing this in spreadsheets, read our guide on how to build a risk register as a starting point.
Get ahead of the 2026–2027 enforcement wave
Waiting for a regulator letter is the most expensive way to discover a gap. Start free on Reesk and have a compliant, auditable risk register in place before enforcement activity ramps up. See plans on our pricing page — the free plan is enough to get your first risks and controls documented today.
