Norway's Digital Security Act: 7 requirements to meet

Back to Blog

Norway's Digital Security Act in practice: 7 areas to get in place

Norway's Digital Security Act (digitalsikkerhetsloven) and the accompanying Digital Security Regulation (digitalsikkerhetsforskriften) set specific requirements for organisations that provide essential and digital services. The rules took effect on 1 October 2025 and cover, among other things, a management system, risk assessment, security measures, preparedness and the reporting of security incidents. The Act implements the EU's first NIS Directive in Norwegian law, and NIS2 is expected to follow.

But where do you start?

We have gone through the Act and the Regulation and broken the requirements down into 30 controls that can be followed up in practice. Although the rules are extensive, much of the security work will be familiar.

Here are the seven areas we think it makes sense to start with.

1. Clarify whether you are covered, and what is in scope

The first step is to clarify whether the Digital Security Act applies to your organisation, and which services, systems and parts of the organisation are covered.

The Act applies to providers of essential services in sectors such as energy, transport, health, water supply, banking, financial market infrastructure and digital infrastructure. It also covers certain providers of digital services. The Digital Security Regulation defines the scope in more detail.

If you are covered, document the scope. Which services do you provide? Which IT systems and suppliers do those services depend on? Which parts of the infrastructure are critical for delivery?

This becomes the foundation for the rest of your security work.

2. Establish a management system for digital security

The Digital Security Regulation requires providers of essential services to establish and maintain a security management system that covers digital security.

This should not be a security project running alongside the business. The management system must be part of how the organisation is governed overall.

Roles and responsibilities must be defined and documented. Management must approve the management system and review it at least once a year.

In practice, this means putting in place:

  • clear roles and responsibilities

  • a policy and governing documents

  • routines for following up the security work

  • management commitment

  • periodic review and improvement

In other words, security work must be possible to manage, document and follow up over time.

3. Carry out risk assessments, and use them to prioritise

Risk assessment is a central part of the Digital Security Regulation.

A risk assessment should not just be a list of generic cyber threats. You need to understand which unwanted events could affect your services, which vulnerabilities exist, what the consequences could be, and which dependencies you have.

That means having an overview of:

  • networks and information systems

  • relevant events and threats

  • vulnerabilities

  • possible consequences

  • dependencies on systems, people and suppliers

The risk assessment should then be used to prioritise security measures.

This is an important point. The goal is not just to have a risk assessment to show during an inspection. It should be used to decide what you actually do about the risk.

See also: Risk and vulnerability analysis in 7 steps, with template.

4. Get the basic security measures in place

The Digital Security Regulation sets requirements for organisational, technological, physical and personnel security measures.

On the technology side, this covers a number of areas that most people working with information security will recognise.

Examples include:

  • access control

  • strong authentication

  • network segmentation

  • patch and vulnerability management

  • backup and recovery

  • logging

  • security monitoring

  • capacity and resilience

Which measures you need depends on your risk. That is why the risk assessment and the security measures must be seen together.

The basic measures also cover people and organisation. Training, awareness, responsibilities, confidentiality and relevant personnel processes are all part of the whole.

5. Keep control of suppliers and dependencies

Few organisations deliver their services alone.

Cloud services, data centres, software suppliers, consultants and other third parties can be essential for your services to work. A failure at a supplier can quickly become your own security incident.

You should therefore map important supplier dependencies and assess the risks they bring.

This includes:

  • identifying critical suppliers

  • assessing supplier risk

  • setting relevant security requirements

  • following up security requirements and measures

  • understanding dependencies and concentration risk

  • planning for the loss of critical deliveries

Supplier management should be an integrated part of risk management, not a separate exercise done only at procurement.

6. Prepare for something going wrong

Good digital security is not only about preventing incidents.

You must also be able to detect, handle and recover from them.

The Digital Security Regulation sets requirements for incident handling and preparedness. In practice, this means having a contingency plan, defined roles and responsibilities, channels for security communication and plans for recovery.

And the plans should be exercised.

It is much easier to agree who does what before the production systems are down than while the incident is ongoing.

7. Know your reporting and information duties

The Digital Security Act and Regulation also require security incidents to be reported.

Decide in advance which incidents could trigger a duty to report, who is responsible for assessing this, who must be notified, and how the necessary information will be collected.

The same applies to the duty to provide information to the authorities.

This should be part of your incident handling and preparedness, not something you start looking into after a serious incident has happened.

The Digital Security Act is about more than compliance

The good news about the requirements in the Digital Security Act and Regulation is that much of the work has value beyond compliance itself.

An organisation that puts in place a management system, risk assessments, basic security measures, supplier follow-up, incident handling and preparedness has also built much of the foundation for systematic information security work.

That also makes it easier to work with other security standards and frameworks.

There is considerable overlap between the work done for the Digital Security Act and, for example, ISO/IEC 27001. Meeting the Digital Security Act does not automatically mean you meet ISO/IEC 27001, but documentation, risk assessments, governance processes and security measures can often be reused.

The work can therefore pay off in several ways at once: a better overview of your risks and dependencies, more structured security work, better preparedness, and a better starting point if you later want to work towards other requirements or certifications.

The Digital Security Act as a framework in Cyrigo

We have turned the Digital Security Act and Regulation into an operational framework in Cyrigo.

The framework consists of 30 controls that let you follow the requirements and link them to governing documents, risk assessments, security measures and other evidence of how each requirement is met.

The point is not to produce as much compliance documentation as possible. It is to make it easier to see which requirements apply, what is already in place, and where you still have work to do.

If your organisation is working on the Digital Security Act, see how Cyrigo supports security management, risk assessment and compliance on our product page, or book a demo to see the framework in practice.

Want to build the competence in-house? In our course Digital Security in Practice (DSiP), taught in Norwegian, you work with the requirements of the Digital Security Act, NIS2 and DORA over four sessions, and develop documentation and measures for your own organisation along the way.

Back to Blog