NIS2 guide
NIS2 compliance checklist
NIS2 names ten areas that every covered organisation's security measures must cover as a minimum. It also sets duties for management and deadlines for incident reports. This checklist goes through them one by one, with the article each one comes from. In Sweden the authority has also issued binding detail rules, listed in section 4 and marked as binding or advice.
On this page
This is a plain-language summary, not legal advice. Where this page and the law differ, the law decides.
1. In short
- NIS2 is Directive (EU) 2022/2555. EU countries had to apply it from 18 October 2024 (Article 41). Sweden's law took effect on 15 January 2026.
- Article 21 lists ten areas that your security measures must cover "at least".
- The measures must be appropriate and proportionate. That depends on your exposure to risks, your size, and how likely and how severe incidents are (Article 21(1)). The directive does not tell you which product or brand to use.
- Management must approve the measures, oversee them and be trained (Article 20).
- In Sweden the authority's regulation MCFFS 2026:11 turns the measures into binding detail rules. It has been in force since 1 October 2026 (section 4).
- Significant incidents must be reported without undue delay: an early warning within 24 hours of becoming aware, an incident notification within 72 hours of becoming aware, and a final report within one month of the notification (Article 23(4)).
2. Are you covered
NIS2 applies to organisations in the sectors listed in its Annex I and II that are at least medium-sized, and to some organisations regardless of size (Article 2). Each EU country writes this into its own law. For Sweden, see Does NIS2 apply to my company?, Cybersäkerhetslagen: what Sweden's NIS2 law requires and NIS2 registration in Sweden.
Not covered yourself? Your customers may be, and they have to take their suppliers' security into account (Article 21(3)). See NIS2 requirements for suppliers.
3. The ten measures
Article 21(2) lists the areas as points (a) to (j). The middle column quotes the directive. The last column gives practical examples of what to check. Those examples are not legal text. For Sweden, the binding detail behind each point is in section 4.
| Point | What the directive says | Practical examples |
|---|---|---|
| (a) | "policies on risk analysis and information system security" |
|
| (b) | "incident handling" |
|
| (c) | "business continuity, such as backup management and disaster recovery, and crisis management" |
|
| (d) | "supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers" |
|
| (e) | "security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure" |
|
| (f) | "policies and procedures to assess the effectiveness of cybersecurity risk-management measures" |
|
| (g) | "basic cyber hygiene practices and cybersecurity training" |
|
| (h) | "policies and procedures regarding the use of cryptography and, where appropriate, encryption" |
|
| (i) | "human resources security, access control policies and asset management" |
|
| (j) | "the use of multi-factor authentication or continuous authentication solutions, secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate" |
|
How much is enough depends on you. Under Article 21(1) the level of security must fit the risk, taking into account the state of the art, relevant European and international standards where applicable, and the cost. Whether a measure is proportionate depends on the entity's exposure to risks, its size, and how likely and how severe incidents are, including their impact on society and the economy.
4. In Sweden: the binding detail rules
The law (2 kap. 3 and 4 §§) is made concrete by the authority's regulation MCFFS 2026:11, "föreskrifter och allmänna råd om säkerhetsåtgärder och ledningens utbildning". It has been in force since 1 October 2026. It was issued by MCF. Since 1 July 2026 FRA holds the rule-making role (ordinance 2025:1507, 38–39 §§, as changed by SFS 2026:623), and the regulation applies unchanged.
Start here. If you read only five lines below, read these: management goals and the yearly report to management (3 kap. 4 §), the three named roles (5 §), the action plan (13 §), backups (4 kap. 28 §) and multi-factor sign-in (17 §).
- Binding = föreskrifter. You must follow them.
- Advice, not binding = allmänna råd. The regulation itself says advice is not binding: it explains the rules and gives general recommendations.
- "Identify and handle the need" (identifiera och hantera behovet) means you must assess the need and deal with it. The rule does not fix the answer.
- If another regulation sets a higher requirement, that one applies (1 kap. 2 §). FRA may grant an exemption in an individual case when there are special reasons (7 kap. 1 §).
Who it covers. If your sector activity is only in digital infrastructure, digital providers, ICT service management (business to business), postal and courier services or space, only the management training in 2 kap. 1 § applies to you (MCFFS 2026:11, 1 kap. 1 §, second paragraph). The carve-out is worded "uteslutande" (only). If you also work in another sector, the carve-out does not apply to you and the full rules do. See section 7.
Management and organisation
- Binding. Management sets goals and direction, makes its tasks clear, makes sure resources and authority exist, and is told about the measures and the security level when needed and at least once a year (3 kap. 4 §).
- Binding. Appoint a coordinator (samordnare), an information owner (informationsägare) for all information processing and a system owner (systemägare) for every system (3 kap. 5 §).
- Binding. Management training must let management set goals, assess which measures the risks call for and monitor delivery (2 kap. 1 §). No minimum frequency is set. Advice. Cover management's role and the rules, why cybersecurity matters for sector activity, risk handling and monitoring, and your own rules.
- Binding. Set checks at recruitment and when access changes, and the training and exercises staff must do before and during employment (3 kap. 9 §). Advice. Keep a training plan.
- Binding. Collect information from your hardware and software suppliers and from the national cybersecurity centre at FRA, in particular its national CSIRT unit (the national incident response team) and its crisis-management function (3 kap. 10 §).
Risk, documentation and follow-up
- Binding. Systematic, risk-based work that covers every kind of hazard (3 kap. 1 §). Identify and handle the need to use relevant standards (2 §). Advice. Use ISO/IEC 27001:2022 and 27002:2022 or equivalents.
- Binding. Set internal rules and ways of working. Identify and handle the need to document and keep what you need for follow-up and supervision (3 §). Advice. Decide retention from your own needs. No fixed retention period is set.
- Binding. Classify information for confidentiality, integrity (including authenticity) and availability, with your own number of levels and criteria (11 §).
- Binding. Set consequence and likelihood levels and risk acceptance criteria, and identify and handle the need to update risk analyses when threats or vulnerabilities change (12 §).
- Binding. Write an action plan (åtgärdsplan): each chosen measure, the risks it handles, the responsible role and the date (13 §).
- Binding. Follow up and evaluate the measures. For sector-critical systems at least once a year (19 §). A sector-critical system is one you need to run your sector activity or to provide your outside services (1 kap. 4 §). You must decide which of your systems these are (4 kap. 10 §).
- Binding. Keep architecture documentation, an inventory of the digital environment and operating documentation per system current (4 kap. 8–10 §§).
Continuity, incidents and backups
- Binding. Set a restoration priority order. Set and practise alternative working methods where needed (3 kap. 14 §). Advice. Practise them, and restoring sector-critical systems, when needed and at least yearly.
- Binding. For production: set acceptable downtime, handle the need for redundancy, and plan and practise outages in sector-critical systems (15 §).
- Binding. Identify and handle the need for a crisis organisation, supplier support in advance (16 §) and crisis handling and communication (18 §). Advice. Practise crisis handling when needed and at least yearly.
- Binding. Identify, report, analyse and limit incidents and near misses, restore in priority order, and handle the need to find the root cause (17 §). Reports: NIS2 incident reporting.
- Binding. Make sure information can be restored within the acceptable downtime, and handle the need for backups (4 kap. 28 §). Advice. Keep one backup on separate hardware.
- Binding. Suppliers: assess risks before buying or outsourcing, and make the contract allow security measures over time (4 kap. 1–4 §§). See NIS2 requirements for suppliers.
Network and access
- Binding. Segment the digital environment and allow only approved flows (4 kap. 11 §). Keep development, test and training that could affect production IT apart from it (12 §).
- Binding. Replace default credentials, remove unneeded functions, allow only approved flows (13 §). Credentials long and complex enough (14 §). Lock identities after failed logins and remove access that is no longer due (15 §). Least privilege, restrictive admin rights, no production credentials in development or test (16 §). No review interval for access is set.
- Binding. Multi-factor sign-in for IT-segment systems with information needing extended protection, for administrative access to IT and OT segments (OT means machine and plant control systems) in production, and for staff and supplier access from outside (17 §).
Secure systems and encryption
- Binding. Secure development, pre-launch tests and reviews, and a plan for decommissioning (5–7 §§).
- Binding. DNSSEC on your registered domain names, unless obviously unnecessary (26 §).
- Binding. Encrypt security logs and credentials when they move inside the digital environment. Encrypt security logs, credentials and other information that needs extended protection when they are sent to systems outside it (25 §). Extended protection means information that outside rules require to be protected at a set level, or that you judge needs the same protection. Advice. Encrypt them at rest too.
Time, malware and change control
- Binding. Accurate time that can be translated to UTC(SP), Sweden's official time, in production (23 §). Malware protection on IT segments (24 §). Intrusion detection and prevention on production IT segments (29 §). Structured, traceable change management (30 §).
Monitoring, testing and patching
- Binding. Handle the need for monitoring and alarms. Subscribe to the national CSIRT unit's automatic vulnerability notifications (ANTS), unless obviously unnecessary (20 §).
- Binding. Log security events and unauthorised access attempts, protect the logs, keep them as long as needed, and analyse them at a suitable interval (21–22 §§).
- Binding. Security tests on IT systems: latest approved version, published vulnerabilities handled, chosen configuration in place (27 §). Advice. Report unpublished vulnerabilities to the national CSIRT unit.
- Binding. Install security updates promptly. Replace or upgrade software whose vendor has stopped security updates, without undue delay (31 §). Advice. Start within 72 hours of a fix being available.
Physical protection and public administration
- Binding. Restrict access to premises and, unless obviously unnecessary, guard them (5 kap. 1 §). Check the identity of staff and visitors, except in designated visitor areas (1 §).
- Binding. Guard and alarm special IT and OT rooms, unless obviously unnecessary (2 §).
- Binding. Identify and handle the need to protect premises against fire, water damage, harmful humidity and harmful temperature (3 §). Make sure power, cooling, heat, ventilation and external communications work well enough (4 §).
- Binding. Public administration only: check systems used for crisis communication (6 kap. 1 §; Advice. every three months) and handle the need, where possible, for Rakel or SWEN terminals (the state emergency radio and data networks) and SGSI (the secure government intranet) for crisis communication (2 §).
5. Management duties
Article 20 puts the responsibility on the management body:
- It approves the security measures.
- It oversees that they are carried out.
- It can be held liable when the organisation breaks Article 21. This does not change national rules on the liability of public institutions, public servants and elected or appointed officials.
- Its members must follow training. Offering similar training to employees on a regular basis is encouraged.
In Sweden these duties are made concrete, with a yearly report to management, three required roles and the content of the training. See section 4.
6. Incident reporting
| Deadline | Report |
|---|---|
| Within 24 hours | Early warning (a) |
| Within 72 hours | Incident notification (b) |
| Within one month | Final report (d) |
The directive counts the 24 and 72 hours from becoming aware of the significant incident (Article 23(4)). The Swedish law says the same ("fått kännedom om", 2 kap. 5 & 6 §§). The authority's regulation MCFFS 2026:8 counts from when the incident has been identified as significant (2 kap. 3 & 4 §§). The month counts from the incident notification. The letters are the points of Article 23(4).
Our advice: to be safe, start counting from the first of the two moments.
The regulation's definition of a significant incident does not cover operators whose sector activity is in digital infrastructure, digital providers, ICT service management (business to business), postal and courier services or space (MCFFS 2026:8, 1 kap. 1 §). If that is you, ask FRA how these deadlines apply to you.
Providers of trust services have 24 hours, not 72, for the notification (in Sweden, 2 kap. 6 § of the law). What each report must contain, and the reports for ongoing incidents and on request, are in NIS2 incident reporting: 24 hours, 72 hours, one month.
7. EU rules for some digital and ICT providers
For some kinds of provider the EU has set detailed technical requirements in Implementing Regulation (EU) 2024/2690. It applies to DNS service providers, top-level domain name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online marketplaces, online search engines and social networking services platforms, and trust service providers. The same regulation specifies when an incident counts as significant for them.
In Sweden the detail rules in MCFFS 2026:11 do not apply to an operator whose sector activity is only in digital infrastructure, digital providers, ICT service management (business to business), postal and courier services or space, apart from the management training (1 kap. 1 §, second paragraph). The law's duty to take appropriate measures (2 kap. 3 §) and, for the providers it names, Implementing Regulation (EU) 2024/2690 are not changed by that sentence. If you also work in another sector, the carve-out does not cover you.
8. If you find a gap
An organisation that finds it does not meet the measures in Article 21(2) must take all necessary, appropriate and proportionate corrective measures without undue delay (Article 21(4)).
9. Fines
Article 34 sets the level each country must at least allow when an essential or important entity breaks Article 21 or 23:
| Entity | Maximum fine must be at least |
|---|---|
| Essential | EUR 10 million or 2 percent of the total worldwide annual turnover, in the previous financial year, of the undertaking the entity belongs to, whichever is higher |
| Important | EUR 7 million or 1.4 percent of the total worldwide annual turnover, in the previous financial year, of the undertaking the entity belongs to, whichever is higher |
The exact amounts are set in each country's law, and each country decides whether and how far fines apply to public administration (Article 34(7)). For Sweden, see Cybersäkerhetslagen.
10. How SimpleSecurity helps
SimpleSecurity keeps the records behind the checklist. It does not make an organisation compliant by itself, and SimpleSecurity holds no certification.
| Point | Service you can use |
|---|---|
| (a) Risk and policies | Risk Register and Policy Register |
| (b) Incidents | Incident Register, with the NIS2 24-hour and 72-hour clocks |
| (c) Continuity | Backups (check-ins from your backup jobs and logged restore tests) and Uptime Monitor |
| (d) Supply chain | Vendor Risk, with tiered questionnaires and a vendor portal |
| (e) Vulnerabilities | Vulnerability Scanner and Attack-Surface Discovery |
| (f) Effectiveness | Compliance, with controls mapped to NIS2 and an export pack for auditors |
| (g) Training | People & Awareness, with a timestamped record per person |
| (h) Cryptography | SSL/TLS Monitor, with expiry alerts |
| (i) Assets | Asset Database |
| (j) Authentication | Not something SimpleSecurity provides. This point is about your own sign-in and communication tools. |
See every service or see the plans.
Related guides
11. Sources
- Directive (EU) 2022/2555 (NIS2), Articles 2, 20, 21, 23, 34 and 41
- Commission Implementing Regulation (EU) 2024/2690
- Cybersäkerhetslag (2025:1506), Svensk författningssamling
- MCFFS 2026:11, security measures and management training (binding rules and non-binding advice), in force 1 October 2026
- MCFFS 2026:8, incident reporting, in force 1 July 2026