Key takeaways
- Annex II lists six manufacturing subsectors plus chemicals and food. Manufacturers in scope are usually important entities, unless a member state designates them essential.
- The size cap uses the EU SME definition: medium-sized or larger is in. Group structures count, so check linked and partner enterprises.
- Article 21 requires proportionate risk-management measures across ten areas, including supply chain, incident handling, business continuity and access control. OT is in scope.
- Article 23 sets reporting stages: early warning within 24 hours, notification within 72 hours, final report within one month.
- Management bodies must approve and oversee the measures, take training and can be held liable (Article 20). National laws decide the details, and as of November 2026 a few member states had still not finished transposition.
For most mid-market manufacturers, the first NIS Directive was something that happened to utilities. NIS2 is different. It names manufacturing sectors directly, uses a simple size test, and puts personal accountability on the management body. If you build machines, electrical equipment, electronics or vehicles in the EU, or you process food or make chemicals at industrial scale, assume you need to look at it closely.
This page explains the directive. Your actual obligations come from your national law, which can add detail and, in some countries, extend scope.
What NIS2 is
NIS2 is Directive (EU) 2022/2555, adopted on December 14, 2022, and in force since January 16, 2023. Member states had to transpose it into national law by October 17, 2024. It replaces the 2016 NIS Directive and sets a common baseline for cybersecurity risk management, incident reporting and supervision across 18 sectors.
Does it apply to you?
Sector: Annex II
Manufacturers mostly fall under Annex II, "other critical sectors". The relevant entries are:
| Annex II sector | What is covered |
|---|---|
| Manufacturing: medical devices and in vitro diagnostics | Manufacturers of medical devices under Regulation (EU) 2017/745 and IVDs under Regulation (EU) 2017/746 (with some exclusions) |
| Manufacturing: computer, electronic and optical products | NACE Rev. 2, Section C, Division 26 |
| Manufacturing: electrical equipment | NACE Rev. 2, Section C, Division 27 |
| Manufacturing: machinery and equipment n.e.c. | NACE Rev. 2, Section C, Division 28 |
| Manufacturing: motor vehicles, trailers and semi-trailers | NACE Rev. 2, Section C, Division 29 |
| Manufacturing: other transport equipment | NACE Rev. 2, Section C, Division 30 |
| Chemicals | Manufacture, production and distribution of substances and mixtures under REACH |
| Food | Food businesses engaged in wholesale distribution and industrial production and processing |
Annex I sectors (energy, transport, health, drinking water and others) can also catch manufacturers, for example a pharmaceutical maker under health, or a company with its own energy assets. Check both annexes against your main activities.
Watch out: NACE codes describe activities, not company names. A packaging company that also builds and sells its own machines may have a Division 28 activity. Ask your finance team which NACE codes you report, then check whether your national law looks at the main activity or any activity.
Size: the medium-sized cap
Article 2(1) brings in entities that qualify as medium-sized enterprises under Commission Recommendation 2003/361/EC, or exceed those ceilings. In practice that means you are in unless you are a small or micro enterprise. Under the recommendation, a small enterprise has fewer than 50 staff and annual turnover or balance sheet total of no more than €10 million. So you are in scope if you have 50 or more staff, or if both your turnover and your balance sheet exceed €10 million.
The recommendation's rules on linked and partner enterprises apply, so a 40-person subsidiary of a large group is usually in. Article 2(2) also lets member states bring in smaller entities in specific cases, such as sole providers of a critical service.
Essential or important?
Article 3 splits in-scope entities into two classes.
- Essential entities are, mainly, large companies in Annex I sectors, plus some specific types and any company a member state designates.
- Important entities are everything else in scope, which includes medium and large Annex II manufacturers.
Both classes have the same core duties. The difference is supervision and fines. Essential entities face proactive supervision. Important entities are supervised after the fact, typically when there is evidence of non-compliance or an incident.
Note: Commission Implementing Regulation (EU) 2024/2690 sets detailed technical measures for digital infrastructure and digital providers such as cloud and managed service providers. It does not apply to manufacturers as such. Do not use it as your checklist, although it can be a useful reference.
What you must do
Article 21: risk-management measures
Article 21 requires appropriate and proportionate technical, operational and organizational measures, based on an all-hazards approach. Proportionality depends on your risk exposure, size, the likelihood and severity of incidents and cost. The measures must cover at least:
- Risk analysis and information system security policies.
- Incident handling.
- Business continuity, including backup management, disaster recovery and crisis management.
- Supply chain security, including relationships with direct suppliers and service providers.
- Security in acquisition, development and maintenance of systems, including vulnerability handling and disclosure.
- Policies and procedures to assess whether the measures work.
- Basic cyber hygiene and cybersecurity training.
- Cryptography and, where appropriate, encryption.
- Human resources security, access control and asset management.
- Multi-factor or continuous authentication, secured communications and secured emergency communications, where appropriate.
None of this is OT-specific, and none of it excludes OT. Here is how it lands on the plant floor:
| Article 21 area | Plant-floor translation |
|---|---|
| Asset management | An OT asset inventory per site |
| Supply chain | OEM and integrator security requirements; control of vendor remote access |
| Business continuity | Tested backups of PLC logic, HMI and SCADA configs; recovery priorities per line |
| Access control and MFA | MFA on remote access to OT; no shared engineering accounts |
| Incident handling | An OT incident response playbook that operations has rehearsed |
| Vulnerability handling | A realistic patch process for OT that works with maintenance windows |
IEC 62443 and NIST CSF 2.0 give you a recognized structure for these measures. Our framework crosswalk maps Article 21 to both.
Article 23: incident reporting
If you have a significant incident (one that causes or can cause severe operational disruption or financial loss, or considerable damage to others), you report to your national CSIRT or competent authority in stages:
| Stage | Deadline |
|---|---|
| Early warning | Without undue delay and within 24 hours of becoming aware |
| Incident notification | Within 72 hours of becoming aware, with an initial assessment |
| Intermediate report | On request |
| Final report | Within one month of the incident notification |
The 24-hour clock is the hard part. It means someone on the night shift needs to know who to call when the lines stop and the HMIs show a ransom note.
Plant-floor reality: Many plants find out about an incident as "the line is down and we don't know why". Your playbook needs a rule for when an unexplained outage gets escalated to the security lead, so the reporting clock does not start without anyone noticing.
Article 20: management body accountability
The management body must approve the Article 21 measures and oversee their implementation, and it can be held liable for infringements. Members of management bodies must follow training. Member states should also encourage regular training for employees. In practice: the board or managing directors need to see and sign off the program, not just receive a summary. A short, regular board briefing on OT and IT risk works better than a once-a-year slide.
Fines
For important entities, national law must allow maximum fines of at least €7 million or 1.4% of worldwide annual turnover, whichever is higher. For essential entities, at least €10 million or 2%.
Supply chain: both directions
NIS2 affects you as a customer and as a supplier.
- As a customer: you must manage risk from your OEMs, integrators, MSPs and cloud providers. Use a questionnaire such as the OT and AI vendor security questionnaire and put security terms in contracts.
- As a supplier: your customers in scope will send you their questionnaires. Expect requests for evidence on patching, remote access and incident notification.
For products with digital elements you make or buy, the Cyber Resilience Act adds product-level duties that sit next to NIS2.
Transposition status (as of November 2026)
National laws decide registration deadlines, competent authorities and some of the detail. As of November 17, 2026:
- The transposition deadline was October 17, 2024. Most member states missed it. The Commission sent reasoned opinions to 19 member states on May 7, 2025.
- On July 8, 2026, the Commission referred Ireland, Spain, France and the Netherlands to the Court of Justice of the EU for failing to notify full transposition.
- The Netherlands' Cyberbeveiligingswet entered into force on August 15, 2026.
- France's transposition bill was still before parliament in November 2026, according to French legal press. Public trackers also listed Ireland and Spain as not yet in force in late October 2026.
This changes month to month. Check your national authority's website before you plan around a date.
Note: In January 2026 the Commission proposed targeted amendments to NIS2 as part of a cybersecurity package, including simplification measures. As of November 2026 these were proposals in the legislative process, not law.
Effort and cost
For a 300 to 1,500 person manufacturer starting from a typical IT-only security program:
- Scoping and registration: days, but get legal input on NACE codes and group structure.
- Gap assessment against Article 21 across IT and OT: 4 to 8 weeks.
- Closing gaps: usually 12 to 24 months. The biggest OT items are segmentation, remote access, backups and incident response.
- Board training: a half-day session to start, then annually.
Common mistakes
- Assuming "we are just a manufacturer, NIS2 is for utilities".
- Scoping IT only and leaving the plants out.
- Treating the 24-hour early warning as a legal task, not an operational one.
- Waiting for national law before doing anything. The core measures are already clear from the directive.
- Using the digital-provider implementing regulation as a manufacturer's checklist without adapting it.
Where to start: Monday-morning checklist
- Confirm your NACE codes, headcount and turnover at group level. Decide with counsel whether you are in scope and in which countries.
- Find your national authority and check registration requirements and deadlines.
- Brief the management body on Article 20 and schedule training.
- Run a gap assessment against Article 21 that includes every plant. The OT security maturity assessment is a quick start.
- Write and test a 24-hour escalation path for production outages.
- Add NIS2 security clauses to OEM, integrator and MSP contracts at renewal.
This page is not legal advice. Confirm your scope and obligations under your national law with counsel.
Sources and further reading
- Directive (EU) 2022/2555 (NIS2), EUR-Lex
- Commission refers Ireland, Spain, France and the Netherlands to the Court of Justice (European Commission, 8 July 2026)
- NIS2 Directive transposition in EU countries (European Commission)
- Cyberbeveiligingswet en Wet weerbaarheid kritieke entiteiten van kracht (Government of the Netherlands, 15 August 2026)
This guide is general information for manufacturers, not legal advice. Confirm regulatory obligations with qualified counsel.
FAQ
Frequently asked questions
Does NIS2 apply to my manufacturing company?
Check three things. First, is your main activity in an Annex II sector, such as manufacture of machinery (NACE division 28), electrical equipment (27), computer and electronic products (26), motor vehicles (29), other transport equipment (30), medical devices, chemicals or industrial food production? Second, are you at least medium-sized under the EU SME definition? Third, do you operate in an EU member state whose national law follows the directive? Then read your national law, which decides registration and supervision.
Is a manufacturer an essential or an important entity under NIS2?
Annex II sectors, which include the manufacturing subsectors, chemicals and food, make in-scope companies important entities by default. A member state can designate a company essential, for example if it is the sole provider of a critical service or if disruption could have significant systemic or cross-border effects. Important entities are supervised after the fact (ex post), essential entities proactively.
What are the NIS2 fines for manufacturers?
For important entities, member states must allow maximum fines of at least €7 million or 1.4% of total worldwide annual turnover, whichever is higher. For essential entities the floor for the maximum is €10 million or 2%. National laws can set higher maxima. Fines apply to breaches of the risk-management and reporting duties in Articles 21 and 23.
Does NIS2 cover OT and production systems or only IT?
NIS2 covers the network and information systems an entity uses for its operations or to provide its services. For a manufacturer that includes OT: PLCs, SCADA, MES and the networks that connect them. A ransomware attack that stops production lines can be a significant incident that must be reported, even if no customer data is touched.
Related guides
Frameworks
Cyber Resilience Act for industrial manufacturers: what makers and plants need to do
The EU Cyber Resilience Act (Regulation (EU) 2024/2847) sets cybersecurity requirements for products with digital elements sold in the EU, from PLC-based machines to…
7 min read
Frameworks
IEC 62443 for mid-market manufacturers: a practical guide
ISA/IEC 62443 is the main international series for securing industrial automation and control systems. For a mid-market manufacturer, the useful core is small: run a…
8 min read
Frameworks
NIST CSF 2.0 for manufacturers: one language for IT, OT and the board
NIST Cybersecurity Framework (CSF) 2.0 is a voluntary, outcome-based framework that organizes cybersecurity into six functions: Govern, Identify, Protect, Detect…
7 min read
OT Security
OT incident response with AI in the mix: playbooks and tabletops
OT incident response starts with safety and keeping the process in a known state, not with wiping machines. Plan for manual operation, include AI failures alongside…
8 min read