NIS 2-loven: NIS2 in Denmark, as the Danish law states it.
The Danish act is titled “Lov om foranstaltninger til sikring af et højt cybersikkerhedsniveau (NIS 2-loven)”. In English: Act on measures to ensure a high level of cybersecurity (the NIS 2 Act). This page describes the national law from its Danish text. It is not legal advice on whether your organisation is in scope.
Who the Act applies to
The Act distinguishes essential entities from important entities.
“Loven finder anvendelse på offentlige og private enheder, der er omfattet af lovens bilag 1 og 2, jf. dog stk. 2-5 og 7.” (§ 1(1)). In English: the Act applies to public and private entities covered by Annexes 1 and 2 of the Act, subject to subsections 2 to 5 and 7.
The exceptions include entities to the extent they are covered by the Danish Act on strengthened preparedness in the energy sector, and entities where sector-specific EU legal acts and any national implementation of them have at least the same effect as §§ 6, 12, 13 and 15 (§ 1(2) and (3)).
Essential entities. “Enheder af en type, som er omfattet af lovens bilag 1, anses for at være væsentlige enheder, hvis enheden opfylder en af følgende betingelser” (§ 4(1)). In English: entities of a type covered by Annex 1 of the Act are considered essential entities if the entity meets one of the following conditions, subject to subsections 2 and 3. The conditions are that the entity employs 250 persons or more, or has an annual turnover above EUR 50 million and an annual balance sheet above EUR 43 million. Regardless of size, essential entities also include, among others, qualified trust service providers, top-level domain name registries, DNS service providers and public administration entities of the central government (§ 4(3)).
Important entities. An entity of a type covered by Annex 1 or 2 that does not meet the criteria for an essential entity is an important entity if it employs 50 persons or more, or has an annual turnover above EUR 10 million and an annual balance sheet above EUR 10 million. Trust service providers that do not meet the criteria for essential entities are important entities whatever their size (§ 5).
Risk-management measures (§ 6)
“Væsentlige og vigtige enheder skal træffe passende og forholdsmæssige tekniske, operationelle og organisatoriske foranstaltninger for at styre risiciene for sikkerheden i net- og informationssystemer, som disse enheder anvender til deres operationer eller til at levere deres tjenester” (§ 6(1)). In English: essential and important entities must take appropriate and proportionate technical, operational and organisational measures to manage the risks to the security of network and information systems which those entities use for their operations or to provide their services.
In our English rendering, the measures must at least cover:
- policies on risk analysis and information system security;
- incident handling;
- business continuity, including backup management, disaster recovery and crisis management;
- supply chain security;
- security in acquiring, developing and maintaining network and information systems, including vulnerability handling and disclosure;
- policies and procedures to assess the effectiveness of the measures;
- basic cyber hygiene practices and cybersecurity training;
- policies and procedures on cryptography and, where relevant, encryption;
- human resources security, access control policies and asset management;
- where relevant, multi-factor or continuous authentication, secured voice, video and text communications, and secured emergency communication systems within the entity.
An entity that does not meet one or more of these requirements must take all necessary, appropriate and proportionate corrective measures without undue delay (§ 6(2)).
Management duties (§ 7)
“De foranstaltninger, som en væsentlig eller vigtig enhed træffer på baggrund af § 6, stk. 1 og 2, og regler fastsat i medfør af § 6, stk. 3, skal være godkendt af enhedens ledelsesorgan.” “Ledelsesorganet fører tilsyn med foranstaltningernes gennemførelse.” (§ 7(1)). In English: the measures an essential or important entity takes under § 6(1) and (2), and rules laid down under § 6(3), must be approved by the entity's management body. The management body oversees their implementation.
The members of the management body must take part in relevant courses on cybersecurity risk management, and encourage the entity to offer similar courses to its other employees (§ 7(2)).
Incident reporting (§§ 12, 13 and 15)
“Væsentlige og vigtige enheder skal underrette den relevante kompetente myndighed og Computer Security Incident Response Team (CSIRT) om enhver væsentlig hændelse.” (§ 12(1)). In English: essential and important entities must notify the relevant competent authority and the CSIRT of every significant incident. An incident is significant if it has caused or can cause severe operational disruption of the services or financial loss for the entity, or has affected or can affect others by causing considerable material or non-material damage (§ 12(2)).
| Step | Deadline | Section |
|---|---|---|
| Early warning | Without undue delay, at the latest within 24 hours of becoming aware of the significant incident | § 13(1)(1) |
| Incident notification | Without undue delay, in any event within 72 hours of becoming aware of it | § 13(1)(2) |
| Incident notification by a trust service provider | Without undue delay, at the latest within 24 hours of becoming aware of it | § 13(2) |
| Intermediate report | On request of the CSIRT | § 13(1)(3) |
| Final report | At the latest one month after the incident notification | § 13(1)(4) |
If the incident is still ongoing when the final report is due, the entity sends a status report at that time and a final report at the latest one month after the incident has been handled (§ 13(1)(5)).
Registration (§ 10)
Essential and important entities, and entities that provide domain name registration services, must register with the relevant competent authority, subject to § 9. They give, among other things, their name and up-to-date contact details, including email addresses, IP ranges and telephone numbers, and their sector and subsector (§ 10(1)).
“Oplysningerne efter stk. 1 skal indgives, senest 2 uger efter at enheden omfattes af loven.” (§ 10(2)). In English: the information under subsection 1 must be submitted no later than two weeks after the entity becomes covered by the Act. A change to that information is notified no later than two weeks after the date of the change (§ 10(3)).
Supervision, enforcement and fines
The competent authorities supervise essential entities' compliance. Their measures include on-site inspections without a court order on presentation of proper identification, security audits, security scans and demands for information and documentation (§ 21(1)).
For important entities, supervision is reactive: “De kompetente myndigheder fører reaktivt tilsyn med vigtige enheders overholdelse af denne lov og regler udstedt i medfør af loven.” (§ 24(1)). In English: the competent authorities carry out reactive supervision of important entities' compliance with this Act and rules issued under it.
Enforcement measures against both kinds of entity include warnings, binding instructions, and orders and prohibitions (§ 22 and § 25). For an essential entity, if measures under § 22, points 1 to 4, have proved insufficient and the entity misses the deadline the authority sets, the authority can also temporarily prohibit a person with managerial responsibilities at chief executive officer or legal representative level from exercising managerial functions in the entity (§ 23(1)). This does not apply to public administration entities (§ 23(4)).
Fines: “Med bøde straffes den, der” (§ 32(1)). In English: a fine is the penalty for anyone who breaches, among others, § 6(1) or (2), §§ 9 or 10, § 12(1), § 13(1) or (2), or § 15, or does not comply with certain decisions and orders. “Der kan pålægges selskaber m.v. (juridiske personer) strafansvar efter reglerne i straffelovens 5. kapitel.” (§ 32(2)). In English: companies and other legal persons can be held criminally liable under Chapter 5 of the Criminal Code. The text of § 32 that Ansvar serves names no fine amount.
The dates that matter
- 1 July 2025: “Loven træder i kraft den 1. juli 2025.” (§ 33(1)). In English: the Act's entry into force is set for 1 July 2025. NIS 2-loven entered into force on 1 July 2025.
- 1 October 2025: “Oplysningerne efter § 9, stk. 1, og § 10, stk. 1, skal indgives senest den 1. oktober 2025.” (§ 33(3)). In English: the information under § 9(1) and § 10(1) had to be submitted by 1 October 2025 at the latest.
For the EU directive itself, read NIS2 explained, or run the free NIS2 checker.
Frequently asked questions
Under § 1 the Act applies to public and private entities covered by its Annexes 1 and 2, with exceptions. Sections 4 and 5 then sort them into essential and important entities by type and size, and § 4(3) makes some entities essential whatever their size.
Under § 13(1), an early warning goes out within 24 hours and an incident notification within 72 hours of the entity becoming aware of the significant incident, both without undue delay. A trust service provider sends the incident notification within 24 hours. A final report follows at the latest one month after the incident notification, or, if the incident is still ongoing, one month after it has been handled, with a status report first.
Section 32 makes a breach of, among others, § 6(1) or (2), §§ 9 or 10, § 12(1) and § 13(1) or (2) punishable by a fine, and companies can be held criminally liable. The text of § 32 that Ansvar serves names no amount.
Ask NIS 2-loven with the source attached
On the free plan, your own AI client searches law and regulation through Ansvar, one jurisdiction or framework per question, and every answer carries its source.
Ask these to see the quality
Paste one into your own agent once Ansvar is connected, and check the section it quotes.
Using Ansvar, within what deadlines must an essential or important entity send an early warning and an incident notification under § 13 of the Danish NIS 2-loven? Quote the points that set the deadlines.Using Ansvar, which measures must the cybersecurity risk-management measures at least cover under § 6 of the Danish NIS 2-loven? Quote the list.Using Ansvar, what does § 7 of the Danish NIS 2-loven require of an entity's management body? Quote both subsections.