
The modern supply chain does not end with transport and warehousing. Production planning, batch traceability, control systems, data exchange with suppliers, and order processing form a single system of dependencies. When a digital element of this system fails, the consequences can quickly affect delivery timeliness, product quality, and customer relationships. Therefore, preparation for NIS2 should be conducted as an operational resilience project, not just a task for the IT department.
NIS2 should be read through the lens of the process
In a manufacturing company, the first question should not be: what security tool do we need to buy? It is more important to determine which processes must function so that an order can be accepted, work planned, an order launched, batch compliance confirmed, goods shipped, and reliable information provided to the customer. Only against this background can one see where a digital incident becomes a logistical and business problem. A useful starting point may be material on NIS2 for manufacturing companies, which organizes the topic of business continuity, management responsibility, and risk oversight.
Disruption of the planning system can change the order of tasks or stop the transfer of information between production and the warehouse. Loss of access to batch data, recipes, or control records can make it difficult to release a product and reconstruct the history of the process. In turn, failure of communication channels with suppliers and customers affects the confirmation of deadlines, complaint handling, and shipping decisions. This shows that digital resilience should be discussed jointly by operations, quality, maintenance, logistics, purchasing, and IT.
A dependency map is more important than a list of systems
Preparation should start with a map of critical processes. It should show not only applications and devices but also data, people, external suppliers, and decisions that must be made in a specific order. For each process, the consequences of losing information availability or integrity must be determined. We will assess a short unavailability of an auxiliary tool differently than the lack of data needed for batch traceability or safe resumption of line operation.
In a plant operating for the food industry, digital dependencies are additionally linked to the supervision of hazards, control points, and records. HACCP documentation itself can be an important element of work, but it does not replace a coherent model of responsibility, monitoring, and response to deviations. Therefore, the implementation of ELOT EN ISO 22000:2018 can be treated as an example of organizing food safety processes, documentation, and competencies, although it is not a substitute for an analysis of obligations related to NIS2.
The map should also include external dependencies. A supplier of a system, cloud service, automation, service, or component may have an impact on the plant’s ability to fulfill orders. It is therefore worth knowing how incidents are reported, who makes decisions on the supplier’s side, what information is available during a failure, and how operations can be restored. The assessment should not be limited to price and the declared delivery date alone.
Responsibility must work under pressure
A response procedure is only valuable if it helps make decisions under conditions of information scarcity. The organization should clearly indicate who triggers escalation, who assesses the impact of the event on production and product compliance, who contacts the customer, and who approves recovery actions. Rules for switching to emergency mode, maintaining substitute records, and returning to standard work are also needed.
A good test is a scenario of unavailability of the system on which production registration and batch release are based. Is it known what information needs to be recorded manually? Who decides if production can continue? Who assesses the impact on quality, and who verifies data completeness after system restoration? If the answers are scattered among departments, the exercise reveals an organizational gap before a real incident does.
In the food sector, similar discipline can be linked to daily product safety management. The description of the HRN EN ISO 22000:2018 system points to the importance of responsibility, operational records, supervision of critical points, and audit preparation. These elements can support the organization of work, but the scope and method of their application must always be adapted to the specific process and profile of the organization.
Preparation plan: from risk owner to exercise
The first step should be to appoint a sponsor from the management side and a cross-functional team. Then, the company can determine the scope of activities and processes requiring special attention, identify critical resources, describe dependencies on external parties, and conduct a gap analysis. It is worth using existing mechanisms: management reviews, internal audits, supplier qualification, change management, training, and corrective actions.
The next stage is the selection of several scenarios with the greatest operational significance. They may concern the unavailability of planning, loss of traceability data, disruption of communication with a supplier, or a problem with a system supporting warehousing. For each scenario, roles, the order of decisions, required records, communication methods, and criteria for a safe return to normal work must be defined. The exercise does not have to be extensive, but it should lead to concrete conclusions.
Only after analyzing processes and gaps is it worth setting investment priorities. Otherwise, the organization may buy solutions that it cannot incorporate into procedures or create documentation that does not correspond to real threats. Measures of progress can include escalation time, completeness of substitute records, readiness for emergency work, and the time to restore a critical process.
Supply chain resilience is a board-level task
NIS2 in production does not boil down to securing infrastructure. It is a test of whether the organization understands its critical dependencies, can assign responsibility, and has evidence that the adopted rules work. For logistics, this means protecting the continuity of the flow of information and goods, and for production – maintaining control over the process, quality, and shipping decisions.
The board does not have to start with a full program covering every area simultaneously. However, it should quickly confirm the scope of the analysis, appoint risk owners, and require a realistic plan of exercises and corrective actions. Such an approach allows for combining cybersecurity requirements with operational practice and reducing the risk that a digital incident will turn into downtime, a quality problem, or a crisis in customer relations.








