NIS2 guide
Is there a NIS2 certification?
No. NIS2 does not create a certificate that shows an organisation complies with it. Compliance is shown to the supervisory authority, which can ask for documents, inspect and order audits. This page explains what the law says and what you can show customers and auditors instead.
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
- Neither NIS2 nor Cybersäkerhetslagen (2025:1506) sets up a certificate that proves an organisation complies. The Swedish law text has no certification requirement. The authority's binding rules (MCFFS 2026:11, from 1 October 2026) do touch standards and certified products; see section 3.
- Compliance is checked through supervision: the authority can ask for information and documents, enter premises, order security audits and run security scans (3 kap. 3–7 §§).
- NIS2 Article 24 lets a member state require certified ICT products, services or processes. It also lets the Commission, by delegated act (an extra EU rule the Commission can add later), require some categories of entity to use such products or to obtain a certificate under an EU certification scheme. None of that is a certificate of NIS2 compliance.
- Article 25 says member states shall encourage European and international standards, without requiring any one of them, and that ENISA draws up advice and guidelines on them.
- Show customers evidence instead: a mapping to the ten areas, training records, incident procedures and your registration. An ISO/IEC 27001 certificate can support that. The law does not treat it as proof of compliance; the authority's general advice (MCFFS 2026:11) names SS-ISO/IEC 27001:2022 as a standard to use in the security work.
2. Is there a NIS2 certificate?
No official one. The directive and the Swedish law describe duties (the ten security areas, management training, incident reporting, registration) and a way to check them, which is supervision. Neither creates a certificate, a seal or a register of “compliant” organisations.
The three Swedish law texts were searched for the words “certifi” and “27001”: Cybersäkerhetslagen (2025:1506), Cybersäkerhetsförordningen (2025:1507) and the amendment SFS 2026:623. There were no hits. So the law itself requires no certificate and names no standard. The authority's binding rules (föreskrifter) do mention standards and certified products; see the end of section 3.
3. What the law allows (Article 24)
The word “certification” does appear in the directive. Here is exactly where, and what it covers.
| Where | What it says |
|---|---|
| Article 24(1) | "In order to demonstrate compliance with particular requirements of Article 21, Member States may require essential and important entities to use particular ICT products, ICT services and ICT processes ... that are certified under European cybersecurity certification schemes adopted pursuant to Article 49 of Regulation (EU) 2019/881." |
| Article 24(2) | The Commission may adopt delegated acts "specifying which categories of essential and important entities are to be required to use certain certified ICT products, ICT services and ICT processes or obtain a certificate under a European cybersecurity certification scheme". Such acts "shall be adopted where insufficient levels of cybersecurity have been identified and shall include an implementation period". |
| Article 24(3) | Where no appropriate scheme exists, the Commission may, after consulting the Cooperation Group and the European Cybersecurity Certification Group, "request ENISA to prepare a candidate scheme". |
| Recital 80 (explanatory text in front of the directive) | In the absence of appropriate schemes, member states "should ... promote the use of relevant European and international standards by essential and important entities or may require entities to use certified ICT products, ICT services and ICT processes". |
| Article 25(1) | Member states shall "encourage the use of European and international standards and technical specifications relevant to the security of network and information systems", without imposing or favouring a particular type of technology. |
Three things follow from the text.
- Article 24(1) is a permission ("may"). It concerns ICT products, services and processes, and ties to the schemes of Regulation (EU) 2019/881, the Cybersecurity Act.
- Article 24(2) lets the Commission make certified products, or a certificate under such a scheme, binding for named categories of entity by delegated act, so the picture could change. This page has not confirmed that any such act exists, so check the Commission's pages if it matters to you.
- The Swedish law text has no certification requirement (Cybersäkerhetslagen, the ordinance, SFS 2026:623). The authority's rules are covered below.
What the EU certification schemes cover
A scheme adopted under the Cybersecurity Act is the European Common Criteria-based scheme (EUCC), set out in Implementing Regulation (EU) 2024/482. Its Article 1 says the regulation "applies to all information and communication technologies ('ICT') products ... which are submitted for certification under the EUCC", and to protection profiles submitted as part of the ICT process leading to product certification. It certifies ICT products, not organisations.
Standards in the rules for digital providers
Implementing Regulation (EU) 2024/2690 sets the detailed security measures for DNS service providers, cloud providers, data centres, managed service providers and some other digital providers. Its recital 3 says the technical and methodological requirements in its Annex "are based on European and international standards, such as ISO/IEC 27001, ISO/IEC 27002 and ETSI EN 319401, and technical specifications, such as CEN/TS 18026:2024". Recital 17 says entities can obtain assurance about the ICT products and services they buy "for example by European cybersecurity certificates and EU statements of conformity". These are explanations in the recitals. They do not turn a standard into proof of compliance.
Standards and certified products in the authority's binding rules
The authority's rules (föreskrifter) are binding. Its general advice (allmänna råd) is not: the regulation itself says general advice has "en annan juridisk status än föreskrifter" and "De är inte tvingande". MCFFS 2026:11, in force 1 October 2026 and applying unchanged under FRA, says two things relevant here.
- Standards (3 kap. 2 §, binding). The operator "ska identifiera och hantera behovet av att använda relevanta standarder i cybersäkerhetsarbetet" (must identify and deal with the need to use relevant standards). The general advice (not binding) says SS-ISO/IEC 27001:2022 and SS-EN ISO/IEC 27002:2022, or equivalent, should be used as support. That is advice, not a certificate requirement and not proof of compliance.
- Certified products (4 kap. 3 §, binding). When acquiring or outsourcing, the operator must identify and deal with the need to choose products, services and processes certified under the European cybersecurity certification schemes of the Cybersecurity Act (Article 1.1 b). The general advice says products and services in sector-critical systems should be so certified. This is a duty to assess the need, not a flat requirement to buy certified products. In single cases, and for special reasons, FRA can grant an exemption from this regulation (7 kap. 1 §). Operators active only in digital infrastructure, digital providers, ICT service management (business to business), postal and courier services and space are covered by this regulation only for management training (2 kap. 1 §); see 1 kap. 1 §, second paragraph.
5. What to show customers instead
There is no official NIS2 certificate for customers or auditors to ask for. They can ask for evidence. Practical examples, tied to the law where there is a link:
| Show this | Why it counts |
|---|---|
| A mapping of your measures to the ten areas | 2 kap. 3 § lists the ten areas the measures must at least cover. See the NIS2 compliance checklist. |
| Records that management has been trained | 2 kap. 4 § says the people in the management must complete training on security measures. A dated attendance list is the natural proof. |
| Incident procedures and an incident log | The law sets a 24-hour first notice, a 72-hour incident report (24 hours for trust service providers) and a final report within one month. See NIS2 incident reporting. |
| Your registration confirmation | 2 kap. 2 § requires registration with the authority. See NIS2 registration. |
| Supplier answers and contract terms | See NIS2 requirements for suppliers. |
| An ISO/IEC 27001 certificate, if you hold one | It is a certificate for an information security management system under a recognised standard. It can support your evidence, but it does not equal NIS2 compliance. NIS2 and Cybersäkerhetslagen do not name ISO 27001 as proof of compliance; the authority's general advice names the standard as support. |
Whether your organisation is covered at all is a separate question: Does NIS2 apply to my company?
6. “NIS2 certified” claims
Some companies sell badges, audits or reports described as “NIS2 certified”. Since the law creates no NIS2 compliance certificate and appoints no body to issue one, such a badge is a private statement by the company that issues it. It is not an official status under the law.
- Ask who issued it, what exactly was checked, against which standard and on what date.
- A certificate under a recognised standard, such as ISO/IEC 27001, is a different thing: it names the standard it is issued under.
- A private report does not replace your duties under the law.
7. How SimpleSecurity helps
SimpleSecurity does not certify anyone and holds no NIS2 certificate to give. It keeps the records you would otherwise assemble by hand, and framework mapping is readiness support.
| Evidence | Service |
|---|---|
| Mapping to the ten areas | Compliance maps controls across 22 frameworks, including NIS2/Cybersäkerhetslagen, with an auditor-ready export pack. |
| ISO 27001 readiness | Statement of Applicability covers all 93 Annex A controls of ISO 27001:2022: you record whether each applies, with reasons, justification and evidence. |
| Policies | Policy Register tracks the policy lifecycle, with review SLAs. |
| Training records | People & Awareness time-stamps lessons, quizzes and policy read-receipts per person. |
| Incident log | Incident Register keeps NIS2 24h/72h clocks. |
See every service or see the plans.
Related guides
8. Sources
- Directive (EU) 2022/2555 (NIS2), Articles 24, 25, 32(7) and 33(5), recital 80
- Cybersäkerhetslag (2025:1506), 2 kap. 2–4 §§ and 3 kap. 2–11 §§
- MCFFS 2026:11 (security measures and management training), 1 kap. 1 §, 3 kap. 2 §, 4 kap. 3 § and the general advice; MCFFS 2026:12 (security audits and scans), 2 kap. 6 §; both in force 1 October 2026
- FRA: Föreskrifter (the rules apply unchanged under FRA since 1 July 2026)
- Implementing Regulation (EU) 2024/2690, recitals 3 and 17
- Implementing Regulation (EU) 2024/482 (EUCC), Article 1