General Counsel

Apr 24, 2025

5 min. read

NIS2 directive regulations and implementation in Denmark

Share:

NIS2 directive regulations and implementation in Denmark

When the first version of the Network and Information Security Directive (NIS1) was enacted, most Danish businesses hardly noticed. It targeted a narrow set of operators in essential services like energy and telecoms. But now, as the second generation—the NIS2 Directive (Directive (EU) 2022/2555)—is on the cusp of becoming law in Denmark, the impact is significantly broader and deeper. The expansion from around 1,000 to more than 6,000 entities across 18 sectors is not just a regulatory upgrade—it’s a paradigm shift.

Let’s explore what the NIS2 Denmark transposition looks like, how Danish regulators plan to enforce it, and what organisations need to do to comply.

Key take-aways for Denmark in April 2025

Denmark has taken a pragmatic approach to NIS2: no overreaching, no gold-plating. The general law, NIS-2-loven” (Bill L 141), sets the framework for most sectors, while separate, sector-specific bills tweak existing rules for telecoms, finance, and energy. The goal is consistency with the EU directive, tailored to the Danish regulatory landscape.

Here’s a breakdown of where things currently stand:

Overview of Denmark’s NIS2 implementation strategy

ThemeStatus
General legislationBill L 141 covers 15 sectors; lighter sectoral bills cover finance, telecom, energy
TimelineIn force 1 July 2025; mandatory self-registration by 1 October 2025
Scope expansionFrom ~1,000 entities under NIS1 to ~6,000 under NIS2
Entity classesEssential (VE) and Important (VI) based on size and sectoral relevance
SanctionsVE: up to €10m/2% global turnover; VI: up to €7m/1.4%; daily penalties, public naming
Reporting duties24h alert → 72h update → 30-day final report via CFCS/NIS portal
GovernanceMinistry for Society Security & Preparedness (MSSB); sector agencies lead supervision

This centralised yet sector-aware framework provides the foundation for robust cyber resilience—without burdening businesses unnecessarily.

Relevant deadlines and timeline for implementation

Denmark is following a clear legislative path, and while deadlines are tight, they are transparent. The NIS2 law is currently going through its final parliamentary reading, with implementation scheduled to begin this summer.

Denmark NIS2 implementation timeline

DateMilestoneStatus
6 Feb 2025General (L 141) and telco (L 142) bills tabled in parliament✔ Completed
7 Mar 2025First reading concluded✔ Completed
14 Apr 2025Committee report adopted✔ Completed
29 Apr 2025Third reading scheduled⏳ Pending
Mid-May 2025Royal assent & publication in Lovtidende⏳ Expected
1 Jul 2025Acts enter into force; CFCS portal goes live⏳ Upcoming
1 Oct 2025Deadline for mandatory entity self-registration⏳ Critical deadline
Jan 2026Initial audits by CFCS and sector authorities begin⏳ Future milestone

The Denmark NIS2 directive enters the operational phase mid-year, meaning companies should now be deep into readiness mode.

How Denmark is implementing the NIS2 directive

The general legislation (L 141) provides a unified baseline across sectors, while respecting existing regulatory infrastructures where they exist. This means the Danish Energy Agency, Financial Supervisory Authority (FSA), and telecommunications regulators maintain domain-specific oversight with NIS2-aligned rules.

Crucially, organisations must self-assess and self-register by 1 October 2025. This means understanding whether they are a “Væsentlig enhed” (VE – Essential Entity) or “Vigtig enhed” (VI – Important Entity), based on thresholds such as:

  • VE: ≥ 250 full-time employees or €50 million turnover
  • VI: ≥ 50 employees or €10 million turnover

Telecoms, DNS providers, and trust services are automatically included regardless of size.

The governance structure delegates overall coordination to the Ministry for Society Security and Preparedness, while the Centre for Cybersecurity (CFCS) becomes the national incident coordinator and EU point of contact.

Sanctions and executive responsibility

Denmark has chosen to strictly follow the NIS2 penalty model without extending its reach—monetary sanctions, daily penalties, and management bans are all on the table for private sector entities.

Sanctions under Denmark’s NIS2 law

Entity typeFine ceilingOther penalties
VE€10 million or 2% global turnoverLicence suspension, executive bans, public naming
VI€7 million or 1.4% turnoverDaily penalties, corrective orders
PublicNo monetary finesCorrective directives only

The Companies Act has been amended to include executive liability. If boards fail to approve and oversee a proper cybersecurity programme, they risk personal sanctions. In other words, cyber governance is now a boardroom-level responsibility.

Impact on key industries

The scope of NIS2 Denmark implementation stretches far beyond traditional critical infrastructure. Newly regulated sectors now include food production, manufacturing, and digital service providers.

Sector-specific NIS2 obligations in Denmark

SectorChange from NIS1New requirements
ManufacturingNewly regulatedOT/IT segmentation, supplier clauses, annual penetration tests
EnergyTweaks to existing rulesSBOMs, KPI reporting to Danish Energy Agency
HealthcareBroadened scope (labs, medium hospitals)ISO 27001 governance, quarterly backups, 24h reporting
Digital InfraNow fully covered regardless of size24/7 SOC, zero-trust frameworks, critical-vendor registry
FinanceMerged with DORATLPT, third-party tracking, dual incident reporting
Public SectorMandatory for large municipalities, etc.Appoint CISO, comply with CFCS standards, but exempt from fines

This means virtually every medium-to-large Danish enterprise in these sectors must now adopt formalised risk management frameworks.

What Danish companies should do now

Preparation is critical. Fortunately, Danish authorities are providing practical support tools. The CFCS and MSSB offer a self-assessment tool (currently in beta) to help organisations determine their obligations. Businesses should also gather their registration data—including CVR number and NACE code—well before the 1 October deadline.

Key action steps include:

  • Conducting a gap analysis against Article 21 of the directive (risk controls mapped to ISO 27001)
  • Preparing an incident response SOP aligned with CFCS, sector CERTs, and GDPR timelines
  • Documenting board approval of cybersecurity strategies to mitigate personal risk

Engagement at executive and operational levels will be essential in avoiding financial penalties and reputational damage.

Is your organisation ready for July?

The countdown to the Denmark NIS2 directive going live is in its final phase. With transposition legislation nearly complete and regulatory infrastructure in place, businesses must now shift from awareness to action. This directive isn’t just about ticking compliance boxes—it’s about embedding cyber resilience into the DNA of your operations.

By aligning your governance practices and IT capabilities with the NIS2 mandate, your organisation can not only avoid sanctions but also strengthen its position in an increasingly interconnected, vulnerable digital ecosystem. The opportunity is just as great as the obligation.

For the latest updates and resources, keep an eye on MSSB’s official portal and CFCS guidance, and make sure your leadership team is informed and engaged. Because this time, cyber readiness isn’t optional—it’s law.

Automate Your Cybersecurity and Compliance

It's like an in-house cybersecurity & compliance team for a monthly subscription! No prior cybersecurity or compliance experience needed.

Share this article

Post on Linkedin
Post on Facebook
Post on X

How useful was this post?

0 / 5. 0

General Counsel

He is regulatory compliance strategist with over a decade of experience guiding fintech and financial services firms through complex EU legislation. He specializes in operational resilience, cybersecurity frameworks, and third-party risk management. Nojus writes about emerging compliance trends and helps companies turn regulatory challenges into strategic advantages.
  • DORA compliance
  • EU regulations
  • Cybersecurity risk management
  • Non-compliance penalties
  • Third-party risk oversight
  • Incident reporting requirements
  • Financial services compliance

Explore further