Skip to main content

Guide

NIS2 for machinery manufacturers: Assess production and IT together

Assess NIS2 in machinery manufacturing: activity, company size, remote maintenance and production dependencies, with a practical recovery test.

NIS2 for machinery manufacturers: Assess production and IT together
Julian Köhn
|Read time: 3 minutes

Machinery manufacturing brings office IT, engineering and production together across different maintenance cycles. An update completed quickly on a workstation may require manufacturer coordination for production equipment. NIS2 work needs to make those differences visible.

Start with one production chain. These steps help record dependencies, govern remote maintenance and connect a postponed update with a time-limited approach.

Assess scope using the actual activity

Annex 2 of Germany’s BSIG includes machinery manufacturing under NACE Rev. 2, section C, division 28. The conditions in section 28 BSIG also apply. Calling yourself a machinery manufacturer on a website neither proves nor excludes applicability.

Document the activity, legal entity and data used for the size assessment. Corporate groups also need to examine aggregation. Customer requirements can apply additionally even where no direct statutory duty arises.

Start with a production order

Record required engineering data, bills of materials, programmes and equipment. Then examine central services affecting several steps simultaneously: identities, network, file storage or remote maintenance.

A dependency matters even if a provider operates it. Ask how an outage is detected and who may act. Our supplier risk guide provides review questions.

Treat remote maintenance as a complete process

Fictional example: An equipment manufacturer needs urgent access. Check approval, identity, time limits, logging and termination. Can production see whether access is still needed? Is there a traceable route for an incident outside usual hours?

A documented VPN alone does not answer these questions. The measure must cover the full workflow.

Test recovery before an emergency

Choose one installation and check which configurations, programmes and licences restoration needs. An existing backup becomes meaningful when recovery works using the resources available.

Assign an owner and deadline to unresolved manufacturer dependencies. Unavoidable transitional risks need conscious risk acceptance, rather than an indefinite exception.

An update is an operational change

If a manufacturer needs to assess a change first, that is not automatically a reason to stop production immediately or wait indefinitely. Record the affected system, specific threat and restriction preventing the normal update route.

Assess interim safeguards with operations and the manufacturer. Depending on the installation, these may include restricted access, another maintenance route or additional monitoring. Technical suitability needs assessment; entering “compensated” is insufficient.

DecisionRequired basis
Change in the next maintenance windowConfirmed date, owner and approval conditions
Time-limited continued operationReasoned treatment of remaining exposure
Test before production approvalFunctional test, recovery option and documented result

In Kopexa, you can keep affected assets, the risk and measures together. A BPMN process describes technical and operational approvals. Evidence should identify the equipment configuration actually tested.

The first project scope should support one order

Start with a production chain involving engineering, programme transfer and selected equipment. Involve an owner from each function. The outcome is a traceable protection and recovery need for that chain. Extend the approach to other installations by priority.

Track implementation in Kopexa

Information assets, other assets and dependencies preserve the production context. Risks, measures and evidence show what is implemented and what needs checking. Evidence maintenance remains necessary after the initial project ends.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

Is every machine automatically within NIS2 scope?

No. Classification starts with the entity and activity. Derive traceably which systems matter to its security.

Sources

  1. BSIG section 28: Scope — Bundesministerium der Justiz [Accessed ]