Law / Norway

Norway

In the European Economic Area 59 EU instruments the EEA Joint Committee has incorporated into the EEA Agreement apply in Norway:
  1. Database Directive, Sui Generis Right and Lawful-User Exceptions (2000)
  2. e-Commerce Directive (2000)
  3. e-Commerce Directive, Liability of Intermediary Service Providers (Articles 12 to 15) (2000)
  4. ePrivacy Directive (2004)
  5. Cookie Directive (2004)
  6. ePrivacy Directive (2004)
  7. Directive 2001/29/EC on the harmonisation of certain aspects of copyright and related rights in the information society (InfoSoc Directive) (2005)
  8. Directive 2009/24/EC on the legal protection of computer programs (Software Directive), Articles 1, 4, 5 and 6 (2011)
  9. Consumer Rights Directive (2014)
  10. Commission Regulation on Personal Data Breach Notification by Electronic Communications Providers (Regulation (EU) No 611/2013) (2016)
  11. GDPR Article 22, Automated Individual Decision-Making (2018)
  12. GDPR Article 9, Special Categories of Personal Data (2018)
  13. GDPR Articles 12-21, Data Subject Rights (2018)
  14. GDPR Articles 33-34, Breach Notification (2018)
  15. GDPR Articles 51-59, 68-76 and 77-84, Supervisory Authorities, Penalties and Remedies (2018)
  16. GDPR Chapter V, Cross-Border Transfer Restrictions (2018)
  17. General Data Protection Regulation (GDPR), Comprehensive Regime (2018)
  18. General Data Protection Regulation, Principles Relating to Processing of Personal Data and Accountability (Article 5) (2018)
  19. General Data Protection Regulation, Records of Processing Activities (Article 30) (2018)
  20. Fourth Anti-Money-Laundering Directive: Reporting of Suspicious Transactions to the Financial Intelligence Unit and Prohibition of Disclosure (Articles 33 and 39) (2019)
  21. Japan Adequacy Decision, Commission Implementing Decision (EU) 2019/419 (2019)
  22. MiFID II Algorithmic Trading Controls: Resilient Systems, Testing, Kill Functionality, Records and Notification (Article 17 and RTS 6) (2019)
  23. MiFID II Product Governance for Manufacturers and Distributors of Financial Instruments (Articles 16(3) and 24(2) and Delegated Directive 2017/593 Articles 9 and 10) (2019)
  24. MiFID II Suitability Assessment for Investment Advice and Portfolio Management, Including Automated and Semi-Automated Systems (Article 25(2) and Delegated Regulation 2017/565 Article 54) (2019)
  25. MiFID II and MiFIR Records of Services, Activities, Orders and Transactions (Article 16(6) and MiFIR Article 25) (2019)
  26. MiFID II (2019)
  27. Capital Requirements Directive, Robust Governance Arrangements of Institutions (Article 74(1)) (2020)
  28. In Vitro Diagnostic Medical Devices Regulation, Software Development, Information Security and IT Security Information Requirements (2020)
  29. Medical Devices Regulation, Software Development, Information Security and IT Security Information Requirements (2020)
  30. Trade Secrets Directive, Articles 2 to 5 (trade secret definition, lawful and unlawful acquisition, use and disclosure) (2021)
  31. United Kingdom Adequacy Decision, Implementing Decision (EU) 2021/1772 as renewed by Implementing Decision (EU) 2025/2574 (2022)
  32. Payment Services Technical Standards on Strong Customer Authentication, Personalized Security Credentials and Common and Secure Open Standards of Communication (2022)
  33. Republic of Korea Adequacy Decision, Commission Implementing Decision (EU) 2022/254 (2022)
  34. Radio Equipment Directive, Network, Privacy and Fraud Protection Requirements for Internet-Connected Radio Equipment (2022)
  35. Consumer Protection Cooperation (CPC) Regulation, Article 9(4), point (g) (power of a competent authority to remove content, restrict access to an online interface or order a domain name deleted) (2023)
  36. General Safety Regulation, Protection of Vehicles Against Cyberattacks (Annex II, Item D4) (2024)
  37. Unfair Commercial Practices Directive, Annex I point 23a (reselling event tickets acquired by automated means that circumvent a purchase limit) (2024)
  38. EU-US Data Privacy Framework Adequacy Decision, Commission Implementing Decision (EU) 2023/1795 (2024)
  39. Ecodesign Regulation for Servers and Data Storage Products, Firmware and Security Updates (2024)
  40. European Electronic Communications Code (2025)
  41. Audiovisual Media Services Directive (AVMSD), Article 7b (Overlay and modification of audiovisual media services) (2025)
  42. Audiovisual Media Services Directive (AVMSD), Articles 6a and 28b (2025)
  43. Audiovisual Media Services Directive, accessibility of media services to persons with disabilities (2025)
  44. Commission Delegated Regulation (EU) 2022/1645, External Reporting of Information Security Incidents and Vulnerabilities (IS.D.OR.230) (2025)
  45. Commission Delegated Regulation (EU) 2022/1645, Information Security Management System for Design, Production and Aerodrome Organizations (Part-IS.D.OR) (2025)
  46. Commission Implementing Regulation (EU) 2023/203, External Reporting of Information Security Incidents and Vulnerabilities in Aviation (IS.I.OR.230) (2025)
  47. Commission Implementing Regulation (EU) 2023/203, Information Security Management System for Aviation Organizations (Part-IS.I.OR) (2025)
  48. DORA Technical Standards on ICT Risk Management Tools, Methods, Processes and Policies and the Simplified ICT Risk Management Framework (2025)
  49. DORA Technical Standards on the Classification of ICT-Related Incidents and Cyber Threats and the Materiality Thresholds for Major Incidents (2025)
  50. DORA, Article 19 (reporting of major ICT-related incidents), with the time limits of Delegated Regulation (EU) 2025/301 (2025)
  51. DORA, Articles 24-27 (Digital Operational Resilience Testing and Threat-Led Penetration Testing) (2025)
  52. DORA, Articles 28-30 (ICT Third-Party Risk Management) (2025)
  53. DORA, Articles 31-44 (Oversight of Critical ICT Third-Party Service Providers) (2025)
  54. DORA, Articles 5-16 (ICT Risk Management Framework) (2025)
  55. Crypto-Asset Service Providers, Records of Communication with Clients (2025)
  56. Ecodesign Regulation for Smartphones and Tablets, Operating System Updates (2025)
  57. DORA Technical Standards on the Standard Forms, Templates and Procedures for Reporting Major ICT-Related Incidents and Notifying Significant Cyber Threats (2026)
  58. European Patent Organisation Adequacy Decision, Commission Implementing Decision (EU) 2025/1382 (2026)
  59. L-Category Vehicles, Protection Against Cyberattacks Under UN Regulation No 155 (Annex XVIII to Delegated Regulation (EU) No 44/2014) (2026)
Each reaches Norway through the EEA Agreement rather than as EU law, and the rest of the law on the European Union page does not bind here unless the Joint Committee incorporates it. For a concern in Norway, read the instrument there and the law of Norway, described on this page below.

17 of 19 named instruments researched to a stage, across five of the ten areas of law we track: 16 in force and 1 proposed. As of .

When each starts14 of 17 carry a date, 3 do not.
2015: 1 instrument (1 in force) ’15 2016: 0 instruments 2017: 0 instruments 2018: 9 instruments (9 in force) 2019: 0 instruments 2020: 0 instruments ’20 2021: 0 instruments 2022: 0 instruments 2023: 0 instruments 2024: 0 instruments 2025: 4 instruments (4 in force) 2026: 0 instruments ’26 today

in forcenot yet in forceblocked by a courtproposedno longer in force

  1. AI law 1
  2. Privacy law 7
  3. Scraping law 2
  4. Cybersecurity law 6
  5. Communications law not researched
  6. Content moderation law not researched
  7. Product and AI liability law not researched
  8. Digital accessibility law not researched
  9. Age gating law
  10. Reuse law 1

AI law1 instrument, 1 proposed

Research summary (132 words)

Norway has no AI-specific statute in force.

The proposed Norwegian Artificial Intelligence Act (KI-loven), which would implement Regulation (EU) 2024/1689, remains at the pre-enactment stage: on the Ministry of Digitalisation and Public Governance announced a new consultation on the Act in autumn 2026 and an ambition to put it before the Storting in spring 2027, and on it put the EU's 2026 amendments to the Regulation out for consultation (responses due by ) while still working on the legislative proposition.

Because Norway is an EEA member and not an EU member, Regulation (EU) 2024/1689 does not apply as Norwegian law on the strength of its EU status, and no confirmation that the Regulation has since been incorporated into the EEA Agreement has been located.

AI risk obligations

Norwegian Artificial Intelligence Act (KI-loven)

Proposed Act on Artificial Intelligence (KI-loven) not yet enacted; Stortinget EU/EØS-nytt briefing of ; Ministry of Digitalisation and Public Governance press releases of 4 August and Stortinget (the Storting), EU/EEA news briefing quoting the Ministry of Digitalisation and Public Governance's press release

Proposed. proposed Not law. It binds no one unless it is enacted.

Binds public and private bodies.

What this law does

In its press release the Ministry of Digitalisation and Public Governance said it was preparing a legislative proposition to the Storting for a Norwegian Act implementing Regulation (EU) 2024/1689 (the EU AI Act). As of , the ministry stated that the high-risk rules will apply in Norway only once the Norwegian AI Act is adopted by the Storting.

It also stated that Norwegian rules are intended to take effect as soon as possible after Regulation (EU) 2024/1689, with the amendments agreed under the EU's Digital Omnibus package, is incorporated into the EEA Agreement. On the ministry announced that the Norwegian AI Act would be sent out for a new consultation in autumn 2026. The minister's stated ambition on that date was to put the AI Act before the Storting in spring 2027.

On the ministry put the EU's 2026 amendments to Regulation (EU) 2024/1689 out for consultation as an addition to the 2025 consultation, with responses due by . The ministry stated on that it was working on the legislative proposition implementing the Regulation in Norwegian law.

What it requires

Privacy law7 instruments, 7 in force

Research summary (94 words)

Norway is not an EU member; General Data Protection Regulation (GDPR) reaches Norway through the EEA Agreement, incorporated by Norway's own Personal Data Act (personopplysningsloven, LOV-2018-06-15-38), which is the controlling instrument recorded here rather than the EU Regulation directly.

Under Section 1 of the Act the GDPR applies as Norwegian law, and the Act adds Chapter 3 supplementary provisions (digital consent age of 13, national identity number processing) and Chapter 7 sanctions provisions under which Datatilsynet imposes administrative fines directly, unlike Denmark's criminal-court route. As at ; later amendment to the Act is not independently confirmed.

Breach notification

Personal Data Act, Breach Notification in Norway

Personopplysningsloven (LOV-2018-06-15-38) § 1, incorporating Regulation (EU) 2016/679, Arts. 33-34; § 16Stortinget, Lovvedtak 54 (2017-2018), sanctioned as personopplysningsloven LOV-2018-06-15-38

In force since . Binds public and private bodies.

What this law does

General Data Protection Regulation (GDPR) Articles 33-34, incorporated as Norwegian law through the Personal Data Act: a controller must notify Datatilsynet without undue delay, and within 72 hours where feasible, after becoming aware of a breach unless the breach is unlikely to result in a risk to natural persons, and must notify affected individuals without undue delay for a breach likely to result in a high risk.

Section 16 of the Act lifts the Article 34 notice to individuals to the extent it would reveal information of the kinds in section 16(1), letters a, b and d. Letter a covers information that matters to Norway's foreign-policy, defence or security interests and that the controller may withhold under the Freedom of Information Act. Letter b covers information that must be kept secret to prevent or investigate offences. Letter d covers information a law makes confidential.

What it requires

Comprehensive regime

Personal Data Act (personopplysningsloven)

Lov om behandling av personopplysninger (personopplysningsloven), LOV-2018-06-15-38, in force Stortinget, Lovvedtak 54 (2017-2018), sanctioned as personopplysningsloven LOV-2018-06-15-38

In force since . Binds public and private bodies.

What this law does

Norway is not an EU member; General Data Protection Regulation (GDPR) reaches Norway through the EEA Agreement, incorporated by Norway's own Personal Data Act (personopplysningsloven), not as directly applicable EU law. Section 1 provides that the Regulation, Annex XI item 5e of the EEA Agreement, applies as Norwegian law with the adaptations that follow from Annex XI, Protocol 1 and the Agreement otherwise.

Chapter 3 sets the digital age of consent for information society services at 13 (Section 5) and governs national identity number (fodselsnummer) processing (Section 12). Datatilsynet is the supervisory authority, institutionally distinct from Denmark's identically named authority.

Section 12a, which the Storting added by an amendment passed on , lets public authorities disclose personal data to one another where necessary to prevent, detect, forestall or sanction workplace crime, and does not extend to the special-category data of GDPR Article 9; that amending act takes effect from the time the King decides. The Storting's text of the Act dates from its passage in 2018, so amendments made since, other than Section 12a, are not carried by that source.

What it requires

Cross border transfer

Personal Data Act and GDPR Chapter V, Cross-Border Transfer from Norway

Personopplysningsloven (LOV-2018-06-15-38) § 1, incorporating Regulation (EU) 2016/679, Arts. 44-49Stortinget, Lovvedtak 54 (2017-2018), sanctioned as personopplysningsloven LOV-2018-06-15-38

In force since . Binds public and private bodies.

What this law does

Transfers within the EEA, including to EU member states, are unrestricted; the restriction applies to transfers to third countries outside the EEA. General Data Protection Regulation (GDPR) Chapter V, incorporated as Norwegian law through the Act, permits such a transfer only on an adequacy decision, appropriate safeguards such as Standard Contractual Clauses or Binding Corporate Rules, or a narrow Article 49 derogation, backed by the Article 83(5) top fine tier. Chapter 3 contains no Norway-specific provision narrowing or broadening this beyond the incorporated GDPR text.

What it requires

Data subject rights

Personal Data Act, Automated Decisions in Norway

Personopplysningsloven (LOV-2018-06-15-38) § 1, incorporating Regulation (EU) 2016/679, Arts. 13(2)(f), 14(2)(g), 15(1)(h) and 22Stortinget, Lovvedtak 54 (2017-2018), sanctioned as personopplysningsloven LOV-2018-06-15-38

In force since . Binds public and private bodies.

What this law does

The Personal Data Act (§ 1) makes Regulation (EU) 2016/679, as incorporated into the EEA Agreement, law in Norway, and adds no rule of its own on automated decisions.

General Data Protection Regulation (GDPR) Article 22 gives a person in Norway the right not to be subject to a decision based solely on automated processing, including profiling, that produces legal effects or similarly significantly affects them, unless the decision is necessary for a contract with them, authorised by a law that safeguards their rights, or based on their explicit consent.

Where it rests on a contract or consent, the controller must at least let the person obtain human intervention, express their point of view and contest the decision.

Under the Regulation's Article 22(4), such a decision may not rest on the special categories of personal data in Article 9(1) unless the person gave explicit consent or the processing is necessary for reasons of substantial public interest on the basis of a proportionate law, with suitable safeguards in place.

Its Articles 13(2)(f), 14(2)(g) and 15(1)(h) require the controller to tell the person that such decision-making takes place, with meaningful information about the logic involved and its significance and envisaged consequences for them, at collection, within the Article 14(3) period where the data came from another source, and on an access request.

What it requires

Personal Data Act, Data Subject Rights in Norway

Personopplysningsloven (LOV-2018-06-15-38) § 1, incorporating Regulation (EU) 2016/679, Arts. 12-21; §§ 16 and 17Stortinget, Lovvedtak 54 (2017-2018), sanctioned as personopplysningsloven LOV-2018-06-15-38

In force since . Binds public and private bodies.

What this law does

General Data Protection Regulation (GDPR) Articles 12 to 21, incorporated as Norwegian law through the Personal Data Act: access, rectification, erasure, restriction, portability, and objection, exercisable against the controller.

Section 16(1) of the Act excludes from the Article 13 to 15 rights to information and access the information described in letters a to f. Letter a covers information that matters to Norway's foreign-policy, defence or security interests and that the controller may withhold under sections 20 or 21 of the Freedom of Information Act. Letter b covers information that must be kept secret to prevent, investigate, detect or prosecute offences.

Letter c covers information it would be inadvisable for the person to learn, because of their health or their relationship with people close to them. Letter d covers information subject to a duty of confidentiality set by or under a law. Letter e covers information that exists only in text prepared for internal case preparation and not given to others, so far as refusing access is necessary to ensure sound internal decision processes.

Letter f covers information whose disclosure would conflict with obvious and fundamental private or public interests.

Section 17(1) of the Act disapplies the Article 15 right of access for processing for archiving in the public interest, scientific or historical research or statistical purposes carried out in accordance with Article 89(1) of the Regulation, so far as giving access would take a disproportionate effort or would probably make the aims of the processing impossible or seriously impair them.

Section 17(2) disapplies the Article 16 and 18 rights to rectification and restriction for the same processing, so far as they would probably make the aims impossible or seriously impair them. Section 17(3) provides that neither exclusion applies where the processing has legal effects or direct factual effects for the person.

What it requires

Enforcement supervision

Personal Data Act Chapter 7, Datatilsynet Enforcement in Norway

Personopplysningsloven (LOV-2018-06-15-38) § 1, incorporating Regulation (EU) 2016/679, Arts. 82-83; §§ 26 to 30Stortinget, Lovvedtak 54 (2017-2018), sanctioned as personopplysningsloven LOV-2018-06-15-38, Chapter 7

In force since . Binds public and private bodies.

What this law does

Unlike Denmark, Norway's Datatilsynet imposes administrative fines directly rather than routing them through the criminal courts.

Chapter 7 of the Act: Section 26 lets Datatilsynet impose administrative fines under General Data Protection Regulation (GDPR) Article 83; Section 27 gives a four-week compliance deadline from a final fine decision, with court review available; Section 28 sets a five-year limitation period from when the violation ceased; Section 29 lets Datatilsynet impose a daily coercive fine for continued non-compliance; and Section 30 cross-references GDPR Article 82, letting a liable party also be ordered to pay compensation for non-economic harm.

Section 26's fining power is stated in terms of public authorities; whether the same or a separate mechanism reaches private controllers is not confirmed against Section 26's exact Norwegian text.

What it requires

Sensitive categories

Personal Data Act Chapter 3 and GDPR Article 9, Special Categories in Norway

Personopplysningsloven (LOV-2018-06-15-38) § 1, incorporating Regulation (EU) 2016/679, Art. 9; §§ 6, 7, 9 and 10Stortinget, Lovvedtak 54 (2017-2018), sanctioned as personopplysningsloven LOV-2018-06-15-38, Chapter 3

In force since . Binds public and private bodies.

What this law does

General Data Protection Regulation (GDPR) Article 9(1), incorporated as Norwegian law through the Personal Data Act, classifies biometric data processed for unique identification as a special category. Chapter 3 of the Act contains no biometric-specific provision and no enumeration of biometric examples, so the special category here is the incorporated GDPR one without Norwegian elaboration.

What it requires

Scraping law2 instruments, 2 in force

Research summary (247 words)

Norway has no scraping-specific statute, so general law governs each dimension separately.

The Penal Code (straffeloven, LOV-2005-05-20-28) section 204 criminalises gaining access to a computer system by breaching a protection measure or by another unauthorised method; because the offence's trigger is breaching a protection measure, a scraper reading a public, unauthenticated page without defeating any access control falls outside a plain reading of the provision, and no reported Norwegian case addressing the point has been located.

Section 205 of the same Penal Code chapter is not an aggravated form of the section 204 offence; it addresses violation of the right to private communication (unlawful interception of correspondence), a different offence entirely.

The Copyright Act (åndsverkloven, LOV-2018-06-15-40) section 24 confers a sui generis right on the producer of a database resulting from a substantial investment in collecting, checking or presenting its contents; the Act's own list of the EU/EEA directives it implements does not include a text-and-data-mining exception. No account of the enforceability of a browsewrap or clickwrap terms-of-service against a scraper under the Contracts Act (avtaleloven, 1918) has been located.

Norway's data-protection law (the Personal Data Act, incorporating the General Data Protection Regulation (GDPR) through the EEA Agreement) is documented as this jurisdiction's privacy-topic instrument rather than repeated here, and whether it carries a carve-out for publicly available personal data specific to scraping has not been confirmed. No Norwegian statute or reported case establishing a scraping-specific unfair-competition or misappropriation doctrine, or assigning legal weight to a robots.txt directive, has been located.

Computer misuse

Penal Code, Unauthorised Access to a Computer System

Straffeloven (Penal Code), LOV-2005-05-20-28, kapittel 21 (Vern av informasjon og informasjonsutveksling), § 204Norwegian-language consolidated text of the Penal Code (straffeloven), WIPO Lex

In force since . Binds public and private bodies.

What this law does

Section 204 punishes, with a fine or imprisonment of up to two years, a person who gains access to a computer system or part of it by breaching a protection measure or by another unauthorised method. The provision sits in Chapter 21 (Protection of Information and the Exchange of Information), added to the Penal Code by the Act of No. 74.

Because the offence's trigger is breaching a protection measure, a scraper reading a public, unauthenticated page without defeating any access control falls outside a plain reading of the provision.

What it requires

Database right

Copyright Act, Sui Generis Database Right

Act relating to Copyright in Intellectual Works, etc. (Copyright Act), LOV-2018-06-15-40, as amended to , s. 24Official English translation of the Copyright Act (åndsverkloven), as amended to , WIPO Lex

In force since . Binds public and private bodies.

What this law does

Section 24 gives the producer of a database, such as a form, catalogue, table, program or similar work resulting from a substantial investment in collecting, checking or presenting its contents, an exclusive right to control extraction from or reuse of all or a substantial part of the database's contents, and this right applies correspondingly to repeated or systematic extraction or reuse of immaterial parts of the database that is harmful to its normal use or that unreasonably sets aside the producer's legitimate interests.

The right subsists for 15 years after expiry of the year the database was produced, or, if the database is published within that period, for 15 years after expiry of the year of first publication. The Act's own list of the EU/EEA directives it implements includes Directive 96/9/EC on the legal protection of databases, but does not include a text-and-data-mining exception.

What it requires

Cybersecurity law6 instruments, 6 in force

Research summary (415 words)

Norway's Digital Security Act (digitalsikkerhetsloven) and its regulation entered into force on , transposing the EU's original NIS Directive.

It requires an undertaking that delivers an essential societal service in the energy, transport, health, water-supply, banking, financial-market-infrastructure or digital-infrastructure sector to register itself and its services with the National Security Authority (NSM) and its sector authority, and requires such an undertaking to notify NSM within 24 hours of an incident that significantly affects its service delivery.

NSM is Norway's national contact point, national computer security incident response team (CSIRT), and national supervisory authority for sectors with no dedicated supervisor. The entity classes this Act regulates, operators of essential services in named critical-infrastructure sectors, are reached through the essential-service flag its rows carry.

NIS2, which has replaced the original NIS Directive in the EU, had not been incorporated into the EEA Agreement or transposed into Norwegian law as of the date below; NSM's own account states that NIS2 will in time be introduced into Norwegian law together with the EU's Critical Entities Resilience (CER) Directive, replacing the current Digital Security Act. The Cyber Resilience Act's incorporation into the EEA Agreement and implementation in Norway has not been confirmed.

Norway's Security Act (sikkerhetsloven), which can reach private undertakings designated as carrying out a fundamental national function, is not described here. Norway's breach-notification duty for exposed personal data sits in the Personal Data Act and is documented as this jurisdiction's privacy-topic instrument rather than repeated here.

Section 2 of the Digital Security Act applies the Act to providers of essential societal services in the energy, transport, health, water supply, banking, financial market infrastructure and digital infrastructure sectors, and to providers of digital services.

Section 8 of the Digital Security Act requires a provider of an essential societal service to notify the body designated by the King, without undue delay and regardless of confidentiality duties, of incidents that significantly affect the delivery of the service. Section 1 of the DORA Act gives Regulation (EU) 2022/2554 the force of law in Norway, with the adaptations that follow from the EEA Agreement.

Section 3-1 of the Electronic Communications Act requires a provider to offer electronic communications networks and services with adequate security for users in peace, crisis and war, to maintain adequate preparedness and to secure adequate protection of communication and data.

Section 3-3 of the Electronic Communications Act requires a provider to notify the ministry immediately of security incidents that have caused a significant breach of availability in electronic communications networks or services.

Sector security regimes

Digital Operational Resilience in the Financial Sector: ICT Risk Management and Testing

Lov om digital operasjonell motstandsdyktighet i finanssektoren (DORA-loven) §§ 1, 3 and 4 (Regulation (EU) 2022/2554, Arts. 5 to 16 and 24 to 42)Act adopted by the Storting on (Lovvedtak 54, 2024-2025), as published by the Storting

In force since . Binds private bodies.

What this law does

Section 1 of the DORA Act gives Regulation (EU) 2022/2554 the force of law in Norway, with the adaptations that follow from the EEA Agreement. Section 4 of the DORA Act covers breaches of the Regulation's provisions on governance, ICT risk management framework, identification of ICT functions, security policies, response and recovery, backup, crisis communication and the simplified framework.

Section 4 of the Act also covers breaches of the Regulation's provisions on general testing requirements, vulnerability assessments, ICT third-party risk management and consideration of risks identified at ICT providers. Section 2 of the Act lets the ministry extend the Act by regulation to financing undertakings, loan intermediaries, debt collection undertakings, real estate brokerage undertakings and parent companies of financial groups.

Section 4 of the DORA Act lets the Financial Supervisory Authority impose an administrative fine of up to NOK 50 million on a person or undertaking that breaches the listed provisions of the Regulation. The Act entered into force on .

What it requires

Security Requirements for Providers of Essential Societal Services and Digital Services

Lov om digital sikkerhet (digitalsikkerhetsloven), §§ 7 and 10Act adopted by the Storting on (Lovvedtak 15, 2023-2024)

In force since . Binds private bodies.

What this law does

Section 2 of the Digital Security Act applies the Act to providers of essential societal services in the energy, transport, health, water supply, banking, financial market infrastructure and digital infrastructure sectors, and to providers of digital services. Section 9 of the Act defines a provider of digital services as an undertaking offering online marketplaces, online search engines or cloud services.

Section 7 of the Act requires a provider of an essential societal service to carry out a risk assessment of the network and information systems it uses to deliver the service and to put in place appropriate and proportionate technical and organisational security measures that secure a level of security adapted to the risk.

Section 10 of the Act imposes the same risk assessment and security measures on a provider of a digital service, with regard to security of systems and facilities, incident handling, continuity management, monitoring, auditing and testing, and recognised international standards. Section 2 of the Act excludes undertakings covered by the Act on electronic trust services.

The National Security Authority's guide states that the digital-service security requirement does not apply to providers of digital services with fewer than 50 employees and an annual turnover or balance sheet not above EUR 10 million. Section 17 of the Act lets the supervisory authority impose an administrative fine on a provider that intentionally or negligently breaches sections 7, 8, 10, 11 or 14.

The National Security Authority's guide to the Act states that the administrative fine can reach 25 times the National Insurance basic amount or four percent of the preceding year's turnover for an undertaking, whichever is higher, and cannot in any case exceed NOK 50 million. The Act and its regulation entered into force on .

What it requires

Security and Preparedness Duty of Electronic Communications Providers

Lov om elektronisk kommunikasjon (ekomloven), § 3-1Act adopted by the Storting on (Lovvedtak 1, 2024-2025)

In force. Binds private bodies.

What this law does

Section 3-1 of the Electronic Communications Act requires a provider to offer electronic communications networks and services with adequate security for users in peace, crisis and war, to maintain adequate preparedness and to secure adequate protection of communication and data. Section 3-1 also requires the provider to prevent and minimise the effects of security incidents, to secure rapid recovery and to document an adequate level of security. Section 15-12 of the Act lets the ministry impose an administrative fine for a breach of section 3-1(1), (3) or (4).

What it requires

Vulnerability and incident reporting

Digital Operational Resilience in the Financial Sector: ICT Incident Management and Reporting

Lov om digital operasjonell motstandsdyktighet i finanssektoren (DORA-loven), §§ 1, 3 and 4 (Regulation (EU) 2022/2554, Arts. 17 to 19)Act adopted by the Storting on (Lovvedtak 54, 2024-2025), as published by the Storting

In force since . Binds private bodies.

What this law does

Section 1 of the DORA Act gives Regulation (EU) 2022/2554 the force of law in Norway, with the adaptations that follow from the EEA Agreement. Section 4 of the DORA Act covers breaches of Article 17 of the Regulation on the process for managing ICT-related incidents. Section 4 of the Act also covers breaches of paragraphs 1, 3 and 4 of Article 19 of the Regulation on the reporting of major ICT-related incidents.

Section 4 of the DORA Act lets the Financial Supervisory Authority impose an administrative fine of up to NOK 50 million on a person or undertaking that breaches the listed provisions of the Regulation. The Act entered into force on .

What it requires

Incident Notification by Providers of Essential Societal Services and Digital Services

Lov om digital sikkerhet (digitalsikkerhetsloven), §§ 8 and 11Act adopted by the Storting on (Lovvedtak 15, 2023-2024)

In force since . Binds private bodies.

What this law does

Section 8 of the Digital Security Act requires a provider of an essential societal service to notify the body designated by the King, without undue delay and regardless of confidentiality duties, of incidents that significantly affect the delivery of the service. Section 11 of the Act imposes the same duty to notify without undue delay on a provider of a digital service.

The National Security Authority states that a provider of an essential societal service must notify within 24 hours of becoming aware of the incident. The Authority states that the first notice is due within 24 hours, an update to the authorities within 72 hours and an incident report within one month of the first notice. The National Security Authority's guide states that the 24-hour, 72-hour and one-month deadlines of the regulation do not apply to a provider of a digital service.

The National Security Authority's guide states that the notification duty does not apply to providers of digital services with fewer than 50 employees and an annual turnover or balance sheet not above EUR 10 million. Section 17 of the Act lets the supervisory authority impose an administrative fine on a provider that intentionally or negligently breaches sections 7, 8, 10, 11 or 14.

The National Security Authority's guide to the Act states that the administrative fine can reach 25 times the National Insurance basic amount or four percent of the preceding year's turnover for an undertaking, whichever is higher, and cannot in any case exceed NOK 50 million. The Act and its regulation entered into force on .

What it requires

Notification of Security Incidents by Electronic Communications Providers

Lov om elektronisk kommunikasjon (ekomloven), §§ 3-2 and 3-3Act adopted by the Storting on (Lovvedtak 1, 2024-2025)

In force. Binds private bodies.

What this law does

Section 3-3 of the Electronic Communications Act requires a provider to notify the ministry immediately of security incidents that have caused a significant breach of availability in electronic communications networks or services. Section 3-3 requires the provider to notify without undue delay of security incidents that have caused a significant breach of authenticity, integrity or confidentiality.

The Norwegian Communications Authority states that it must be notified immediately and no later than half an hour after the provider becomes aware of a security incident that has caused a significant breach of availability. The Authority states that all providers of electronic communications networks and services under the Act have a duty to notify it under section 3-3 of the Act and section 2-8 of the regulation.

Section 3-2 of the Act requires a provider to notify a subscriber or user without undue delay where there is a particular risk of a security incident in public networks or services. Section 15-12 of the Act lets the ministry impose an administrative fine for a breach of section 3-3(1).

What it requires

Reuse law1 instrument, 1 in force

Research summary (185 words)

Norway has no press-publisher neighbouring right along the lines of Directive (EU) 2019/790 article 15, no compelled platform-to-publisher bargaining code, and no hot-news or misappropriation doctrine distinct from ordinary copyright law. None of these appear in the current text of the Copyright Act (åndsverkloven, LOV-2018-06-15-40, as amended to ), and that Act's own list of the EU/EEA instruments it implements does not include Directive (EU) 2019/790's press-publisher article.

The Act's general quotation exception and its exception for reproducing a work that forms part of a current event in media coverage of that event are the provisions an aggregator's own reproduction of headlines and snippets would fall under; neither carries a headline-length or short-extract cap distinct from a fair-practice, purpose-justified test, and no reported Norwegian decision applies either provision to a systematic news aggregator rather than an individual reproduction.

Norway has not enacted a text-and-data-mining opt-out mechanism of the kind Directive (EU) 2019/790 article 4 contemplates. No statute or case law addressing whether a hyperlink is itself a communication to the public, or whether framing or inline display changes the answer, has been located.

Snippet reproduction

Copyright Act, Quotation and Current-Event Reproduction Exceptions

Act relating to Copyright in Intellectual Works, etc. (Copyright Act), LOV-2018-06-15-40, as amended to , ss. 29, 36Official English translation of the Copyright Act (åndsverkloven), as amended to , WIPO Lex

In force since . Binds public and private bodies.

What this law does

Section 29 permits quotation from a published work in accordance with proper usage and to the extent required for the purpose, with no headline-length or short-extract cap distinct from that fair-practice test. Section 36 permits a work that forms part of a current event to be reproduced in media coverage of that event on the same fair-practice, purpose-justified terms.

It also permits a published work of art, photograph or film connected to but not part of the event to be reproduced on the same terms against remuneration, except where the work was created in the course of trade for the purpose of reproduction in the media.

What it requires

Where nothing was found1 area of law

These areas of law were researched here and no instrument was recorded. Each finding says what the research checked, as of the date under it. It describes our search, not a guarantee that no such law exists.

Age gating law

Norway has no adult-content age-verification statute, social-media minor-access-restriction statute, app-store age-verification statute, or age-appropriate design code confirmed in force as of the date below.

Bildeprogramloven, Norway's audiovisual-programme classification statute, requires an age rating (allowed for all, or 6, 9, 12, 15 or 18) on every film, game or other audiovisual programme made available to the public, but since a 2023 amendment Medietilsynet no longer sets the rating itself; distributors self-classify, and Medietilsynet reviews and can override a rating rather than approving it in advance.

That is a content-classification scheme rather than a duty to verify a user's age before granting access, so it is described here rather than listed as a separate instrument.

Medietilsynet's own account of the EU Digital Services Act states that the Regulation's minor-protection provisions, including a prohibition on targeted advertising directed at minors, have applied in the EU since February 2024 and were planned to apply as Norwegian law from summer 2026; no confirmation that EEA incorporation and national implementation have actually taken place has been located, so nothing from the Digital Services Act is recorded here as Norwegian law.

As of .

Case law

  • No current case law for Norway AI law
  • No current case law for Norway privacy law
  • No current case law for Norway scraping law
  • No current case law for Norway cybersecurity law
  • No current case law for Norway communications law
  • No current case law for Norway content moderation law
  • No current case law for Norway product and AI liability law
  • No current case law for Norway digital accessibility law
  • No current case law for Norway age gating law
  • No current case law for Norway reuse law

Reporting clocks that run here8 instruments

The instruments whose obligation lines set a deadline for reporting an incident, a vulnerability or a personal-data breach, each deadline read from the sentence that carries it and listed shortest first. The law of Norway comes first, then the law of the bodies above it that applies here.

Each flag is one law, and a link to it. Read down the scale: the clocks document's time axis, with the empty stretches shortened so the deadlines sit close. Flags on one line set the same duty at the same deadline, and the laws behind them are named to the right, with what each clock counts from.

1 hour
Incident notificationsecurity law
4 hours
Incident notificationsecurity law
1 month
Incident notificationsecurity law
The deadlines above on one time axis, shortest at the top. The axis keeps its order and, between neighbors, its proportion, but a stretch with no deadline on it is shortened, so the hour marks on the left are what say how far apart two stations really are. Beside each action, the laws that set it, what each counts from, and a status where the law is not yet in force. The List tab has the same data in full, with the sentences.

The law of Norway

1 hour

Notification of Security Incidents by Electronic Communications Providers

Lov om elektronisk kommunikasjon (ekomloven), §§ 3-2 and 3-3security law, in force

The sentences the clocks are read from

Notify the authority immediately of security incidents that have caused a significant breach of availability, and, as the Norwegian Communications Authority states it, no later than half an hour after you become aware of the incident (section 3-3(1)).

Notify the authority without undue delay of security incidents that have caused a significant breach of authenticity, integrity or confidentiality (section 3-3(1)).

Notify subscribers and users without undue delay where there is a particular risk of a security incident in public networks or services, and tell them of protective or remedial measures they can take (section 3-2).

24 hours72 hours1 month

Incident Notification by Providers of Essential Societal Services and Digital Services

Lov om digital sikkerhet (digitalsikkerhetsloven), §§ 8 and 11security law, in force since

The sentences the clocks are read from

Notify the body the King designates, without undue delay and regardless of confidentiality duties, of incidents that significantly affect the delivery of an essential societal service (section 8) or a digital service (section 11).

As an essential-service provider, send the first notice within 24 hours of becoming aware of the incident, an update within 72 hours, and an incident report within one month of the first notice (digitalsikkerhetsforskriften section 17, as the National Security Authority states it).

As a digital-service provider, the 24-hour, 72-hour and one-month deadlines do not apply; notify without undue delay (section 11). A provider with fewer than 50 employees and an annual turnover or balance sheet not above EUR 10 million is outside the notification duty, as the National Security Authority's guide states it.

72 hours

Personal Data Act, Breach Notification in Norway

Personopplysningsloven (LOV-2018-06-15-38) § 1, incorporating Regulation (EU) 2016/679, Arts. 33-34; § 16privacy law, in force since

The sentences the clocks are read from

Notify Datatilsynet without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting a person in Norway, unless the breach is unlikely to risk their rights and freedoms.

If you process personal data on behalf of a controller, notify the controller without undue delay after becoming aware of a personal data breach (Article 33(2)).

Notify affected individuals without undue delay where a breach is likely to result in a high risk to their rights and freedoms.

The law of the European Union incorporated into the EEA Agreement, which applies in Norway

4 hours24 hours72 hours1 month

DORA, Article 19 (reporting of major ICT-related incidents), with the time limits of Delegated Regulation (EU) 2025/301

Regulation (EU) 2022/2554, Article 19security law, in force since

The sentences the clocks are read from

Report a major ICT-related incident to the competent authority your sector's Union law designates under Article 46, the European Central Bank through your national supervisor if you are a credit institution classified as significant, using the templates referred to in Article 20, and submit an initial notification as early as possible and in any case within four hours of classifying the incident as major, and no later than 24 hours from becoming aware of it.

Where classification as major comes later than that, submit the initial notification within four hours of the classification instead.

Submit an intermediate report within 72 hours of the initial notification, and submit an updated intermediate report without undue delay and in any case when you have recovered regular activities.

Submit a final report no later than one month after the intermediate report, or your latest updated one, once you know the root cause and the actual impact figures.

If you cannot meet one of those deadlines, tell the competent authority without undue delay and before the deadline lapses, explaining why. A deadline falling on a weekend or bank holiday moves to noon of the next working day, unless you are a credit institution, a central counterparty, a trading venue operator, or an entity your Member State has designated essential or important under the NIS2 Directive, none of which get that extension for an initial notification or intermediate report.

Your competent authority may also decide, and notify you, that the extension does not apply to you if you are a financial entity that is significant or has a systemic character for the financial sector at national or Union level.

Notifying a significant cyber threat under Article 19(2) is voluntary, only where you judge it relevant to the financial system, service users, or your clients. Where a major ICT-related incident affects your clients' financial interests, tell them without undue delay as soon as you become aware of it, describing the incident and the mitigation measures you took, and, for a significant cyber threat, tell a potentially affected client of protection measures it could take, where applicable.

24 hours3 days

Commission Regulation on Personal Data Breach Notification by Electronic Communications Providers (Regulation (EU) No 611/2013)

Regulation (EU) No 611/2013privacy law, in force since

The sentences the clocks are read from

If you provide a publicly available electronic communications service, notify every personal data breach to the competent national authority (Article 2(1)), no later than 24 hours after its detection, where feasible, with the information set out in Annex I; detection is deemed to have taken place when you have acquired sufficient awareness that a security incident has occurred that led to personal data being compromised (Article 2(2)).

Where all the information in Annex I is not available and further investigation is required, you may make an initial notification no later than 24 hours after detection containing the information in Section 1 of Annex I, and you must then make a second notification as soon as possible and at the latest within three days following the initial notification, containing the information in Section 2 of Annex I (Article 2(3)).

If you cannot provide all the information within the three-day period, notify as much as you have within it, submit to the competent national authority a reasoned justification for the late notification of the remaining information, and notify the remaining information as soon as possible (Article 2(3)).

Notify the subscriber or individual without undue delay after detection of the breach, whether or not you have yet notified the competent national authority (Article 3(3)).

If you have a direct contractual relationship with the end user and, despite reasonable efforts, cannot identify within the timeframe all the individuals likely to be adversely affected, you may notify them through advertisements in major national or regional media in the relevant Member States within that timeframe, containing the Annex II information where necessary in a condensed form, and you must continue all reasonable efforts to identify and notify them as soon as possible (Article 3(7)).

If you are contracted to deliver part of the electronic communications service without a direct contractual relationship with subscribers, immediately inform the contracting provider in the case of a personal data breach (Article 5).

72 hours

Commission Delegated Regulation (EU) 2022/1645, External Reporting of Information Security Incidents and Vulnerabilities (IS.D.OR.230)

Commission Delegated Regulation (EU) 2022/1645, IS.D.OR.230security law, in force since

The sentence the clocks are read from

Submit a notification as soon as you know of the condition, and a report as soon as possible and not exceeding 72 hours from the time you know of it unless exceptional circumstances prevent this, in the form your competent authority defines (point IS.D.OR.230(c), points (1) and (2)).

72 hours

Commission Implementing Regulation (EU) 2023/203, External Reporting of Information Security Incidents and Vulnerabilities in Aviation (IS.I.OR.230)

Commission Implementing Regulation (EU) 2023/203, IS.I.OR.230security law, in force since

The sentence the clocks are read from

Submit a notification as soon as you know of the condition, and a report as soon as possible and not exceeding 72 hours from the time you know of it unless exceptional circumstances prevent this, in the form your competent authority defines (point IS.I.OR.230(c), points (1) and (2)).

72 hours

GDPR Articles 33-34, Breach Notification

Regulation (EU) 2016/679, Arts. 33-34privacy law, in force since

The sentences the clocks are read from

Notify the competent supervisory authority without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting EU personal data, unless the breach is unlikely to risk individuals' rights and freedoms.

If you process personal data on behalf of a controller, notify the controller without undue delay after becoming aware of a personal data breach (Article 33(2)).

Notify affected individuals without undue delay where a breach is likely to result in a high risk to their rights and freedoms.

Which of these one incident starts turns on the facts: the incident method works that through. The clocks document draws every clock in the LexLint law library on one axis, with the sentence beside every rung.

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

This page covers the instruments LexLint has researched to a stage. Instruments named in the law library but not yet researched are counted in the head and are not listed here. Every entry carries its own primary source on its note page. This is a research index, not legal advice.