NIS2 guide
NIS2 requirements for suppliers
NIS2 puts its duties on the organisations it covers, not on their suppliers. But one of those duties is to secure the supply chain, so covered customers have to pass requirements on to the companies they buy from. In Sweden the authority's regulation makes that a binding duty. This page explains both sides.
On this page
This is a plain-language summary, not legal advice. Where this page and the law differ, the law decides. The two checklists are practical examples, not legal text, except where a line says Binding and cites MCFFS 2026:11. The general advice in that regulation is not binding.
1. In short
- Supply chain security is one of the ten areas NIS2 requires (Article 21(2), point (d)).
- It is about the relationship between a covered organisation and each of its direct suppliers and service providers.
- A covered organisation must weigh each supplier's specific vulnerabilities, the quality of its products and its cybersecurity practices (Article 21(3)).
- Recital 85 says covered organisations "should in particular be encouraged" to put security measures into their contracts with direct suppliers. That is the directive's wording. In Sweden it is a binding duty: the contract or agreement must make sure appropriate and proportionate security measures can be carried out and kept up over time (MCFFS 2026:11, 4 kap. 4 §, in force 1 October 2026).
- The duties in Article 21 are placed on essential and important entities. A supplier that is neither should still expect covered customers to ask how it handles security.
2. What the directive says
| Where | What it says |
|---|---|
| Article 21(2)(d) | The measures must include at least "supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers". |
| Article 21(3) | When deciding which supply chain measures are appropriate, entities must take into account "the vulnerabilities specific to each direct supplier and service provider and the overall quality of products and cybersecurity practices of their suppliers and service providers, including their secure development procedures". They must also take into account the results of any coordinated security risk assessments of critical supply chains carried out at EU level under Article 22(1). |
| Recital 85 | Entities "should in particular be encouraged to incorporate cybersecurity risk-management measures into contractual arrangements with their direct suppliers and service providers". They "could consider risks stemming from other levels of suppliers and service providers". |
| Recital 86 | Entities "should therefore exercise increased diligence in selecting a managed security service provider". |
The recitals are the directive's own explanation of its articles. Note their wording: "should be encouraged" and "could consider". The Swedish regulation goes further for covered operators (section 6).
3. If you are covered
Practical examples. The basis is Article 21(2), point (d), and Article 21(3). The contract terms come from recital 85 and the extra care with managed security service providers from recital 86. In Sweden some of these steps are binding duties under MCFFS 2026:11, chapter 4. Lines marked Binding in Sweden cite it (section 6).
- List your direct suppliers and service providers, and what each one can reach.
- Assess each one: its specific vulnerabilities, the quality of its products, its security practices and how it develops software. Binding in Sweden: assess and handle the risks before you buy or outsource, and judge whether the supplier can meet the cybersecurity requirements for the whole contract term (4 kap. 1 §).
- Put security requirements into the contract. Binding in Sweden (4 kap. 4 §).
- Ask to be told about incidents fast enough that you can meet your own 24-hour deadline.
- Repeat the assessment on a schedule, and after an incident.
- Take extra care when you choose a managed security service provider.
- Binding in Sweden: identify and handle the need to keep running if the hardware, software or information you depend on is not delivered, and the need for suppliers to tell you about their own subcontractors (4 kap. 2 §).
- Keep the evidence: the questions, the answers, your decisions and the dates.
4. If you are a supplier
The directive does not list what a supplier must show. Covered customers have to take a supplier's vulnerabilities, product quality and security practices into account (Article 21(3)). In Sweden a covered customer must also make sure that its supplier meets the requirements the regulation sets on the customer, except where the customer itself meets a requirement in full (MCFFS 2026:11, 4 kap. 1 §, second paragraph). So expect questions like these.
- A security policy and a named contact person.
- How fast you tell the customer about an incident that affects them.
- How you find and fix vulnerabilities.
- How you develop software securely, if you deliver software.
- Who has access to the customer's data or systems, and how sign-in is protected.
- Which of your own suppliers are involved in the delivery.
- Evidence: test results, audit reports or any certificates you hold.
Advice, not binding. The authority's general advice on contracts for outsourced information processing says they should cover the points below (MCFFS 2026:11, 4 kap. 4 § advice).
- Contact details for your system owner, and the cybersecurity skills you need.
- When and how you tell the customer about suspected and actual incidents, threats, vulnerabilities and changes that could affect compliance.
- How risks from your subcontractors are handled and passed on.
- That you check hardware and software for malicious code before use.
- How much you take part in joint incident, continuity and crisis exercises.
- How you follow up your own and your subcontractors' compliance, and how the customer follows up yours.
- Early termination if you fall short.
- Return or destruction of the customer's information when the contract ends.
For acquired systems, the advice says the contract should require you to check hardware and software for malicious code and other flaws before delivery.
Answer once, keep the answers current and reuse them.
5. Suppliers that are covered themselves
Some suppliers are in an NIS2 sector in their own right. Annex I lists managed service providers and managed security service providers under "ICT service management (business-to-business)", and cloud computing, data centre and content delivery network providers under "Digital infrastructure". A provider of that kind that meets the size rule has duties under the law itself, not only the questions from its customers.
In Sweden, the authority's regulations say two different things about sector activity in digital infrastructure, digital providers, ICT service management (business to business), postal and courier services and space.
- Security measures: an operator whose sector activity is only in those sectors follows only the management training duty (MCFFS 2026:11, 1 kap. 1 §, second paragraph).
- Incident rules: chapters 3–5 of MCFFS 2026:8 do not cover that sector activity. That means the criteria for what counts as significant and the duty to inform recipients (MCFFS 2026:8, 1 kap. 1 §, second paragraph).
This page does not say more than that. For technical measures, Implementing Regulation (EU) 2024/2690 applies to the providers it names.
In Sweden, a provider of cloud, data centre or content delivery services, managed services (utlokaliserade driftstjänster) or managed security services (utlokaliserade säkerhetstjänster) is covered by 1 kap. 7 § of Cybersäkerhetslagen when its main establishment, or its representative, is in Sweden and it is at least medium-sized or meets one of the special criteria in 1 kap. 5 §, points 1 to 3.
6. In Sweden
Cybersäkerhetslagen (2025:1506) lists supply chain security (säkerhet i leveranskedjan) as point 4 of the ten areas that security measures must cover (2 kap. 3 §). More on the Swedish law: Cybersäkerhetslagen: what Sweden's NIS2 law requires.
The directive only encourages contract terms (recital 85). Sweden has gone further. The authority's regulation MCFFS 2026:11 (in force 1 October 2026) makes supplier duties binding for covered operators. It was issued by MCF. Since 1 July 2026 FRA holds the rule-making role, and the regulation applies unchanged. Chapter 4 says:
| Section | Binding duty of the covered operator |
|---|---|
| 4 kap. 1 § |
|
| 4 kap. 2 § | Identify and handle the need for continuity in your digital supply chains for the hardware, software and information you need. To handle weak points, especially where no alternative exists if delivery fails or falls short, identify and handle the need for the supplier to give relevant information about its subcontractors. |
| 4 kap. 3 § | Identify and handle the need to choose products, services and processes certified under European cybersecurity certification schemes when you acquire or outsource. This is a duty to assess the need, not a duty to buy certified products. Advice, not binding: products or services in sector-critical systems (systems you need to run your sector activity or provide your outside services) should be certified. |
| 4 kap. 4 § | In the contract or agreement with the supplier, make sure appropriate and proportionate security measures can be carried out and kept up over time. |
Contracts signed before 1 October 2026. The text sets a date rule: you must identify and handle the need to, if possible, supplement them with cybersecurity requirements, and handle the risks of any that have insufficient requirements (4 kap. 1 § fourth paragraph). The regulation does not say old contracts become invalid.
Advice, not binding. The general advice also says to assess risks from subcontractors in the supply chain (4 kap. 1 § advice), and to consider the EU's coordinated risk assessments of critical supply chains (Article 22(1)) and the authorities' recommendations on digital sovereignty (4 kap. 2 § advice). The regulation itself says that advice is not binding.
These duties apply to operators the security measure rules cover. They do not apply to an operator whose sector activity is only in the sectors named in section 5, apart from management training. If you are a covered operator, the tick-list is in the NIS2 compliance checklist. For a supplier that is asked about certificates, see Is there a NIS2 certification? Not sure you are covered? Does NIS2 apply to my company?
7. How SimpleSecurity helps
SimpleSecurity keeps the record of who you asked, what they answered and when. It does not make an organisation compliant by itself, and SimpleSecurity holds no certification.
- Vendor Risk: tiered questionnaires, a portal where the vendor answers, and CSV import and export.
- Asset Database: links each vendor to the systems it touches.
- Incident Register: vendor signals are queued as incident candidates for you to judge.
If you are the supplier, the records customers ask for are the ones the other services keep: policies, training records, vulnerability scan results and an incident log.
See every service or see the plans.
Related guides
8. Sources
- Directive (EU) 2022/2555 (NIS2), Article 21(2) and (3), Article 22, recitals 85 and 86, Annex I
- Cybersäkerhetslag (2025:1506), 1 kap. 7 § and 2 kap. 3 §
- MCFFS 2026:11, 1 kap. 1 § and 4 kap. 1–4 §§, in force 1 October 2026
- MCFFS 2026:8, 1 kap. 1 §, in force 1 July 2026