NIS2 and the Cybersecurity Act – which systems do you need?

The Cybersecurity Act requires that you manage risks, report incidents in a timely manner and have control over your systems and suppliers. No single system can do all of that. Here we go through what types of systems are needed, what the law specifically requires and where a Swedish ITSM system like Easit GO fits in.

What systems help meet the requirements of NIS2?

No system alone is sufficient to meet NIS2. The requirements of the Cybersecurity Act span governance, technology and day-to-day operations, and in practice four types of support are needed: an information security management system, technical protection, monitoring and detection, and process and operational support where the measures are actually implemented and documented.

A GRC tool describes what you should do. An ITSM system like Easit GO is where it is done, tracked and can be shown to the regulator. The two complement each other.

System type

What it covers in the law

Category example

Where Easit GO fits in

Management systems and GRC

Risk analysis, security policies, management responsibilities, training and monitoring of the effectiveness of measures

ISMS and GRC tools, often according to ISO 27001

Complement. Actions from the risk analysis become cases in Easit GO that are followed to the end. Anyone without GRC tools can manage risks directly in GO

Technical protection

Access control, multi-factor authentication, encryption, backup and continuity

MFA, backup, encryption, endpoint protection

Vulnerabilities and actions that require changes are handled in the change process

Monitoring and detection

Detecting incidents in a timely manner so that reporting deadlines can be met

SIEM, log monitoring, SOC service

Alarms become incident cases via integration, with timestamp from the first moment

Process and operational support

Incident management and reporting, change management, asset management and supply chain security

ITSM and ESM platform

The core. This is where the incident, change, access and supplier processes and the traceability that supervision demands live

How does an ITSM system support NIS2?

An ITSM system carries the parts of NIS2 that happen every day: incidents to be handled and reported, changes to be approved, systems to be tracked, and suppliers to be followed up. It is also where the traces are when the regulatory authority asks how you have acted.

Incident reporting within legal deadlines

The law requires an early warning within 24 hours, an incident report within 72 hours and a final report within one month. In Easit GO, the incident is registered with a time stamp immediately, classified and escalated according to fixed rules, and monitoring of deadlines ensures that the right person is reminded before the clock runs out. All the information that the report needs is collected in the case. Read more about how you go from incident to report in Easit GO.

Change management with traceability

Many incidents start with a change that didn't go as planned. A structured change process with risk assessment, approval and documented outcome reduces risk and demonstrates that changes to critical systems are happening under control. Read more about the change process and NIS2.

CMDB and asset registry

You can't protect what you don't know you have. The law requires asset management, and a CMDB shows what systems exist, who owns them, and how they are connected. When an incident occurs, you immediately see which services are affected. Read more about why CMDB is a cornerstone of the work with NIS2 and about system and object management.

Supplier follow-up

NIS2 requires you to manage security throughout your supply chain. In Easit GO, suppliers are linked to the systems and services they deliver, and regular risk assessments and follow-ups are planned and documented as cases. Read more in the guide on implementing supplier management.

Risk management in Easit GO

NIS2 requires systematic identification and prioritization of risks. Risk management in Easit GO provides an overall picture of threats, vulnerabilities and actions, and each action can be followed as a case until it is implemented. If you already have a GRC tool, Easit GO receives the actions from there. Read more about the support for risk management in GO.

What does the Cybersecurity Act specifically require?

The Cybersecurity Act is Sweden's implementation of the EU's NIS2 Directive. It entered into force on 15 January 2026 and replaces the previous NIS Act. The Act covers significantly more activities than before, within 18 sectors, and also applies to the public sector such as municipalities, regions and state authorities.

The requirements can be summarized in four parts:

  • Notification. Activities that are covered must notify the supervisory authority.
  • Security measures. You will work systematically and risk-based on, among other things, risk analysis, incident management, continuity and backup, supply chain security, vulnerability management, training and cyber hygiene, encryption, access control and asset management, and multi-factor authentication.
  • Significant incidents are reported in three stages: early warning within 24 hours, incident notification within 72 hours, and final report within one month. The reports go to the National Cyber ​​Security Center (NCSC) via CERT-SE.
  • Management's responsibility. Management is responsible for implementing the measures and must have training in cybersecurity themselves.

Supervision is handled by sectoral supervisory authorities, and deficiencies can lead to sanctions. Current regulations, guidance and reporting channels can be found at the National Cybersecurity Center. Also read how the new Cybersecurity Act affects your organization.

Why a Swedish supplier simplifies supplier security.

NIS2 makes your suppliers part of your own security. Every system you buy becomes something you need to risk assess: where the data is stored, who can access it and what legislation the supplier is subject to. The fewer question marks, the easier that assessment becomes.

Easit is a Swedish company based in Sundsvall, and Easit GO is delivered as SaaS from Swedish data centers with Swedish staff. No data leaves Sweden. For those who want full control in their own environment, Easit GO is also available on-premises.

The same principle applies to AI. Easit GO can be connected to any AI service, and together with Atea we offer AI via Atea's Model as a Service where data stays in Sweden. This means you can use AI for triage, classification and knowledge articles without case data being sent outside the country.

For your risk assessment, this means a shorter supply chain, clearer responsibilities and fewer questions about third-country transfers.

Checklist: how to get started in five steps

  1. Find out if you are covered. Review the guidance from the NCSC or your regulatory authority and report the business if it is covered.
  2. Conduct a current situation analysis. Compare how you work today with the legal security measures and prioritize the biggest gaps based on risk.
  3. Map your systems and services. Build an asset register or CMDB with owners, dependencies and critical suppliers. It is the foundation for both risk analysis and incident management.
  4. Secure the incident flow. Decide who decides if an incident is significant, who reports and how you will maintain 24 and 72 hours even on a Friday night. Practice the flow.
  5. Get your changes and suppliers in order. Implement traceable change flows for critical systems and follow up with suppliers regularly. Report status to management so that responsibility becomes visible.

Would you like to see what the steps might look like in Easit GO? Book a walkthrough

Frequently asked questions about NIS2 and IT support.

Is there a system that makes us NIS2-compliant? No. NIS2 requires a systematic approach, not a specific system. In practice, a management system for information security, technical protection, monitoring, and process and operational support is needed that demonstrates that the measures are actually being implemented.

Do we need both a GRC tool and an ITSM system? Most people need both. The GRC tool manages risks, policies, and compliance, while the ITSM system is where incidents, changes, and assets are managed on a day-to-day basis. Smaller organizations can sometimes manage risk work directly in the ITSM system.

Where to report a significant incident? To the National Cyber ​​Security Center (NCSC) via CERT-SE. The early warning should be submitted within 24 hours of becoming aware of the incident.

Are municipalities and regions covered by the Cybersecurity Act? Yes. Public administration is covered, which includes state agencies, regions and municipalities.

Does our ITSM system have to be located in Sweden to comply with NIS2? The law does not require it, but you should assess the risk with each supplier. With Swedish operations and data staying in Sweden, that assessment becomes easier.

Can Easit help us with NIS2? Yes. We help you with Easit GO to support incident reporting, change management, CMDB, supplier follow-up and risk management, and our consultants help you set up the processes according to your requirements. Easit GO works well together with the GRC tool you already have.

Do you want to ensure your compliance with NIS2 regulations?

Subscribe to our newsletter.

News, customer cases and invitations from Easit directly in your inbox.

Privacy policy (opens in new window)
Scroll to the top